Manage subscriptions and bills for Atlassian cloud products
Get a high-level overview of billing and subscription management for Atlassian cloud products.
Atlassian Access is an organization-wide subscription that connects your Atlassian cloud products to your identity provider. It provides user management, enterprise-grade authentication, and additional security features, across your company domains.
Atlassian Access uses a different billing model from other Atlassian cloud products. Atlassian Access is billed per organization. This means you only pay once for each managed account in your organization.
Your Atlassian Access bill will show the number of users that you are paying for. These are your unique billable users for Atlassian Access. This user count may not match the total number of managed accounts in your organization because some plans already include Atlassian Access, and we don’t charge you twice for the same user.
User accounts on the following plans don’t count towards your Atlassian Access bill, because Atlassian Access is already included in their plan. Learn how we bill you for Enterprise plans
Managed accounts on all other plans, including free plans, do count towards your Atlassian Access bill. Managed accounts that only have access to a sandbox also count towards your Atlassian Access bill.
Product | Accounts not considered unique billable users |
---|---|
Confluence | Any managed account on an Enterprise plan |
Jira Core | Any managed account on an Enterprise plan |
Jira Software | Any managed account on an Enterprise plan |
Jira Service Management | Any managed account on an Enterprise plan (agent accounts only) |
OpsGenie | Any managed account on a Standard or Enterprise plan |
Statuspage | Any managed account that can administer:
|
Trello | Any managed account on an Enterprise plan, or not part of a Trello workspace. |
In addition, a user is not considered a unique billable user if:
They don’t have access to any products.
They haven’t been active since February 2018.
Their account is deactivated.
They are a member of a non-billable authentication policy.
They have a Jira Service Management portal customer account (portal customers who have an Atlassian account are covered by Atlassian Access features, but only agents count as unique billable users).
Their account is covered by a legacy Trello Enterprise license. For more details see, Impact of Trello users on your Atlassian Access bill
Here’s a simple example, showing how your access bill only includes users not covered under an Enterprise plan.
Here are a few more examples that illustrate how Atlassian Access billing works:
If your organization has 100 people with Jira access on a Standard plan, and 50 of those people also have Confluence access on a Standard plan, the user count on your Atlassian Access bill would be 100. This is because Atlassian Access is not included in your Jira and Confluence plans.
If your organization has 30 people on an Enterprise OpsGenie plan, and no-one with access to any other Atlassian cloud products, the user count on your Atlassian Access bill would be 0, because your OpsGenie plan includes Atlassian Access.
If your organization has 1500 users with Jira and Confluence access on an Enterprise plan, and 50 users with access to Bitbucket on a Standard plan, the user count on your Atlassian Access bill would be 50, because Enterprise plans include Atlassian Access.
If your organization has 40 people with Jira access on a Free plan, and 10 of those people also have access to a Statuspage page on a Business plan, the user count on your Atlassian Access bill would be 30, because Statuspage Business plans include Atlassian Access.
The cost depends on the number of unique billable users, and whether you choose to pay monthly or annually. We apply discounts as your organization increases in size.
To get an idea of what Atlassian Access might cost for your organization, use our pricing calculator.
To view your bill estimate and the number of unique billable users:
Go to admin.atlassian.com. Select your organization if you have more than one.
Select Billing then Manage subscription next to Atlassian Access.
The number of users listed in your Atlassian Account subscription represents the total number of users you will pay for, not the total number of managed accounts that are covered by Atlassian Access (for example users on an Enterprise plan that includes Atlassian Access aren’t included in this count, but can take advantage of Atlassian Access features like single sign-on).
The date of your first bill depends on when you subscribe to Atlassian Access. It you’re evaluating Atlassian Access and decide to subscribe, your first bill will be due at the end of the evaluation period.
You can choose to be billed monthly or annually. There are advantages and disadvantages to each:
Monthly
Flexible, per-user pricing. At the end of your billing period, you’re automatically charged based on the number of unique billable users within your organization. You only pay for what you need.
Annual
Flat rate, user-tier pricing. Annual subscriptions are for one year, and are paid up front, by user-tier. It has a lower cost per user, but you may end up paying for more users than you need.
To find out which option is best for your organization, use our pricing calculator.
To change to an annual Atlassian Access subscription:
Go to admin.atlassian.com. Select your organization if you have more than one.
Select Billing then Manage subscription next to Atlassian Access.
Select Choose annual payment under Payment options.
You can also purchase annual pricing directly by contacting Atlassian.
To get started with Atlassian Access you need to:
Have an organization.
Verify one or more domains.
Subscribe to Atlassian Access.
For more details, see Understand Atlassian Access.
You’ll need to provide your payment details for Atlassian Access in the billing section for your organization (even if you are already paying for existing Atlassian cloud products and services).
To enter your payment details:
Go to admin.atlassian.com. Select your organization if you have more than one.
Select Billing then Manage subscription next to Atlassian Access.
Select Add payment method and follow the prompts to confirm your billing address, and preferred payment method.
For more ways to pay, see How to pay.
There are several ways you can change the number of unique billable users that count towards your Atlassian Access bill. You can:
Deactivate or delete accounts you no longer need.
Remove product access for some users.
Add users to a non-billable authentication policy.
There are advantages and disadvantages to each approach, and you may want to use a combination of all three.
Deactivated and deleted accounts don’t count towards your Atlassian Access bill.
Deactivate an account
Useful when someone no longer needs access to any Atlassian cloud applications. You can reactivate their account at any time. Learn how to deactivate a managed account
Delete an account
Useful when someone has left your organization. You can’t restore a deleted account. Learn how to delete a managed account
Users won’t be able to access their my.atlassian.com account, get technical support at support.atlassian.com, post messages on community.atlassian.com, or other free services, once their account is deactivated or deleted.
Users who don’t have access to any products supported by Atlassian Access don’t count towards your bill.
If you don’t want to deactivate an account, consider removing access to all products supported by Atlassian Access.
Learn how to remove or suspend a user's product access
Authentication policies allow you to specify different authentication settings for different sets of users and configurations. You can create a nonbillable policy that provides limited security features for users you don’t want to pay for.
Users who are members of a nonbillable authentication policy don’t count towards your Atlassian Access bill.
Learn more about authentication policies
If you no longer need Atlassian Access, you can unsubscribe at any time.
Learn how to unsubscribe from Atlassian Access
Once you unsubscribe, Atlassian Access functionality, such as user provisioning and SAML single sign-on, will immediately end.
There’s no change to your Atlassian cloud product subscriptions, which continue as previously. To also cancel your Atlassian cloud subscription, see Cancel your site subscription.
Was this helpful?