Before you start
Who can use this feature
Supported on the Organization and Enterprise plans
Organizations go beyond the set up of individual teams. They're fantastic for established or growing businesses that need to share resources across a number of teams.
Plan specific features
There are two organization plans: Organization and Enterprise. Your organization account will look mostly the same on both plans, with a few differences that we'll cover in this article. Explore your organization account →
One of the biggest differences is your team hierarchy. The Enterprise plan support workspaces, which add another layer of structure within an organization. Check out the diagrams below to see how workspaces impact your organization.
Another difference is what features you can use:
|Feature||Organization plan||Enterprise plan|
|Share organization-wide libraries||✓||✓|
|Track library analytics||✓||✓|
|Create and merge branches||✓||✓|
|View organization activity logs||✓||✓|
|Registered domains and domain capture||✓||✓|
|Set default roles||✕||✓|
|Restrict guest access||✕||✓|
|Authenticate members using SAML SSO||✓||✓|
|Provision users with SCIM||✓||✓|
|Set member roles with SCIM||✕||✓|
If you're on the Enterprise plan, your organization will have workspaces! Workspaces are collections of teams, people, and resources. They add another layer of structure within organizations.
Workspaces could be different teams, departments, cost centers, or business units within your organization.
You can only be assigned to one workspace at a time. When you are assigned to a workspace, you'll be added to any default teams. You can view and join teams outside your workspace. As well as browse and access libraries in other workspaces.
Organization admins create workspaces and assign dedicated admins to each workspace. They can then assign both teams and members (including guests) to workspaces. You might see a workspace selector when you join the organization, asking you to select your workspace.
On team plans, you have to be invited to a team before you can access it in your account. In an organization, you can view all teams in the organization and join the ones relevant to you.
You can also create as many teams as you need within an organization. You can map teams to your company's hierarchy, or create cross-functional teams for company-wide projects.
Members of the organization can find and access teams with the access within organization setting. There are three levels of organization access: open, closed, and secret.
Teams in organizations also have access to extra features, like library analytics, which allows you to track component usage across teams.
You can share organization-specific resources with other members of your team. This includes style and component libraries, custom fonts, and private organization plugins.
- Upload brand-specific fonts and share them with members across your organization.
- Share organization files with peace of mind with organization-specific link sharing settings.
- View and install private organization plugins
Members and guests
Everyone in an organization has an account type. A person's account type determines what they can access within the organization.
This includes organization-wide resources, like teams, libraries, plugins, and widgets. It also includes features and functionality, like branching, library analytics, and shared fonts.
Members are people in the organization that have an email address that matches any of the organization's domains. Members can access teams, libraries, and other resources shared within the organization.
Twigma has the
dev.twigma.com domains registered to their organization. Anyone that joins the organization with a Twigma email address (
firstname.lastname@example.org) is a member.
Guests are external users with email addresses that don't match any of the organization's domains. They could be contractors, agencies, clients, or external collaborators. Guests have limited access to the organization. They can only resources to which they're invited. They can't browse organization teams or access shared resources like fonts, plugins, or library analytics.
Twigma has the
twigma.com domain registered to their organization. They work with an agency called DsgnSystm who they invite to a specific team in the organization. As collaborators from the agency only have
dsgnsystm.com emails, not
twigma.com emails, they are guests. They can't access any teams or resources outside the team they’re invited to.
Your role controls what activities you can do in design or FigJam files. It's also determines if you're included in the organization's billing.
There are three roles: viewer, viewer-restricted, and editor. You can have a different role on each product. Roles in Figma →
If you have an editor role on a product, you can edit that kind of file. You'll also be included in the organization's billing. If you're not an editor, you can request an editor upgrade from an admin.
On an organization plan, your team, project, and file permissions also affect what you can access. Team permissions →
Admins are members that have extra administrative rights within an organization. There are two types of admins in an organization: organization admins and workspace admins.
Organization admins manage all aspects of the organization. This includes everything from members and resources, to billing and other organization-wide settings.
Workspace admins (Enterprise plan only) manage their specific workspace(s). They can manage roles for workspace members, set and assign default teams, and help with billing true-ups.
Organization admins can access the organization's admin settings. They can adjust members, view teams, monitor activity, manage billing, and configure security settings.
Organization admins don't have the ability to manage teams in the organization. You need to be a team admin to manage a team. Organization admins can view a list of open, closed, and secret teams.
Organization admins can claim ownership of empty teams, and perform limited bulk actions.
There are three roles: viewer, viewer-restricted, and editor. People can have a different role on each product. Roles in Figma →
A person's role determines if they're included in the organization's billing. Anyone with an editor role is included in the organization's billing.
- Billing on the Organization plan
- Billing on the Enterprise plan
- Manage organization true-ups
- Manage true-ups with workspaces
Organizations that need enhanced security requirements can configure SAML SSO in Figma. Get started with our Guide to SAML SSO in Figma →
- Security Assertion Markup Language (SAML) is a security standard for logging into applications.
- Single Sign On (SSO) allows users to log into many applications or websites via one set of login details.
You can set up SAML SSO with one of our dedicated providers:
- SAML SSO with Okta
- SAML SSO with OneLogin
- SAML SSO with Azure Active Directory
- Set up SAML SSO for ADFS
If your provider isn't listed above, you can set up a custom SAML SSO configuration: