Skip to content

Blog

Atlassian Guard: what SSO for Jira and Confluence costs

Atlassian Guard adds SAML SSO to Jira and Confluence, billed per user. What Standard and Premium cost, what they add to your bill, and the options without it.

· 8 min read

Atlassian Guard is how Jira and Confluence get SAML single sign-on: none of their Free, Standard or Premium plans include it. Guard Standard costs $4.35 per user a month (monthly billing, for teams over 10 users), on top of what you pay for the products. Guard Premium, which adds security monitoring, is $8.55 per user a month. Only Atlassian's Enterprise plan includes Guard Standard.

Those are the prices on Atlassian's Guard pricing page as we read it on 27 October 2026. Below: what Guard is, what each tier includes, what it adds to a small team's Jira bill, what you can do with Google Workspace without it, and how to manage and remove Atlassian users by hand.

What Atlassian Guard is

Atlassian Guard is Atlassian's security and identity add-on for its cloud products. Its Standard tier was previously called Atlassian Access; Atlassian's support documentation still says "Atlassian Guard Standard (formerly known as Atlassian Access)". If you find old guides about Access, they mean Guard Standard.

It works at the level of your Atlassian organization, not each product. You verify your company's email domain, connect your identity provider, and Guard applies to everyone with an account on that domain, across Jira, Confluence and the rest.

Guard Standard vs Premium

TierPrice, per user a monthWhat it adds
Guard Standard$4.35Enforced SSO, SCIM provisioning and deprovisioning, mobile app management, API token controls, organization audit log
Guard Premium$8.55Standard, plus data classification, anomalous activity detection, alert investigations, content scanning, SIEM integrations, remediation recommendations

Guard Standard covers Jira, Jira Service Management, Confluence, Bitbucket, Trello and Statuspage. Premium's extra features currently cover Jira and Confluence Cloud only, and Premium can be added on top of an Enterprise plan.

Prices are for monthly billing at 11 users or more; annual billing saves up to 17%, according to the page. For 10 users or fewer, the page's calculator shows a flat $30 a month for Standard and $60 a month for Premium. There is a 30-day free trial, started by an organization admin.

How it is billed

Two details work in your favor, and one does not. First, Guard Standard is billed once per managed account, however many Atlassian products that person uses. If your team uses Jira and Confluence, you pay Guard once, not twice. Second, Enterprise includes it: the pricing page describes the Cloud Enterprise plan as one "which includes Atlassian Guard Standard at no additional cost", so those users are not counted again. The catch is that free-plan users count. If someone on your verified domain uses a free Atlassian product, they are billable for Guard too, so check how many accounts on your domain exist before you turn it on. A forgotten Trello board from 2019 can add seats to your bill.

What it costs on top of Jira

Jira Standard is $9.70 per user a month for teams of up to 100 people on monthly billing, per Jira's pricing page on the same day. Adding Guard Standard to that:

Team sizeJira Standard, a yearGuard Standard, a yearIncrease
10 people$1,164$36031%
20 people$2,328$1,04445%
50 people$5,820$2,61045%

The sums: Jira is $9.70 × 12 = $116.40 a person a year, so 20 people is $2,328. Guard Standard is $4.35 × 12 = $52.20 a person a year, so 20 people is $1,044, about 45% of the Jira bill. At 10 people Guard is the flat $30 a month, $360 a year. Those use monthly prices times twelve; annual billing is somewhat cheaper for both. If the same people also use Confluence, the Guard line stays the same while the product bill grows, so the percentage falls.

Compared with most tools, this is a mild SSO tax: the jump is a per-user add-on, not a move to an Enterprise plan for everything. It is still a 45% increase on Jira for a 20-person team, for a login feature. The SSO tax calculator shows how it compares with your other tools.

Is Guard worth it for anything else?

Guard Standard is narrow by design: almost everything on its list is identity. Beyond SSO and SCIM, you get mobile app management, which controls how Atlassian's phone apps handle company data, API token controls, and an organization-wide audit log. If you have been asked to show who changed what in Jira and when, the audit log alone may justify it.

Premium is a different purchase. Data classification, anomalous activity detection, content scanning and SIEM integrations are tools for a security team watching for leaks. A 15-person company without a security person probably won't look at those alerts, and an alert nobody reads protects nothing. If you're weighing Guard against a full identity provider, our posts on Okta pricing and JumpCloud pricing have those numbers, since you need one of those for SAML anyway.

SAML and provisioning with Guard

With Guard Standard you can enforce SAML SSO through your identity provider (Okta, Microsoft Entra ID, Google Workspace and others) for everyone on your domain. You can provision and deprovision users with SCIM, so people added to a group in the identity provider get access to Jira and Confluence, and leavers lose it. You can sync groups from the identity provider, so Atlassian groups and product access follow your directory. And you get control over API tokens, plus the organization-wide audit log.

The provisioning half is what most small teams are really after. Our post on SCIM provisioning explains how it works, and why vendors like to bundle it with SSO on their paid tiers.

Google Workspace without Guard

You can connect Google Workspace to your Atlassian organization without paying for Guard, and it does more than people expect. Atlassian's guide to connecting Google Workspace, as we read it on 27 October 2026, says that without Guard "We sync all Google Workspace users to a single group called All users from Google Workspace." Changes sync every four hours. Once connected, people on your domain can sign in to Atlassian with their Google account.

Three limits apply. App access is turned off for new synced users, so an admin still has to grant Jira or Confluence to the group. Syncing specific Google groups to specific Atlassian groups needs Guard Standard. So does requiring people to log in with Google: Atlassian's guide to requiring Google login is a Guard Standard feature, so without it people can still choose an Atlassian password instead. Our post on Google Workspace SSO covers using Google as your identity provider more broadly.

How to decide

Size changes the answer more here than with most tools. A 10-person company on Google Workspace pays the flat $30 a month, $360 a year, and Guard Standard lets it require Google login for everyone on its domain. That is enforced sign-in through the identity provider it already has, without buying Okta. At $3 a person a month, that is less per person than the Slack SSO upgrade ($7.75) or Zoom's ($4.17). If a customer has asked you to prove that nobody gets into Jira without a company login, that is a cheap way to say yes.

A 50-person company pays $2,610 a year for the same thing, and the question becomes what it actually needs. If it is the enforced login, Guard is still one of the cheaper ways to get it. If it is that leavers lose Jira and Confluence on their last day, that is a removal process, and it can be run without Guard, as the next section shows. Be honest about which problem you have before you pay for the other one.

Managing Atlassian users without it

Without Guard, removing people is a manual job in Atlassian Administration. Atlassian's guide to removing or suspending a user, as we read it on 27 October 2026, gives two options that both stop the bill.

Suspend first. In Atlassian Administration, go to Directory, then Users, find the person, open the ••• menu and choose Suspend access. Atlassian says "You won't be billed for a user when their access is suspended," and if you restore access later, the person gets their roles and group memberships back. On the older user management screens, the path starts at admin.atlassian.com, then your site, then Users, with the same menu.

Remove when you're sure. The same menu has Remove user. Billing stops ("You won't be billed for a user once they're removed"), but Atlassian warns that "Removing a user will remove some of their content", and bringing them back means a new invitation and reassigning roles and groups by hand. For most leavers, suspending is the safer default: access ends the same way, the bill stops the same way, and nothing is lost if you got the wrong person. Accounts on your verified domain can also be deactivated across all Atlassian services from the managed accounts list.

Two habits make the manual route manageable. Give product access through groups, so removing someone from a group removes their access to Jira or Confluence in one step. And review the user list regularly: Atlassian shows last active dates, which makes a quarterly user access review quick. The rest of a leaver's tools are in our employee offboarding checklist.

Where SmashSSO fits

SmashSSO manages Atlassian users from the same place as every other tool. It reads your people from Google Workspace, reads who has access to your Atlassian site and with what role, and invites, changes and removes people through an agent in your own Chrome, where you are already signed in as an admin, or through an API where you have added a token. The agent needs that browser open, it is slower than an API, and a run can fail when Atlassian changes its admin screens. Someone suspended in Google Workspace shows every tool they are still in, Jira and Confluence included. Steps that would add a paid seat wait for your approval, and every change is written to an audit log.

It is not SSO and it does not replace Guard if you need enforced SAML login. If what you want is that leavers lose Jira and Confluence the day they go, without the per-user add-on, it costs a flat fee from $199 a month billed annually, for the whole company (pricing).

FAQ

What is Atlassian Guard?
Atlassian's security and identity add-on for its cloud products. Guard Standard adds enforced SAML SSO, SCIM provisioning, API token controls and an organization audit log across Jira, Confluence and other Atlassian apps; Guard Premium adds security monitoring.
How much does Atlassian Guard cost?
Atlassian's page lists Guard Standard at $4.35 and Guard Premium at $8.55 per user a month on monthly billing, for teams over 10 users, as read on 27 October 2026. For 10 users or fewer its calculator shows $30 and $60 a month in total.
Does Jira include SSO?
Not on Free, Standard or Premium: SAML SSO needs an Atlassian Guard Standard subscription. Jira's Enterprise plan includes Guard Standard. Without Guard, users on your domain can still log in with their Google account if you connect Google Workspace, but you cannot require it.
Is Atlassian Access the same as Atlassian Guard?
Yes. Atlassian renamed Atlassian Access to Atlassian Guard; its support documentation calls the Standard tier "Atlassian Guard Standard (formerly known as Atlassian Access)".

Keep reading

Stop paying for a login button.

Sign in with Google Workspace, connect your tools, and see who has access to what in minutes.

Sign up with Google