Skip to main content
Question

Connected folders

  • September 9, 2026
  • 0 replies
  • 3 views

Martin Fabricius

Hi,

We are having trouble with connected folders.

Setup:

  • We are on Enterprise and we host the connected folder
  • The connected folder is shared with our client's product team
  • The client is on an Organization plan with paid Full and Dev seats

What happens: when the client's users join the connected folder, a guest seat is created for them in our organization. When their developers then use the Figma MCP server, they hit a rate limit almost immediately and get a 429 response.

Our reading of it is that the rate limit is being calculated from their guest seat in our organization rather than from the paid seat they hold in their own plan.

Questions:

  1. Why does joining a connected folder create a guest seat in the host organization at all, when the documentation says each party works based on the seat they hold in their own plan and the host is not billed for external users?
  2. When an external user works in a connected folder owned by the host, which plan and which seat determine their MCP and REST API rate limits?
  3. What is the correct setup so their paid Dev and Full seats are the ones being counted?

Happy to provide the folder link, the affected email addresses and the full 429 response headers.

Thanks,

Martin