New users can’t see all project files and folders despite having editing access

Hi, ​@Lauri_Incrosnatu I updated the ticket to match your urgency. I also added additional notes and context for the agent. I’ll keep an eye on things until we see a resolution. — Jaycee

We’re having the same issues described here; only the original Admin can see all the projects in a Folder, the rest of the team (even if part of the Who can Edit list) can not.

Hey ​@Rafael Grullón, thanks for flagging this here!

What you're describing (only the original admin seeing everything in the folder, while teammates on the Who can Edit list still can't)  lines up with a few other reports in this thread. So I'd like to help narrow down what's going on for you specifically.

A couple of things worth checking first:

1. Open the affected folder and click Share. At the top of that list, look at the Who has access row. Does it show your team or plan name, or does it say People invited to folder?
2. If it says People invited to folder, that folder's access is limited to only the people listed directly on it. A teammate's team-level "Can edit" role won't extend to that folder automatically. They'd need to be added directly to that folder's share list (or the setting switched back to inherit from the team) to see it.
3. If your teammates are already listed directly on that folder's share modal with Can edit and still can't see it.

For more on how folder-level access and inheritance work together, here's our guide to File and folder permissions.

Since checking the specific folder and accounts involved needs more than what I can see from the forum, I'd recommend opening a request through our Support Hub with a link to one of the affected folders. That'll let us dig into the account details and confirm whether this needs further investigation on our end.

I took some time and collected three example folders from our own Figma environment that showcase the problem. This information has already been sent to support by email.

I've also simplified and anonymized them below for this forum, referencing the real examples, in the hope that it helps get this issue resolved even quicker. Even though these images are simplified, all three examples are real, taken from our own Figma.

New user "Jerry Seinfeld" added to the Acme Inc team from the admin panel. Has full edit rights and shows as "Member" in the confusing users list next to the team dropdown.

Example 1

• Old project "folder," created years ago
• Uses Figma's default access settings for both folders and files
• In this specific folder, the new team member "Jerry Seinfeld" was automatically added to the collaborators list and can access all files inside this folder.
• We did not need to do anything. Works the same as it used to when adding a new team member to our Figma.

Example 2

• Old project "folder," created years ago
• Uses Figma's default access settings for both folders and files
• New team member "Jerry Seinfeld" was NOT automatically added to the collaborators list and does NOT see any files inside this folder.
• In folders like this, we've had to change each file permission from “People invited to file “ → “Acme Inc” one by one so that new team members will have access to the files.

Example 3

• New folder, created after the Projects → Folders migration
• Uses Figma's (new) default access settings for both folders and files
• New user "Jerry Seinfeld" can automatically see and access all files.

I know this is a lot to process, but the key questions are:

• Should new team members automatically appear on the collaborators list of old folders?
• Why did the new team member appear in the collaborators list for Example 1, but not Example 2?
• If you've changed the logic so that new members no longer appear in the collaborators list of old folders, and Figma's previous default permission on all the files inside our old folders has remained unchanged through the migration, how are we supposed to get new members access to all our old files, given there's no way to mass-edit permissions? We have hundreds of old folders and thousands of old files, and changing permissions one by one by hand isn't feasible.