We've changed how content is structured and shared in Figma to make organizing team files more flexible and intuitive.
- Projects are now called folders — the concept is the same, but the name has changed everywhere in Figma.
- Folders can now be nested — on paid plans, you can create folders inside other folders, up to 10 levels deep.
- Folder permissions have been simplified — folders inherit access from the parent folder, or access is explicitly limited to specific people.
These changes take effect starting on August 3, 2026, and will take a few weeks to roll out to all users. These changes apply to all users on all plans.
We’ve also updated how users are invited and managed on Starter and Professional plans to give admins more control.
Projects are now called folders
Projects are now called folders. You’ll see this reflected everywhere in Figma: menus, the share modal, and across the file browser.
Your files are in the same place and have not moved.
When you create a new folder, you can now customize the folder’s color, making it easier to distinguish folders at a glance.
Learn more about creating and managing folders.
No. The migration happened automatically, starting on August 3, 2026. The migration will take a few weeks to roll out to all users. All of your projects are now folders with the same name, files, and members as before.
Yes. Any links you've shared to projects will continue to work and will open the corresponding folder.
Folders can now be nested
On paid plans, you can now create folders inside other folders, up to 10 levels deep. Starter plans support only one folder.
This gives you more flexibility to group together related work.
Learn more about creating and nesting folders.
Yes. Files and folders inherit permissions from their parent.
See File and folder permissions to learn how inheritance works and how to limit access to specific folders.
On the Professional, Organization, and Enterprise plans, you can create unlimited folders and can nest folders up to 10 levels deep. On the Starter plan, you can create one folder.
Folder permissions have been simplified
A folder's permissions depend on where it sits in your folder structure:
- Top-level folders follow team permissions. Anyone on the team can access it based on their team permissions or role.
- Nested folders inherit permissions from their parent folder—whoever has access to the parent also has access to it.
On Organization and Enterprise plans, you can limit any folder (top-level or nested) to specific people.
On Professional plans, you can limit a top-level folder to specific people, but nested folders always inherit from their parent.
What's changed
Previously, each project (now folder) had a "Team Access" setting with three options:
- Same as team: members accessed the folder based on their team permissions
- View only: all team or plan members could view the folder, regardless of their role
- Disable: access was limited to people explicitly invited
These settings have been replaced by two states:
- Inherited (”Anyone in [Parent name] can access”): the folder inherits access from its parent. For top-level folders, this means access follows team permissions. This replaces "Same as team."
- Limited (”Only people added to [Resource name] can access”): you've restricted access to specific people. This replaces "Disable."
The "View only" setting no longer exists. During the migration, team or plan members who previously had view-only access to a folder were added as individual viewers on that folder.
If a folder had 'View only' access, you may now see more individuals with can view access listed in the share modal. These are the same people who had access before—just listed individually now instead of through the 'View only’ setting.
No. Permissions were migrated automatically starting on August 3, 2026. It will take a few weeks to roll out to all users. Once migrated, your existing access levels are preserved.
If a folder previously had "View only" team access, the team members who had that access were added as individual viewers during migration. Their access level hasn't changed, it's just more explicitly stated now.
Changing inherited permissions on a nested folder is only available on the Organization and Enterprise plans.
On the Professional plan, you can’t change inherited folder permissions on nested folders. Anyone who was directly invited to a parent folder will get access to any nested folders.
Other changes for Starter and Professional plans
A few additional changes for the Starter and Professional plan are also part of this update:
- Choose a new member’s seat right when you invite them. When an admin invites someone to the Professional plan by email, they can set that person's seat type (Full, Collab, Dev, or View) up front, instead of the person defaulting to a View seat and needing an upgrade later. Joining the plan doesn't automatically grant access to folders or files—new members still need to be given access to specific content. Learn more about inviting users to your Professional plan.
- One role manages the whole plan. Starter and Professional plans consist of only a single team. These teams are managed by admins, and no longer have a separately listed “team owner”. If you're the only admin and want to leave the team, you'll need to promote another member to admin first. Learn more about transferring team ownership.
- See who has limited access at a glance. Anyone invited to specific folders or files, rather than the full plan, is now badged as "Limited Access" in your team members list, so you can tell them apart from full plan members. Guests on Organization and Enterprise plans aren't affected. Learn more about limited access members.