Atlassian Guard Pricing & Licensing

An organization admin can create organizations, claim domains and manage all user accounts on the claimed domains, including making changes to the account profile, email address and password. The organization admin can also configure and enforce security policies for the organization via an Atlassian Guard subscription. To become an organization admin, a user must be a site administrator for a cloud site, then an existing organization admin can add the new account as a new organization admin.

• Site Administrators have the highest administration privileges on a cloud site. They can be considered as the owners of that cloud site.
• Administrators have administration access only to the applications of your cloud site. These are the day to day administrators of your cloud site.
• Billing contacts will be notified of changes to the bill and have access to manage your subscription through my atlassian.com. These are the people who are interested in the ongoing billing of your service.

Your Site Administrators and Administrators are managed through your cloud site and your billing contacts are managed through my.atlassian.com. If no Site Administrators are active users, it will be necessary to contact your internal IT team to grant you access to the email address associated for the previous contact. You can then use the 'Unable to access your account?' link from your cloud site.

When domain verification is completed, the user's Atlassian account becomes a "managed" account. This allows the organization admin to manage the name and email address for those accounts. The organization admin can also disable managed users which removes access to all cloud products and any other systems that uses Atlassian account like my.atlassian.com, support.atlassian.com, community.atlassian.com to name a few.

A billable account is any managed account and external user that has access to Jira, Confluence, Bitbucket, Jira Service Management (agents only), or Trello. When a user has access to any of those products, that user is considered billable. 

The number of managed users and external users in your organization will be greater than, or equal to, the number of billable users since not all managed users have access to Atlassian Guard Standard supported products. Managed users in a non-billable authentication policy will not be considered billable users.

Atlassian Guard Premium billing is based on product access. A user counts towards your bill for Atlassian Guard Premium if they are a unique user with access to at least one Confluence or Jira product across any plan (Free, Standard, Premium, and Enterprise). 

A user does not count towards your bill for Atlassian Guard Premium if:

• their account is deactivated
• they don’t have access to at least one Jira or Confluence product
• they only have access to Jira Service Management or Jira Product Discovery

Any organization admin can add/remove additional organization admins from within admin.atlassian.com: 

1. Go to admin.atlassian.com and select an organization, if you have multiple
2. Select Administrators in the left navigation panel
3. Use the Add administrators button to add new administrators then let them know they are now an organization admin. To remove Administrators, use the "remove" button to the right of a name.

Note: A user does not have to already be a site admin to be made an organization admin.

Jira Service Management portal-only accounts that only submit tickets are not billable for Atlassian Guard Standard. Only Jira Service Management agents that log in using a managed account are billable for Atlassian Guard Standard.

Billing and technical contacts are managed through my atlassian.com. Complete instructions for updating these administrative contacts can be found in this documentation. 

Once you are on a paid subscription, an email will be sent to all billing and technical contacts 3 days prior to the billing date if there has been an increase in the upcoming estimated bill relative to your previous bill. You can manage your technical and billing contacts through My Atlassian.

Since Atlassian Guard is an organization-wide cloud subscription, you must be an organization administrator to sign up for a trial. You can start your free 30-day trial by navigating to admin.atlassian.com/atlassian-guard.

Atlassian Guard trials are 30 days. As an organization admin, you can subscribe to Atlassian Guard Standard or Premium after you’ve created or selected an organization within Atlassian Administration here.

The organization admin(s) can add credit card or PayPal account details at any point during the trial. If you already have added payment information, you will be signed up for a monthly subscription, following the 30-day trial. When the trial ends, the card on file will be automatically charged for the next month's subscription.

If you wish to pay annually, you can contact us and we will provide you with a quote that you can pay for by credit card, bank transfer, or check.

If we do not receive payment, shortly after the end of the trial we will unsubscribe you from Atlassian Guard. This means you will no longer have access to Guard capabilities, including:

• Enforced SAML single sign-on. This means managed accounts will have to log in using their Atlassian account. Some users may need to set a new password for their Atlassian account.
• Enforced two-step verification. This means managed accounts can choose to disable that for their Atlassian account at any time.
• Detections of user activity and content scanning. This means alerts will no longer send.

The organization and verified domains are unaffected by unsubscribing, and the organization admin will still be able to view and update the Atlassian accounts for their managed users.

An authentication policy defines how a user must authenticate in order to access an application that belongs to the organization. The purpose of the policy is to protect the organization against a security incident by verifying that each user is who they claim to be.

Atlassian Guard organization admins will be able to set multiple authentication policies to apply to different subsets of managed users in their organization. Organization admins can use an authentication policy to test their SAML configuration by enabling SSO on a small subset of managed users before rolling it out to the whole organization.

The settings that can be configured through authentication policies are:

• Single sign-on (SSO)
• Enforced two-step verification (2SV)
• User API tokens
• Password policies (password strength, password expiry)
• Session duration

Atlassian Guard organization admins will also have the option to select one authentication policy to be a non-billable policy (cannot be the default policy). This non-billable policy will be excluded from the Atlassian Guard subscription. If there is a subset of managed users an org admin does not want to apply any Atlassian Guard features to (SSO, 2SV, etc.), they can be placed in this policy and these users will not be billable for Atlassian Guard.

Your managed accounts provide you with a pool of users for authentication policies. You assign users to be members of policies. Your organization starts with a default authentication policy. The default policy contains login settings for its members. When you provision new managed accounts, we add them as members to your default policy.

For more information, please see Understanding Authentication Policies.

You can use a non-billable policy when you don’t want to pay for certain managed users under your Atlassian Guard subscription. We won't bill you for members in a non-billable policy.

You can only have one (1) non-billable policy. You can only create a non-billable policy with a subscription to Atlassian Guard. A non-billable policy has limited security for its members; you won't be able to:

• Enforce single sign-on
• Require two-step verification
• Block creation of user API tokens
• Add users that you sync from your identity provider (e.g., Okta, Entra ID (fka Azure AD, Google Cloud) to the policy

You can revert it back to billable to restore security settings. Once you do, its members will count towards your Atlassian Guard bill.

A default policy can’t be a non-billable policy. A default policy is always billable. If you don't want to pay for certain members, make a different policy non-billable and add them to it.

For more information, please see Understanding Authentication Policies.

If you have a Guard Premium subscription, users in a non-billable authentication policy will be excluded from Guard Standard functionality and billing, but will still be covered by Guard Premium and billed for the respective price difference.

An external user policy allows you to apply security settings to external users. The settings apply to all the external users in your Atlassian organization.

If you need single sign-on, you can apply it to users in an external user policy. Along with the ability to apply single sign-on, you’re able to apply session expiration and to block the usage of user API tokens.

By default, the users in an external user policy count towards your Atlassian Guard Standard bill. Alternatively, if you don’t want to use single sign-on, you can make your policy non-billable.

Atlassian Guard organization admins can set an external user security policy. Organization admins can use a test policy to try out their setup for up to 5 users before rolling it out to the entire organization.

You can configure these settings in an external user policy: 

Single sign-on (SSO)

One time passcode (OTP)

Session expiration

Block user API token

Atlassian Guard organization admins can make an external user security policy a non-billable policy. This gives admins the flexibility to choose whether or not to include external users in the Atlassian Guard Standard subscription. When an admin makes an external user security policy non-billable, we won’t bill you for users in the non-billable policy.

In a non-billable policy, you’re only able to apply one-time passcode, session duration and user API token access controls.

Atlassian Guard Standard is billed by the total number of unique users accessing any of the Atlassian Guard Standard supported products (Jira, Confluence, Bitbucket, Jira Service Management Agents, Trello). No matter how many products or sites a user has access to, they are a counted a single unique billable user.

Atlassian Guard uses progressive pricing and offers discounts as the user count increases. Use the Atlassian Guard pricing calculator to get an estimated monthly cost.

At the end of your billing period, the credit card or PayPal account on file will be automatically charged based on the number of unique users within your organization. The contact(s) on file will receive a purchase confirmation and paid invoice.

Both Atlassian Guard plans bill the total number of unique users that access at least one supported product.

For Atlassian Guard Standard:

• Supported cloud products are Jira, Jira Service Management, Confluence, Bitbucket, Trello, Statuspage
• Billing applies to managed accounts and external users
• Users in a non-billable authentication and/or external user policy are excluded from the Atlassian Guard Standard bill
• Users covered in a Cloud Enterprise plan will be excluded from the Atlassian Guard Standard bill

For Atlassian Guard Premium:

• Supported cloud products are Jira and Confluence
• Billing applies to both managed and external users
• Users covered by a Cloud Enterprise or Atlassian Guard Standard plan will be billed a price difference

Atlassian Guard is available for free for eligible Community and Academic customers. Please contact us to learn more.

Atlassian Guard Standard is billed when a managed account or external user has access to any of the supported products:

• Jira
• Jira Service Management (Agents)
• Confluence
• Bitbucket
• Trello
• Statuspage

Individual site administrators manage the users for the products on their specific Jira and Confluence sites. We recommend collaborating with your organization's site administrators before disabling managed users. Please note, disabling a user will also remove the user from using that Atlassian account to raise technical support tickets, access their my.atlassian.com account, community.atlassian.com, and other free services.

You can also make an authentication or external user policy non-billable. We don’t count users in a non-billable policy towards your Atlassian Guard Standard subscription.

For Atlassian Guard Premium, users who have access to supported products (Jira and Confluence) cannot be excluded from billing. If these users are in a non-billable authentication or external user policy, they will not be billable for Guard Standard but will be billable for Guard Premium at the price difference.

There are three kinds of users: managed, external, and billable.

• To view managed users, follow the instructions here.
• To view billable users, follow the instructions here.
• To view external users, follow the instructions here.

Yes, users who sign up for free versions of supported products count towards your bill for Atlassian Guard. 

We only charge once per unique user, so if they have access to a paid and free site, they are only counted once towards your bill. 

Users placed in a non-billable policy: 

• do not count towards your Atlassian Guard Standard bill because they are not covered by Atlassian Guard Standard functionality
• do count towards your Atlassian Guard Premium bill, if they have access to products supported by Guard Premium. 

For more information, see:

• Manage your bill for Atlassian Guard Standard
• Manage your bill for Atlassian Guard Premium

Billable users include managed accounts and external users with access to any of the Atlassian Guard Standard supported products listed below. Managed users in a non-billable authentication or external user policy will not be considered billable users.

Atlassian Guard Standard supported products:

• Jira
• Jira Service Management (Agents)
• Confluence
• Bitbucket
• Trello
• Statuspage

No matter how many products or sites a user has access to, they are counted as a single unique billable user across all products. You do not pay by specific product or site, and you'll only pay once per user.

With Jira Service Management (JSM), only the JSM agents handling the tickets (assuming these agents don’t already have access to one of the other Atlassian Guard Standard compatible products) are billable for Atlassian Guard Standard. The users submitting JSM tickets (portal-only accounts) are not billable, as long as they don’t have access to other AtlassianGuard Standard compatible products.

Refer to our documentation for various Atlassian Guard Standard billing scenarios.

To ensure timely payment for monthly subscriptions, we're only able to accept payment via credit card (Visa, Master Card, and American Express)* or PayPal. 

*Unfortunately, we are unable to accept Discover credit cards for monthly renewals. 

The organization admin can update the credit card on file by:

1. Start by going to admin.atlassian.com - your central administration center.
2. Choose your organization. 
3. Select Billing to open the billing panel
4. Select Billing Details to update the credit card/Paypal account and billing address

The primary billing contact can also update the credit card via My Atlassian (Paypal can only be updated within Billing Details screen at admin.atlassian.com.)

The new card or PayPall account will be charged on the next billing date.

In some cases, card issuers will place an authorization hold on funds (making them unavailable) for the amount of the purchase. Atlassian settles the transaction immediately (known as "settlement"), but the authorization hold can remain from 1-5 days until it "falls off" depending on your card issuer's policies.

If the funds are not made available 5 days after the transaction, we recommend contacting your card issuer (Visa/American Express/MasterCard/etc) to see when the authorization hold will drop off.

If you wish to convert to an annual subscription during your trial, you can Contact Us to ask about what is involved with switching your subscription type. 

If you wish to convert to an annual subscription once you are in a paid monthly subscription, organization admins can navigate to the billing section of the admin.atlassian.com and click on 'Billing Details'. They can then click on the 'Switch to an annual payment plan' link to generate an annual quote, and either pay later with a quote or pay now by credit card.

If you're looking to lower your monthly bill there are a few strategies for doing this:

• Convert to an annual subscription. Annual subscriptions currently offer a discount that equates to 2 months free on an annual basis. Learn how to convert to an annual subscription.
• Contact Site Administrators for other cloud products in your organization to verify their user base is still active users. Site Administrators also pay for their users to have access to cloud products, so they generally are actively managing their users. You can then disable the Atlassian accounts of managed users in your organization who are no longer active. 

Atlassian Guard Standard is billed by the total number of unique users accessing any of the Atlassian Guard Standard supported products (Jira, Jira Service Management (Agents), Jira Product Discovery, Confluence, Compass, Bitbucket, Trello). No matter how many products or site a user has access to, they are counted a single unique billable user.

Atlassian Guard uses progressive pricing and offers discounts as the user count increases. Please use the Atlassian Guard pricing calculator to get an estimated annual cost.

You must purchase a one year subscription of Atlassian Guard upfront. Annual subscriptions are tier-based and currently offer a discount that equates to 2 months free on an annualized basis.

Atlassian Guard Standard is billed when a managed account or external user has access to any of the supported products:

• Jira
• Jira Service Management (Agents)
• Confluence
• Bitbucket
• Trello
• Statuspage

Individual site administrators manage the users for the products on their specific Jira and Confluence sites. We recommend collaborating with your organization's site administrators before disabling managed users. Please note, disabling a user will also remove the user from using that Atlassian account to raise technical support tickets, access their my.atlassian.com account, community.atlassian.com, and other free services.

You can also make an authentication or external user policy policy non-billable. We don’t count users in a non-billable policy towards your Atlassian Guard Standard subscription.

For Guard Premium, you cannot remove users unless they are also removed from accessing supported products.

To see the total number of billable users, follow the instructions to view your bill estimate.

Please contact us to request an upgrade quote.

• Trialers: during your 30 day trial, the organization admin can contact us to request an annual quote.
• Paid monthly subscription customers: organization admins can navigate to the Billing section of admin.atlassian.com and click on 'Billing Details'. Then click on the 'Switch to an annual payment plan' link to generate an annual quote, and either pay later with a quote or pay now by credit card.

If you're looking to upgrade or downgrade upon your renewal date, please contact us via our contact us form. 

Payment can be made by credit card, bank transfer, mailed check, ACH (US banks only), and Net-30 terms for orders above $10,000. Complete payment details appear on the first page of an official quote and on our How To Pay page.

Organization admins can view invoices on the Billing History page in admin.atlassian.com. Primary billing and technical contacts can view invoices and quotes via My Atlassian.

In the legacy billing system, the primary billing and technical contacts will receive a renewal quote 60 days prior to the end of the billing period. They can also retrieve the renewal quote via My Atlassian.

In the new billing engine, billing administrators will receive a renewal quote 90 days prior to the end of the billing period. 

To learn more about which billing experience you are viewing, click here.

If you're looking to upgrade or downgrade upon your renewal date, please contact us via our contact us form.

The organization admin can monitor licensed usage at any time on the Manage Subscriptions page in admin.atlassian.com. If you need to raise your licensed user limit, contact us to request an upgrade quote. 

If you no longer need Atlassian Guard Standard, you can unsubscribe at any time. Follow the instructions to unsubscribe.

You can also contact us for assistance.

If you no longer need Atlassian Guard Premium, you can unsubscribe at any time. Follow the instructions to unsubscribe. 

You can also contact us for assistance.

When you are unsubscribed from Atlassian Guard, you will no longer have access to capabilities like:

• Enforced SAML single sign-on. This means managed accounts will have to log in using their Atlassian account. Some users may need to set a new password for their Atlassian account.
• Enforced two-step verification. This means managed accounts can choose to disable that for their Atlassian account at any time.
• Detections of user activity and content scanning. This means alerts will no longer be sent.

Your verified domains are unaffected and you will still be able to view, manage, and update the Atlassian accounts for your managed users.

Some critical configurations will be retained. For full details of what will change, what is retailed, and for how long, see:

• Unsubscribe from Atlassian Guard Standard
• Unsubscribe from Atlassian Guard Premium

Refunds for Atlassian Guard are only available within the first paid month after the trial period for monthly subscriptions and within 30 days of payment for annual subscriptions. After these periods, we cannot offer refunds. Learn how to request a refund.

Data Center and cloud products are not interchangeable and refunds are not available after 30 days of the initial purchase, see our Cloud Refund FAQ for details.

If you wish to move from one Atlassian cloud product to another, a refund or credit can be granted as long as your initial purchase falls within our 30-day refund window. Orders that fall outside of the refund window will not be credited toward a new purchase. Please contact us to discuss credits or request a refund.

Use of cloud is governed by the Atlassian Customer Agreement and Product Specific Terms.

Within Atlassian's current price structure, we're unable to make any changes to our standard customer terms. If you consider our pricing model and the costs of creating and managing individual agreements with each of our customers, you can begin to understand our position.

Maintaining standard terms with all of our customers allows us to focus our resources on meeting our obligations under these agreements. Do keep in mind of course that our customer terms have been very carefully authored to be fair to both you and us.