Asana SSO through SAML is Enterprise only, and Enterprise has no public price: the pricing page says "Contact sales for custom pricing for your organization". What Starter and Advanced do include, on every paid plan, is the option to require Google sign-in (or Microsoft sign-in) for your whole organization.
That comes from Asana's pricing page and its help center, as we read them on 27 October 2026. For a small team, the Google option is the useful news; the Enterprise quote is the bad news. Below: the plans, what "contact sales" means for your budget, Google sign-in against SAML, how to remove people from Asana, what removal costs you if you forget it, and the alternatives.
Asana's plans and SSO
| Plan | Billed annually, per user a month | Billed monthly, per user a month | Require Google or Microsoft sign-in | SAML | SCIM |
|---|---|---|---|---|---|
| Personal | $0, up to 2 users | $0 | No | No | No |
| Starter | $10.99 | $13.49 | Yes | No | No |
| Advanced | $24.99 | $30.49 | Yes | No | No |
| Enterprise | Contact sales | Contact sales | Yes | Yes | Yes |
The Enterprise card lists "SAML authentication" and "User provisioning (SCIM)". Neither appears on Starter or Advanced. There's also an Enterprise+ tier for more compliance features, again through sales. The pricing page also puts "Guest invitation permissions" on Enterprise, and the Audit Log API sits in a compliance add-on for Enterprise. If you want to control who can bring outsiders into Asana, or feed Asana's activity into a security tool, that's Enterprise money too.
Asana's help article on authentication options for paid plans sets the SAML conditions: you must "belong to an organization or division on Asana Enterprise, Enterprise+, or Legacy Enterprise" and be a super admin.
One pricing detail that affects small teams: Asana sells seats in steps. Between 2 and 5 users you add one at a time; up to 30 users, in steps of 5; up to 100, in steps of 10. A 12-person team pays for 15 seats. Keep that in mind, because it comes back when we get to leavers.
"Contact sales"
We can't tell you what SAML in Asana costs, because Asana doesn't publish it. Here is what you'd pay on the published plans, so you know the floor the Enterprise quote starts from:
| Team size | Starter, annual | Starter, monthly | Advanced, annual | Advanced, monthly |
|---|---|---|---|---|
| 10 | $1,318.80 | $1,618.80 | $2,998.80 | $3,658.80 |
| 20 | $2,637.60 | $3,237.60 | $5,997.60 | $7,317.60 |
| 50 | $6,594 | $8,094 | $14,994 | $18,294 |
The sums: Starter billed annually is $10.99 × 12 = $131.88 a user a year; billed monthly, $13.49 × 12 = $161.88. Advanced is $299.88 a year billed annually and $365.88 billed monthly. Twenty people on Advanced, annual: 20 × $299.88 = $5,997.60. Those team sizes all land on Asana's seat steps, so no rounding up.
Enterprise sits above Advanced, so SAML costs more than $24.99 a user a month, by an amount you'll only learn in a sales call. That's the SSO tax in its most frustrating form: you can't even compare it. Our post on why vendors put SSO on the Enterprise plan explains the business logic, and none of it is about what SAML costs Asana to run. If you're shortlisting tools, a hidden price is a fair reason to prefer one that publishes it.
When you do get a quote, get it in writing with the seat count, the term and the renewal terms. Ask whether SCIM is included or an extra, and whether the price holds if you add people mid-term. A quote that only covers year one is half a quote.
Google sign-in vs SAML
For a company on Google Workspace, this is the part worth reading twice.
By default, members can sign in with a password or with Google. On any paid plan, a super admin can make Google compulsory. From Asana's help article: "If your company uses Google Workspace for business or education, and you are using a paid version of Asana, you have the option to require your members to authenticate via Google."
Turning it on takes four clicks. Open the Admin console from your profile photo, go to the Security tab and then Global authentication settings, and click Google sign-in. Choose Required for all members, except guests, then Save changes.
Members' Asana passwords stop working and they sign in through Google from then on. Asana's pricing page says the same of Microsoft: "Admins on paid plans can require it as the login method across their organization." Google sign-in can't be set up on a division plan, and guests aren't affected by these settings either way.
So what does SAML add on Enterprise? First, any identity provider: Okta, Microsoft Entra ID, OneLogin, LastPass, Active Directory and others, not just Google or Microsoft. Second, session control, since super admins can set a SAML session timeout between one hour and 30 days. Third, control by group, because you can assign SAML sign-in to specific groups in your identity provider. And fourth, SCIM alongside it, which handles onboarding and offboarding automatically and is the real prize. Our explainer on how SCIM provisioning works covers what that automation does and doesn't do.
If your company already lives in Google Workspace, requiring Google sign-in on Starter gives you most of the login benefit of SSO: one account, your Google password rules and two-step verification, and no Asana passwords to leak. What it doesn't do is remove anyone. Suspend a leaver in Google and they can't sign in to Asana, but their Asana seat stays occupied until someone removes them. Our post on Google Workspace SSO covers using Google as your identity provider across tools.
Removing Asana members
A super admin or admin removes a member from the admin console.
Open the Members tab. In the Admin console, go to Members and find the person. Click the three dots next to their name and choose Remove.
Decide where their tasks go. Asana offers to create a private project for the tasks assigned to them and lets you choose who it goes to. Do it. A manager will want that list on Monday.
Confirm. Click Remove member. They show as "Removed" in the list from then on.
What happens to their work, from Asana's user deprovisioning article: a project is generated for the tasks that were assigned to them, and one of your super admins becomes its owner and gets a task to review it. Asana adds that deactivation "does not currently transfer data ownership for projects, portfolios or dashboards", so reassign anything they owned that others rely on before you click.
Two things deserve a closer look. The first is automatic reactivation. On paid plans, a removed user who comes back with the same email address gets their old projects and teams back, if they were removed less than two years ago. That's handy for rehires and a surprise otherwise. Super admins can turn it off under Security, then Reactivation settings.
The second is guests. Starter and above allow unlimited free guests. They don't use seats and aren't covered by your sign-in settings, so they pile up. Your Google sign-in rule does nothing about the freelancer from last spring. Review guests in the same Members tab, and remove the ones whose project has ended.
The admin console can export your membership list to CSV, with each person's last activity and login method, which makes a quarterly user access review quick.
What a forgotten leaver costs
Here's where the seat steps bite. Say you're a 26-person company on Advanced, billed annually. Twenty-six members don't fit the 25 step, so you pay for 30 seats: 30 × $299.88 = $8,996.40 a year. Remove one person who left in the spring and you're at 25, which fits the 25-seat step: 25 × $299.88 = $7,497.00. The difference is $1,499.40 a year, at list price, for one account nobody uses.
On Starter the same gap is 5 × $131.88 = $659.40. Smaller, but it's still money for an account that does nothing except keep an ex-employee's view of your projects open. So compare the seat count in billing with your real member list before each renewal, and remove anyone who shouldn't be there before you commit to another year.
At five people, Asana bills seat by seat, so each leaver you forget is one full seat. At 50, steps are 10 wide, so it takes several forgotten accounts to tip you into the next step, but at 50 people you're also more likely to have several. Either way the fix is the same: remove leavers when they leave.
Common mistakes
Assuming Google sign-in removes people. It stops new logins after you suspend the Google account. The Asana member stays, holding a seat, until an admin removes them.
Leaving guests to the honor system. Guests skip your sign-in rule, cost nothing, and nobody owns them. Give each guest a person inside the company who's responsible for them, and remove guests when that person leaves.
Removing before reassigning. Projects, portfolios and dashboards the leaver owned don't transfer. Move ownership first, then remove.
Forgetting the rehire switch. If you don't want automatic reactivation, turn it off before your next leaver, not after a former contractor quietly gets their old teams back.
Alternatives
The cheapest route to most of what SSO gives you is to require Google (or Microsoft) sign-in on Starter or Advanced. It's on every paid plan, it takes four clicks, and it puts Asana logins under your Google password and two-step verification rules.
Then remove leavers the day they go, and reassign their tasks while someone still remembers what they were. Our employee offboarding checklist puts Asana in order with every other tool a leaver had. Once a quarter, check your seat step against your real member count; just past a step, one leaver can be the difference between paying for 25 seats and 30.
Finally, ask for the Enterprise quote only when something requires SAML, such as a customer contract or an auditor who names it, and ask for SCIM in the same conversation. If you want to see what SAML across your whole stack would cost before that call, the SSO tax calculator adds it up.
Where SmashSSO fits
SmashSSO handles Asana joiners and leavers alongside your other tools, on Starter or Advanced. It reads your people from Google Workspace, reads your Asana organization's members, guests and admins, and matches them by email, flagging accounts that match nobody in your directory. When someone is suspended in Google Workspace, you're alerted and Asana shows up in the list of tools they still have access to.
Invites, role changes and removals run through an agent in your own Chrome, in a tab where you're signed in to Asana's admin console. That browser needs to be open; agent runs are slower than an API and can fail when Asana changes its screens, and a failed run tells you so and shows its last screenshot. Inviting a member adds a paid seat, so that step pauses for your approval, and every change is recorded in the audit log.
It isn't SSO, and if something requires SAML login to Asana, you need Enterprise. Pair Google sign-in on Starter with SmashSSO and you get one login plus leavers removed the day they go, for a flat fee from $199 a month billed annually, however many tools you run (pricing).