Skip to main content
Question

Seats and Billing for temporary collabs

  • June 30, 2026
  • 1 reply
  • 0 views

AACh

As a freelance user of Figma, I find the current seat-based model effective for structured team collaboration, but it creates friction in freelance and cross-workspace scenarios.

There are two specific situations where the current model feels restrictive:

First, when two already-subscribed users need to collaborate on a single file, one of them may still be treated as an additional billable editor within the other’s workspace. This can lead to a form of duplicate billing, even though both users are already paying for the platform.

Second, there is currently no lightweight alternative to full workspace membership for temporary collaboration. Even short-term or file-specific work often requires assigning a full editor seat, which is not always aligned with the scope of the collaboration.

A potential improvement could combine both issues by introducing more flexible collaboration options. For example, allowing already-paid users to collaborate across workspaces without triggering additional editor charges, alongside a “file-scoped editor access” or temporary editor pass for external collaborators who only need access to specific files rather than full workspace membership.

This would better reflect real freelance workflows, where collaboration is often short-lived and project-specific, while still preserving workspace structure, security, and scalability.

1 reply

djv
Figmate
  • Community Support
  • June 30, 2026

Hi ​@AACh, thanks for your honest feedback! 

I hear you and completely understand the friction this is causing you. These are two distinct issues, so I’d like to address them separately:

  • Duplicate billing between two paying users: This can be solved by Connected Projects. It lets two parties share a project using seats from their own plans, so neither side pays for the other's users. An admin sets it up at the project level and the other team/org's admin approves it. (One caveat: both parties need a paid plan, and it's set up per-project, not per-file.)
  • Lightweight, file-scoped access for one-off external collaborators: This isn't something Connected Projects currently covers. It's currently built for two paid parties connecting, not a quick temporary pass for someone without a plan. We appreciate this feedback though, and we can pass it along to the team as a separate request.

Hope this helps clarify, and thanks again for your feedback!