Connected folders

Hi ​@Martin Fabricius, welcome to Figma Forum and thanks for laying this out — these are great questions!

On the Organization plan (your client's) a Dev or Full seat gets up to 200 tool calls per day and 15 per minute, while a View or Collab seat gets up to 6 per month on any paid plan. The full table is here: Rate limits & access — worth comparing against what the developers are seeing.

How connected folders and MCP rate limits interact specifically for your setup depends on the actual seat assignments on that folder. To make sure we have this clarified, this is going to need a look at your account and folder settings.

As for your 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?
   Outside users show up as guests when they join a connected folder — that part is expected. Seats determine which Figma products someone can access, while edit and view permissions are set per file. A deeper look into your folder settings will help clarify specifics, though this guide holds more details: Guide to connected folders → How seats work in connected folders.

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?
   MCP limits are set by plan and seat type. For connected folders, the guide states that people work based on the seat they have in their own plan or organization. If that doesn't match up with what you're experiencing, it will be best to get this in front of the Customer Support team so they can look at what's actually being applied.

3. What is the correct setup so their paid Dev and Full seats are the ones being counted?
   There are a couple of routes here: Guide to connected folders → Guests and external users in connected folders. If the invited user belongs to the connected organization (in your case, the client's) they join the folder using the seat type they already have there. If they're from a different external organization, they join your organization as a guest with a View seat by default, and any upgrade request is routed to a host organization admin. From what I understand from your post, your client's product team already falls into the first case, since they hold paid Full and Dev seats in their own organization. So this looks less like a setup change on your side and more like a question of what's actually being applied on the folder.

Since this turns on specifics we can't see from this public thread, it's worth gathering the following before you get in touch with Customer Support:

• What seat each affected developer holds in their own organization
• What seat, if any, they hold in yours
• How each of them was added to the connected folder
• Which folder the files they're hitting currently sit in

With that information, please get in touch directly and share those details securely via the Support Hub.

Know there’s a lot of moving parts here — keep me posted if anything else comes up.

Thanks a lot for the reply, Tom. Looks like we have followed the guidelines correctly, so I’ve tried to contact the support team and I’m awaiting their reply.

Thanks again