Figma SSO through SAML is only on the Organization and Enterprise plans. Organization is $55 per Full seat a month, billed annually only, against $16 on Professional. That's $39 more per designer a month, or $468 a year, before you count anyone else.
Prices are from Figma's pricing page in US dollars, as we read it on 27 October 2026. The good news buried in Figma's seat model: people who only view and comment cost nothing on either plan, so the bill depends on how many people actually make things. Here is how the plans, seats and SSO fit together, what else Organization buys you, and how to manage a Figma team by hand.
Figma plans and SSO
| Plan | Full seat | Dev seat | Collab seat | SAML SSO | SCIM |
|---|---|---|---|---|---|
| Starter | Free | Free | Free | No | No |
| Professional | $16 annual, $20 monthly | $12 annual, $15 monthly | $3 annual, $5 monthly | No | No |
| Organization | $55, billed annually | $25 | $5 | Yes | Yes, without seat roles |
| Enterprise | $90, billed annually | $35 | $5 | Yes | Yes, with seat roles |
All prices are per seat a month. Figma's comparison table lists "Single sign-on (SSO)" as included on Organization and Enterprise and not on Starter or Professional. Its help article, Guide to SAML SSO, agrees: "Available on the Organization and Enterprise plans," set up by organization admins only.
Admins choose whether SAML is required or whether members can still use email and password. Figma recommends leaving it open while you test. One exception holds whatever you choose: the same guide says guests "can log in via Google SSO or their email and unique password, regardless of an organization's SAML SSO settings." Required SAML covers your members, not the freelancers and clients you invite.
Google sign-in follows the same plan line. Figma's Google SSO article lists the Organization and Enterprise plans (and K-12 Education). Organization admins can require "Members must sign in with a Google Account" or leave it optional. Professional isn't mentioned, and we found no login controls documented for Professional admins.
SCIM on Organization: half the job
SCIM is the standard identity providers use to create and remove accounts in apps (our post on SCIM vs SAML explains how it differs from the login). Figma's SAML guide, as we read it on 27 October 2026, says SCIM "pushes changes immediately and allows you to import and deactivate users," and names dedicated integrations for Microsoft Entra ID, Okta, OneLogin, Google Workspace and AD FS, with custom SAML for anything else.
The catch is seats. On Organization, the guide says, "it's not possible to assign a person's seat type outside of Figma," and everyone who joins gets a free View seat. "Role assignment via SCIM" is an Enterprise line on the pricing page. So on Organization your identity provider can add people and take them away, but someone in Figma still decides who gets a paid Full, Dev or Collab seat. Removal is the half SCIM does well; the expensive half, seat decisions, stays manual.
What else Organization gets you
Organization is sold as more than a login upgrade, and some teams buy it for the rest. Its key features on the pricing page are publishing resources across teams, shared libraries and fonts, and centralized admin tools. It also brings domain capture, which adds anyone with a verified email address on your domain to your Figma account automatically, and centralized billing across teams.
Activity logs are the other one worth knowing about. Figma's activity log article, as we read it on 27 October 2026, lists them on Organization, Enterprise, Government and K-12 Education, viewable by organization admins and exportable as CSV. Logging only starts when you upgrade; history from before can't be added afterwards, and logs for members you've removed can't be reviewed. If an auditor will one day ask who opened which file, the clock starts on upgrade day.
Some controls you might expect stay above Organization. Figma's idle session timeout, which logs out inactive members, is an Enterprise feature. So is setting seat types through SCIM.
If your designers work across several teams and fight over which library is current, Organization may be worth it on those grounds alone. If SSO is the only reason, read on.
Editor seats vs viewers
Figma no longer has "editors" and "viewers" in the old sense. It has seats. A Full seat gets everything, including editing in Figma Design, Make, Sites and the rest. A Dev seat gets full Dev Mode, plus FigJam and Slides, and can view and comment in design files. A Collab seat gets FigJam, Slides and the other collaboration products, and can also view and comment in design files. And a View seat is free: Figma's seat article calls it "a free View seat", letting people view and comment in files they can reach, with basic inspection.
The pricing page puts it plainly: on a paid plan "you can let others view and comment on your files without purchasing extra seats." Seat requests can be set to manual approval, manual unless a seat is free, or auto-approve. If you care about the bill, don't pick auto-approve.
So the honest answer to "do viewers count for SSO pricing?" is no. On Organization, SSO covers everyone who signs in, viewers included, and you pay only for Full, Dev and Collab seats.
The price jump
If everyone in a team had a Full seat, the jump would look like this:
| Tool | Plan without SSO | Cheapest plan with SSO | Extra a year, 20 people |
|---|---|---|---|
| Figma | Professional · $16 a seat | Organization · $55 a seat | $9,360 |
| Total SSO tax a year | $9,360 | ||
That's a worst case. Most 20-person companies don't have 20 designers. Here is the yearly cost of Full seats at 10, 20 and 50, and then a more realistic mix:
| Full seats | Professional, annual | Organization | Extra for SSO, annual | Extra for SSO, from monthly Professional |
|---|---|---|---|---|
| 10 | $1,920 | $6,600 | $4,680 | $4,200 |
| 20 | $3,840 | $13,200 | $9,360 | $8,400 |
| 50 | $9,600 | $33,000 | $23,400 | $21,000 |
The sums: $55 minus $16 is $39 per Full seat a month, $468 a year. Organization has no monthly option, so if you pay Professional monthly at $20, the gap is $35 a month, or $420 a year, and you also commit to a year.
Take a 20-person company with 4 designers on Full seats, 6 engineers on Dev seats, and 10 people viewing for free. On Professional, billed annually, that is (4 × $16 + 6 × $12) × 12 = $136 × 12 = $1,632 a year. On Organization it is (4 × $55 + 6 × $25) × 12 = $370 × 12 = $4,440 a year. The extra for SSO is $2,808 a year, a 172% increase on the Figma bill.
That's the SSO tax in Figma's shape: smaller than the headline when most people only view, still steep for anyone who builds. Our post on per-seat pricing explains why the multiplier matters more than the sticker price.
One billing detail to check on Professional: seats added partway through an annual subscription are charged as a separate monthly subscription at the monthly price, until you add them to the annual plan or remove them.
Managing Figma members by hand
On Starter and Professional, team admins manage people from the team itself. To remove someone from a team, go to the file browser and choose All folders in the left sidebar. Open the team dropdown next to the team name and choose View members. Then open the dropdown next to the person's name and click Remove.
Figma "revokes their permissions and any access to files and folders they had through the team or plan." There is no team owner role on Starter and Professional, so you can remove anyone without transferring anything first.
Their work doesn't vanish. Folders and files they owned become ownerless, and everyone who had access keeps it; give someone "can edit" to get the same control back. On paid plans, their drafts move to Unassigned drafts under Admin > Content. On Starter, drafts are deleted, so export anything you need before you remove a Starter user.
Three things are easy to miss. People with file or folder access who aren't team members are handled separately from the team member list, so check shared files for outside email addresses; that is where agency designers and clients tend to live, and our guide to contractor access management covers keeping them in check. The seat itself is the second: instead of removing someone, you can move them to the free View seat, which frees the paid seat. On an annual Professional plan, unused seats are only dropped at renewal, and Figma shows a banner in your admin 30 days before; on a monthly plan, unassigned seats simply don't renew. Several teams are the third. Figma says "The Professional plan includes a single upgraded Figma team," so if you run more than one paid team, a leaver may need removing from each.
Alternatives
If SSO is the only reason to move to Organization, there are cheaper ways to get most of the benefit.
Stay on Professional and keep the seat list honest. Approve seats by hand, move occasional users to View, and remove leavers the day they go. Our post on SaaS license management covers the habit of paying only for seats in use.
Protect the accounts at the Google end. You can't force Google login below Organization, but if your team signs up with Google Workspace addresses, make sure those accounts have two-step verification on, and suspend a leaver's Google account the day they go so Figma's password-reset emails stop reaching them.
Review access every quarter. A short user access review of Figma catches outside collaborators and forgotten seats before they show up on another renewal.
Automate the adding and removing. That's the part SSO doesn't fully do on Organization anyway, at least not for seats. The rest of a leaver's tools are in our employee offboarding checklist.
Where SmashSSO fits
SmashSSO manages Figma membership from the same place as your other tools, on Professional. It reads your people from Google Workspace, reads who is in your Figma team and on which seat, and matches them by email; accounts that match nobody are flagged. When someone is suspended in Google Workspace, you get an alert listing Figma among the places they still have access. Access bundles let an "Engineer" bundle invite someone with a Dev seat and a "Designer" bundle with a Full seat.
Changes run through an agent in your own Chrome, in a tab where you're signed in to Figma as an admin. That needs the browser open; runs are slower than an API and can fail if Figma changes its screens, in which case the run reports the failure with its last screenshot. Any step that would add a paid seat stops for your approval, and every change goes in the audit log.
It is not SSO. If you need Figma logins enforced through an identity provider, that's Organization. If you need the right seats for the right people and nobody left behind, SmashSSO does it for a flat fee from $199 a month, billed annually, however many people and tools (pricing).