Related Videos

• Manage teams in an organization

  Before you start

  Who can use this feature

  Available on the Organization and Enterprise plan.

  Admins only.

  Who can manage teams in an organization?

  Organization admins

  Organization admins have the highest level of access in an organization. From the Teams tab in Admin settings, they can:

  • Join any open or closed team as a team admin.
  • Update a team without joining it first, including the team’s:
    • Name
    • Access settings
    • Members and their permissions on the team
    • Icon
    • Description
  • See the name of any secret teams in the organization.
  • Join any secret team without an owner.

  Note: Organization admins can’t edit view-only projects or access invite-only projects. They can’t manage secret teams unless they are invited to the team as a team admin.

  Workspace admins (Enterprise plan only)

  Workspace admins and organization admins have the same abilities when managing teams. While organization admins can manage teams across the entire organization, workspace admins can only manage teams in workspaces where they are an admin.

  Team admins

  A team admin can manage all the settings of a single team, including people, resources, and access to the team within the organization. They can also delete the team.

  Manage teams in an organization

  Create or delete teams

  • Create a team
  • Manage who can create a team*
  • Delete a team

  Manage people in a team

  • Invite members to a team
  • Invite guests to a team
  • View members of a team
  • Change a person’s permissions on a team
  • Remove someone from a team
  • Change the owner of a team

  Manage resources in a team

  • Move files and projects to a different team
  • Manage libraries in teams
  • Upload custom fonts to a team
  • Transfer ownership of projects and files in a team

  Manage access to a team

  • Change a team’s access settings
  • Set default permissions to a team
  • Assign teams to a workspace* 
  • Move teams between workspaces* 
  • Unassign a team from a workspace*
  • Transfer a team to a different company

  Manage team settings

  • Upload a team icon
  • Rename a team
  • Edit a team’s description
  • Manage a Community profile for a team

  *Only available on the Enterprise plan.

• Manage who can create a team in an organization

  Before you start

  Who can use this feature

  Available on the Enterprise plan.

  Organization admins only.

  Restricting who can create a team gives organization admins more control over how an organization grows over time.

  There are two options for managing who can create teams:

  1. Anyone: Any member of this organization can create teams
  2. Admins only: Only organization and workspace admins can create teams

  When you limit team creation to admins only, the option to create a new team will be deactivated for all members.

  

  Change who can create teams

  1. Click on Admin settings in the file browser.
  2. Select the Settings tab.
  3. Under Team management, click on Creating teams.
  4. Choose a setting and press Save.
• Manage drafts of deleted members

  Before you start

  Who can use this feature

  Supported on the Organization and Enterprise plans.

  Only organization admins can view and manage deleted drafts from Shared projects.

  When you remove a member from the organization, their drafts are automatically added to a new project in Shared projects. The project will be named something like Name's (email@address.com) deleted drafts.

  To restore the drafts and continue making edits, you need to move the whole project, or individual files, from Shared projects.

  Move a project from Shared projects

  1. From the file browser, click Shared projects.
  2. Find the member's project you want to restore.
  3. Right click on the project name and select Move project.
  4. Choose a location for the project.

  Tip: You can rename the project before moving it.

  Move a file from Shared projects

  1. From the file browser, click Shared projects.
  2. Find a member’s draft you want to restore and click into it.
  3. Click an empty spot on the canvas to deselect any layers.
  4. Click the  icon next to the file name and select Move to project…
  5. Search for a project or choose from the default options.
  6. Click Move.
• Transfer a project or team to a different company

  Before you start

  Who can use this feature

  People on the Professional, Organization, and Enterprise plans can initiate project or team transfers. Only organizations on the Organization or Enterprise plans can receive a project or team.

  Only admins can send or accept a transfer request.

  Figma lets you transfer projects or teams between different companies. For example: If you work at an agency, you can transfer assets to a client after work has completed.

  Note: If you are on the Professional plan and transfer your paid team, we’ll automatically refund any remaining time on your plan. For example: If you transfer your team halfway through a monthly billing period, we will refund the second half of the month to your credit card.

  Project or team transfers include the following resources:

  Resource	Included
  Files	✓
  Prototypes	✓
  Branches	✓
  Comments	✓
  File history	✓
  Components in files where the library is included in the transfer	✓
  Components in files where the library is not included in the transfer	Components will show the last known state before the transfer and will not receive updates afterwards
  Shared fonts	X
  Private plugins	X
  Published Community resources	X

  Note: You can keep accessing files and prototypes at their original links after the transfer is complete. Projects and teams will get new links in the destination organization.

  There are three steps to transfer a project or team between organizations:

  1. Choose where to send the project or team
  2. Send a transfer request
  3. Accept the transfer request

  1. Choose a location for the project or team

  Before you can move a project or team between organizations, Figma needs to know where the resources should go.

  A person at the company who receives the project or team needs to provide a destination URL.

  When receiving a project

  

  1. Log in to your organization in a web browser.
  2. Navigate to the team the project will move into.
  3. Copy the entire URL in your browser address bar.
  4. Send this URL to the person at the other company.

  Tip: You can always move the project to a different team later.

  When receiving a team

  

  1. Log in to your organization in a web browser.
  2. From the file browser, click All teams or All workspaces.
  3. Copy the entire URL in your browser address bar.
  4. Send this URL to the person at the other company

  Note: Any team you transfer between two Figma organizations will keep its access settings, whether that's open, closed or secret.

  2. Send a transfer request

  The admin from the company sending the project or team starts the transfer process.

  Caution: If you transfer a file that contains a published library, other files in your organization won’t receive updates from this library after the transfer is complete. We recommend keeping libraries and their files together.

  1. In the file browser, navigate to the project or team you want to transfer.
  2. Click the Settings tab.
  3. In the Transfer or delete section, select Transfer ownership of this project or Transfer ownership of this team.
  4. Review the information in the modal and press Next.
  5. Enter the destination URL and email address of your contact at the other company and press Request transfer.

  We’ll send an email to your contact and all organization admins in the other organization so they can accept the transfer.

  You will receive an email when the transfer is complete.

  Tip: Organization admins can request a team transfer from Admin settings:

  1. Open the file browser.
  2. Select Admin settings in the sidebar.
  3. Click the Teams tab and navigate to the team you’d like to transfer.
  4. Press the More menu and select Transfer team.

  3. Accept a transfer request

  Caution: When you accept a transfer request, it takes around 5 minutes to move the project or team between companies. Members of the project or team won’t be able to use certain features of Figma during this time. We recommend accepting the transfer at a time that will cause minimal disruption to members of the project or team.

  When an admin at another organization sends you a transfer request, Figma will ask you to review and accept the transfer. After you accept, the project or team will get added to your organization.

  The transferred project or team includes its current files and members. Members from the sending organization will get added to your organization, which may add more paid editors to your billing plan. You can manage these editors after the transfer is complete.

  Additional considerations for admins on the Enterprise plan:

  • If you have restricted guest access and there are guests in the team being transferred, they won’t transfer with the team.
  • If you have set default roles so new members are given the Viewer-restricted role, any new people created in your organization during the transfer will get this role, even if they were previously Editors on the team.
  • If you have workspaces enabled, you’ll need to manually assign the team to a workspace after the transfer is complete.
• Manage default libraries for a workspace

  Organization and workspace admins can enable libraries by default for all files in a workspace. This helps people access a library’s components and styles in their Figma Design and FigJam files, without having to manually search for and add the library.

  If you choose not to enable a library by default for a workspace, people in the workspace can still manually add the library to their files. Learn more about libraries →

  Understanding default libraries in workspaces

  

  Every library can be enabled by default for the organization by an organization admin. Most libraries aren’t enabled by default, so this setting is usually set to Off. Organization and workspace admins can override this setting to enable a library by default for a specific workspace by selecting one of the following:

  • Off: The library is not a default library for a specific workspace. You might use this setting to turn off a library that has been enabled by default at the organization level. A library with this option applied can still be enabled by default for individual teams within the workspace.
  • All files: Enables the library by default for both Figma Design and FigJam files in the workspace.
  • Design files: Enables the library by default only for Figma Design files in the workspace.
  • FigJam files: Enables the library by default only for FigJam files in the workspace.

  Note: You can update this setting at any time. Changing the setting does not affect anyone’s ability to manually access the library. If you want to remove access to a library, you can unpublish it.

  Configure a default library for a workspace

  Workspace admins Organization admins

  1. From the file browser, click Admin settings.
  2. Select the Libraries tab.
  3. Navigate to, or search for, the library you want to manage and click it.
  4. Select the workspace you want to enable the library for.
  5. Choose one of the options: Off, All files, Design files, or FigJam files.

  1. From the file browser, click Admin settings.
  2. Select the Resources page and then the Libraries tab.
  3. Navigate to, or search for, the library you want to manage and click it.
  4. Select the workspace you want to enable the library for.
  5. Choose one of the options: Off, All files, Design files, or FigJam files.

  Caution: The Libraries tab contains a list of all the libraries you have access to in the organization. You can enable any library in the list as a default for a workspace.

  This includes libraries where access may be restricted, such as those in closed or secret teams.

  If the library file isn’t shared with everyone in the organization, you’ll see the following warning:

  

  If you enable the library by default for the workspace, Figma will publish the library to the organization and modify the permissions on the file for you.

  Review a list of default libraries for a workspace

  You can check how many libraries have been enabled by default for a specific workspace:

  Workspace admins Organization admins

  1. From the file browser, select Admin settings.
  2. Click the Libraries tab.
  3. Click Filters and select one or more workspaces to review.

  1. From the file browser, select Admin settings.
  2. Click Resources and then the Libraries tab.
  3. Click Filters and select one or more workspaces to review.
• Upload custom fonts to an organization

  Who can use this feature

  Supported on the Organization and Enterprise plans.

  Only organization admins can upload fonts to the organization. Only team admins can upload fonts to a team.

  Figma supports .TTF and .OTF fonts. Webfonts are not supported.

  Organizations can upload custom fonts to use across organization files. Upload fonts in a specific team, or upload them to the organization.

  There's no need to share, install or update fonts for individual users. This also allows Chromebook and Linux users to access custom fonts.

  You can only upload fonts in .TTF and .OTF format. It's not possible to upload or install web fonts. Access any fonts on your computer via the Figma Desktop app or Figma Font Helper.

  Warning: Admins should only upload fonts they own or have a license to use in Figma. Find out more in the Content and Content rights section of Figma’s Terms of Service

  Entire organization

  Any fonts you upload to the organization will be available to everyone. Members of any team in the organization can access and use these fonts.

  Only organization admins can upload fonts to the organization.

  1. Open Figma in the organization workspace.
  2. Select Admin settings in the left sidebar.
  3. Select Resource and then Shared fonts:
  4. Click Upload fonts
  5. Select the font file from your computer. You can upload multiple font files at once. Click Open to select the fonts.
  6. Confirm you have the necessary rights and licenses to use the font(s). Click Upload to start the upload process. The font will now be available in the font picker for files in the Organization.

  Note: Figma will let you know if you already have fonts uploaded with that font family name. Click Skip to leave the font out of the upload, or Replace to update the existing font.

  Specific team

  Only team admins can upload fonts to a team.

  1. Open Figma in the organization workspace and select the team in the sidebar.
  2. Select the Settings tab.
  3. Click Manage shared fonts.
  4. Figma will show you a list of all the fonts available in that team, including the Font Family, Style, Version and a Sample of the font.
  5. Click in the top-right corner to add a font.
  6. Select the font file from your computer and then Open to select. You can select as many font files as you want.
  7. Check the box to confirm you have the necessary rights and licenses to use the font(s).
  8. Click Upload to start the upload process. The font will now be available in the font picker in any files in that team.
• Claim ownership of a project

  Before you start

  Who can use this feature

  Supported on Organization and Enterprise plans.

  Only the owner or a team admin can claim ownership of a project.

  If there is no longer an owner of a project, the Team Owner or a Team Admin can join the project as the owner.

  This applies to:

  • Projects shared with the entire Team without an Owner
  • Private projects without an Owner
  • View-only projects without an Owner

  Claim ownership of a Project

  Note: If the Team also has no owner, an organization admin or workspace admin can claim ownership of the Team. This allows them to manage aspects of the Team, including the ownership of abandoned Projects.  

  1. Click on the team name in the file browser.
  2. Select the project from the grid or list.
  3. Click the Join as Owner button.

  Once you have joined the project, you can:

  • Move project between teams
  • Transfer ownership of the project
  • Delete project