Before you start
Who can use this feature
Available on all plans
Only owners and those with can edit
permissions on a file or project can make changes to permissions on that file or project.
In Figma, you work in files, and files can be organized into projects. Projects are organized by team.
Learn more about sharing and permissions in Figma.
Project permissions
Permissions define who can access a file, project, or team—and what they can do with it. On a project, users can be assigned the following permissions:
- Can edit: Users can create and edit files in this project.
- Can view: Can only view the project. They cannot create files. Access to individual files is determined by file-level permissions.
- Owner: The person who created the project. They can create and edit files within it.
You can invite individuals to a project and assign them can edit
or can view
permissions.
Example
The Fruit Project contains two files: Apple and Banana.
Jesse is invited to the Fruit Project with can view
project permissions. This means he cannot create new files in Fruit Project. His access to the individual files depend on his individual file permissions.
- He has
can edit
permissions in the Apple file, so he can edit that file. - He has
can view
permissions in the Banana file, so he can only view that file.
On the other hand, Jules is invited to Fruit Project and given can edit
permission on the project. He can create new files in Fruit Project, and can edit both the Apple and Banana files by default.
To view a user’s project permissions:
- Open the file browser by logging in to your account at figma.com.
- If you’re in a specific Figma file, click the Figma menu > Back to files.
- Open the project page.
- On the Starter or Professional plan, select All projects from the left sidebar. Then, select a project.
- On the Organization or Enterprise plan, select All teams from the left sidebar. Select a team, then select a project.
- On the Enterprise plan with workspaces enabled, select All workspaces from the left sidebar. Then, select a team from the Your teams tab. Select a project in that team.
- Click Share to open the share modal, which lists all users and their project permissions.
No. Project permissions do not impact your Figma subscription. Your Figma subscription is determined by both your plan type, and the number of seats on your plan.
Learn more about billing at Figma and how to use seat approval settings to manage incoming seat requests.
Team access to projects
Projects live within teams and inherit team-level permissions by default.
Example
Fruit Project is in the Produce team.
- John has
can edit
team permissions on the Produce team. By default, he is givencan edit
project permissions on Fruit Project. - Jeanie has
can view
team permissions on the Produce team. By default, she is givencan view
project permissions on Fruit Project.
You can change the team-level access to a project by doing the following:
- Open the file browser by logging in to your account at figma.com.
- If you’re in a specific Figma file, click the Figma menu > Back to files.
- Navigate to the list of team projects:
- Starter or Professional plans: Select All projects from the left sidebar.
- Organization or Enterprise plans: Select All teams from the left sidebar. Then, select a team.
- Enterprise plan with workspaces enabled: Select All workspaces from the left sidebar. Then, select a team from the Your teams tab.
- Select a project.
- Click Share.
- From the share modal, select the team access level (labelled “Anyone in [Team Name]”).
- Click Change access.
- Select a new team access option for the project:
-
Same as the team: Project permissions are inherited from team permissions. If a user has
can edit
team permissions, they will havecan edit
project permissions. If a user hascan view
team permissions, they havecan view
project permissions. - View-only: All team members can view the project, but can’t create new files. Access to individual files depend on file permissions.
- Disable: Team members have no access unless individually invited.
-
Same as the team: Project permissions are inherited from team permissions. If a user has
Note: On the Starter plan, team access to projects is set to Same as the team by default. If you want to make projects with more private team access settings, you need to upgrade to a paid plan.
To see a user’s team permissions:
- Open the file browser by logging in to your account at figma.com.
- If you’re in a specific Figma file, click the Figma menu > Back to files.
- Open the team page.
- On the Starter or Professional plan, select All projects from the left sidebar.
- On the Organization or Enterprise plan, select All teams from the left sidebar. Select a team.
- On the Enterprise plan with workspaces enabled, select All workspaces from the left sidebar. Then, select a team from the Your teams tab.
- Select Open team dropdown next to the team name.
- Click View members to view a list of team members and their team permissions.
Organization access to projects
On the Organization and Enterprise plans, projects are created within teams, and teams are created within organizations.
When you create a project, you can set the organization access level to the project from the Who can access dropdown:
- Only those invited: Only people you've directly invited can access the project
- [Organization name]: Allows organization members to access the project via link or through the file browser
If organization access is allowed, choose a permission level under What they can do:
- View: Organization members can view and comment on files in this project.
- Edit: Organization members can create and edit files in this project, add members, and change members’ edit permissions.
To change organization access to a project:
- Open the file browser by logging in to your account at figma.com.
- If you’re in a specific Figma file, click the Figma menu > Back to files.
- Open the project page.
- On the Organization or Enterprise plan, select All teams from the left sidebar. Select a team, then select a project.
- On the Enterprise plan with workspaces enabled, select All workspaces from the left sidebar. Then, select a team from the Your teams tab. Select a project in that team.
- Click Share.
- From the share modal, select the organization access level (labelled “Anyone in [Organization name]” or “Only invited people”).
- Select a new organization access level for the project.
- Only those invited: Only people you've directly invited can access the project.
-
[Organization name]: Select your organization name to allow members to access the project via link or through the file browser. If you allow organization access to the team, you must set a permission level (”What they can do”):
- View: Organization members can view and comment on files in this project.
- Edit: Organization members can create and edit files in this project, add members to the project, and change members’ project permissions.
File permissions
The following file permissions determine what actions someone can take within a file:
- Can edit: Full editing capabilities.
- Can view: View-only access.
-
Owner: Has
can edit
access.
Use the table below to understand the difference between can edit
and can view
file permissions.
Action | Can Edit | Can View |
---|---|---|
Modify designs/components | Included | Not included |
Add comments | Included | Included |
View layer properties | Included | Included |
Copy/export assets | Included |
Included (unless copying and exporting is restricted) |
Tip: Review the “Who can use this feature” box at the top of each Figma Learn article to understand access for individual features.
By default, each resource inherits permission levels from their parent. This means that a file will inherit the permissions set on the project level, and a project will inherit permissions set on the team level.
However, you can override inherited permissions:
- Project-level changes override team settings
- File-level changes override project settings
Example
James has can view
permissions on the Product team. His manager, Vanessa, invites him to a specific file with can edit
access.
With explicit edit access to the file, James is able to make edits to that file. He only has view access to other files and projects in that team.
Seats are separate from permissions.
In Figma, a person's seat determines which Figma products they have access to. For example, a user with a Collab seat has access to FigJam and Figma Slides.
Permissions determine which files and projects they can edit.
For a user to be able to edit a file, they need both the appropriate seat and permissions.
Example
Ernie is a part of an organization, and has a Collab seat. The Collab seat gives Ernie access to FigJam and Figma Slides.
Ernie is invited to three files.
- Ernie is invited to File A, a Figma Design file, with can edit file permissions. Since his seat type does not give him access to Figma Design, he does not have edit access to the file. He would need to make a seat request in order to access the Figma Design file.
- Ernie is invited to File B, a FigJam file, with can edit file permissions. He can edit File B, since his seat gives him access to FigJam, and he also has can edit file permissions.
- Ernie is invited to File C, a FigJam file, with can view file permissions. He can only view File C, since he only has can view permissions on the file. He would need to request to edit the file in order to make changes.
To view permissions on an individual file:
- Open the file.
- Click the Share modal.
From the share modal, you can view a list of invited users and their file permissions.