Organization plan permissions

Who can use this feature

Applies to organizations on the Organization 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
• Authenticate members with your identity provider (SAML SSO)

Organization

Organization admins can use account types and roles 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.

Role

Figma design and FigJam roles controls what activities a person can do in those files. It also controls their billing status. There are three roles: viewer, viewer-restricted, and editor.

Editors are considered paid seats in an organization’s billing, but viewers and viewer-restricted are not.

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.

Teams

Teams in an organization have an Organization access setting. This controls how members of the organization can find and join the team. There are three access levels:

• Open: members join open teams with can view permissions. Members can also be invited to any time with either can view or can edit access.
• Closed: members can request to join closed teams with either can view or can edit access. A team admin can accept or reject their request.
• Secret: members can only be invited to secret teams. Members and guests can be invited with either can view or can edit access.

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 role. 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.

Action	Can view	Can edit	Team admin
Invite others to the team or team files and projects	With can view permissions only	✓	✓
Share files from their drafts	With can view permissions only	✓	✓
Create projects	✕	✓	✓
Move files and projects	✕	✓	✓
Delete team files or projects	✕	✓	✓
Update team and project names or descriptions	✕	✓	✓
Remove members from the team	✕	✓	✓
Change the team name, icon, or description	✕	✓	✓
Update collaborator permissions on a team, project, or file	✕	✓	✓
Manage team settings	✕	✕	✓
Manage Community profile for team	✕	✕	✓

Projects

Every project has a team access setting. This determines what access team members have to that project.

In an organization, you can change a project's team access setting to create view-only or invite-only projects. Only the project owner can update the project's team access setting.

• Can view: Team members can only view files in this project, even if they have can edit permissions on the team. The project owner can allow team members and external collaborators to edit the project by inviting them to the project with can edit permissions.
• Can edit (default): Team members can access projects based on their team-level permissions and their FigJam or Figma design role.
• Invite-only: team members don't have access to private projects. Team members can only access invite-only projects if the project owner invites them. Invite-only projects are useful for projects that need a smaller group of collaborators, or for confidential products or features. For example: team members that manage a team's design system.

Team files

On the Organization plan, access to team files is based on a person's team permissions. Whether they can actually edit the file depends on their design or FigJam role.

• Prototype permissions: You can also set additional permissions for prototypes: Can view prototypes only and Cannot access. The invitation defaults to Can view prototypes only.
• 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 Organization plan, you have the following link sharing settings.

Access	Can edit	Can view	Can view prototypes only
Anyone with the link: anyone inside or outside your team or organization can access the file if they have the link.	✕	✓	✓
Anyone with the link and password: people without a role on the file can access the file using the link and password.	✓	✓	✓
Anyone at organization with the link:  only members of the organization can access the file. Members can only access the file is they open a link to that file.	✓	✓	✓
Anyone at 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 people invited to this file: only people you explicitly invite to the file, or the team it lives in, can access the file.	Access based on user's permissions

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 role shares a file from their drafts, this is considered an upgrade action. They will get an editor role based on the file type they shared. For example: if they shared a FigJam file, they'll get an editor role on FigJam.