Enterprise plan permissions
Who can use this feature
Applies to organizations on the Enterprise plan.
On the Organization plan, you can share assets at five different levels: organization, team, projects, files, and prototypes. As this is a paid plan, you also have access to these extra sharing settings:
- Share just a prototype and not the file
- Restrict viewers from copying, sharing, or exporting
- Add password protection to files
- Grant access to members with SAML SSO
- Restrict or prevent guest access
- Set default seat types for Figma design and FigJam
Organization
Organization and workspace admins can use account types and seat types to manage access to the organization. Any access to individual teams, projects, or files is controlled by their permissions ↓.
Account type
A person’s account type controls what resources and settings they can access. There are three account types: members, guests, and admins.
Note: You can only invite guests to teams, projects, or files within the organization. You can't invite them to the organization. Members versus guests →
Seat type
Figma design and FigJam seat types control what activities a person can do in those files. It also controls their billing status. There are three seat types: viewer, viewer-restricted, and full. The full seat type is considered a paid seat in an organization’s billing, but viewers and viewer-restricted are not.
On the Enterprise plan, organization admins can set default seat types for people joining the organization. This helps organization admins to better control and manage new paid seats. Default seat types apply to both members and guests. You can set default seat types for both Figma design and FigJam files.
Permissions
A person's permissions control their access to individual teams, projects, and files within the organization.
Read our Guide to sharing and permissions for more information on how sharing works in Figma.
Workspaces
Workspaces are collections of teams, people, and resources within an organization. They help companies with business units, sub-brands, or design systems add structure to their Figma organization.
Only organization admins and workspace admins can manage workspaces.
- Organization admins can create workspaces and assign workspace admins to each workspace.
- Workspace admins have a level of access below organization admins. Workspace admins manage teams, members, and guests in their workspaces. They can't manage any organization-wide resources or settings.
You can assign both teams and people to workspaces. A person or team can only belong to one workspace.
Workspaces don't have permissions of their own, so members can still view and browse other workspaces in the organization. They can access teams based on their team permissions or the team's organization access.
Teams
Teams in an organization have an audience access setting. This controls how members of the organization can find and join the team.
- [Organization name]: Anyone in the organization can access the team.
-
Only those invited: Only users explicitly invited to the team can access it. If the team is limited to Only those invited, you’ll need to choose from one of the following visibility options:
- Visible: The team can be found by organization members from the file browser. Members can ask for permission to join a visible team.
- Hidden: The team cannot be found by search. Members must be invited by an existing member.
Organization members can join multiple teams in the organization. To control what access each member has to the team, they have team permissions.
Team permissions are the same across all team types: can view
, can edit
, andadmin
. Teams also have one owner
.
In an organization, team permissions only control what team-level actions people can take. Whether someone can edit files depends on their FigJam or Figma design seat type. This is set at the organization↑ level.
Team actions
This table includes a list of common team-level actions and tasks in Figma. Use the icons to see if someone with that permission can ✓ or can't ✕ perform that task.
Note: If organization audience access is set to anyone in [Organization name] can edit, then anyone in the organization can perform can edit actions, regardless of team roles.
Action | Can view | Can edit | Team admin |
With can view permissions only |
✓ | ✓ | |
With can view permissions only |
✓ | ✓ | |
✕ | ✓ | ✓ | |
✕ | ✓ | ✓ | |
✕ | ✓ | ✓ | |
✕ | ✓ | ✓ | |
✕ | ✓ | ✓ | |
✕ | ✓ | ✓ | |
✕ | ✓ | ✓ | |
✕ | ✕ | ✓ | |
✕ | ✕ | ✓ |
Projects
In addition to audience access settings, every project has a team access setting. This determines what access team members have to that project.
In an organization, only the project owner or those with can edit
permission can change a project's team access.
-
Can view: Team members can only view files in this project, even if they have
can edit
permissions on the team. -
Can access (default): Team members can access the project based on their team-level permissions. For example, if a user has
can view
team permissions, and the team access level for the project is set tocan access
, then the user hascan view
access on the project. - Remove team access: Remove a team’s access to a project. If you remove a team’s access to a project, team members can only access the project if they have already been directly invited or if project owner invites them afterward. You can re-add team access to the project at any time.
Team files
On the Organization or Enterprise plan, access to team files is based on a person's team permissions. Whether they can edit the file depends on their Figma design or FigJam seat type.
-
Restrict viewer actions: By default, anyone with
can view
access to the file will be able to copy and share the file and its contents. On paid plans you can restrict viewers from copying, sharing, or exporting from the file. -
More link sharing settings: Team files also have default permissions for link sharing. Anyone who accesses a file from a link gets those permissions. Files in an organization have extra link sharing options, to make it easier to find and access organization resources.
There are two aspects of link sharing: access and permissions. On the Enterprise plan, you have the following link sharing settings.
Access |
Can edit |
Can view |
Anyone: Anyone inside or outside your team or organization can access the file if they have the link. |
✓ |
✓ |
[Organization]: Organization members can find this file when browsing and searching. Use this setting to share libraries with the organization. Guests can't access these files unless you invite them to the file or team. |
✓ | ✓ |
Only invited people: Only people you explicitly invite to the file, or the team it lives in, can access the file. |
Access based on user's permissions |
Note: If you set file access to Anyone, use the Advanced options in the Share modal to add password protection to the file. Learn more about sharing files and adding password protection to files.
Drafts
Everyone has access to draft files, which are separate from their team files and projects. On the Organization plan, people can invite collaborators to files in their drafts with can view
or can edit
permissions.
If someone with a viewer seat type shares a file from their drafts, this is considered an upgrade action. They will get a paid seat based on the file type they shared. For example: if they share a FigJam file, they'll get a paid FigJam seat.
Note: Drafts are owned by the organization. When a member leaves, the organization can claim ownership of any draft files.