Atlassian Access Pricing & Licensing
Manage roles
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 Access 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. |
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 that has access to Jira Software, Jira Work Management, 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 in your organization will be greater than, or equal to, the number of billable users since not all managed users have access to Atlassian Access supported products. Managed users in a non-billable authentication policy will not be considered billable users. |
Any organization admin can add/remove additional organization admins from within admin.atlassian.com:
Note: a user does not have to already be a site admin to be made an organization admin. |
No, Jira Service Management customers that submit tickets are not counted toward the Atlassian Access bill. Only Jira Service Management Agents that log in using an Atlassian Access managed account are counted in Atlassian Access. |
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. |
Trialing Atlassian Access
As Atlassian Access is a tool for managing authentication and security policies across your cloud users, you must be a site administrator to sign up for Atlassian Access. Follow these steps to get started with your Access evaluation:
|
Atlassian Access trials are for 30 days and begin when the organization admin subscribes. You can subscribe to Atlassian Access after you've created an organization and verified a domain. The trial begins when you click "Try it for free for 30 days". The organization admin will need to configure SAML single sign-on and two-step verification after starting the Atlassian Access trial. |
The organization admin(s) can add credit card or PayPal account details at any point during the trial, the card on file will be automatically charged when the trial ends for the next months 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 Access. The following changes will happen:
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. |
To cancel an Atlassian Access trial or paid subscription, the organization admin will:
SAML single sign-on and two-step verification functionality will immediately end and the following changes will occur:
|
Authentication Policies
An authentication policy dictates which authentication settings a user must pass to access an application. The purpose of the policy is to protect the organization against a security breach by verifying that each user is who they claim to be. |
Atlassian Access org admins will be able to set multiple authentication policies to apply to different subsets of users in their organization. Org admins can use an authentication policy to test their SAML configuration by enabling SSO on a small subset of users before rolling it out to the whole organization. The settings that can be configured through authentication policies are:
Access org admins will also have the option to select one authentication policy to be a non-billable policy. This non-billable policy will be excluded from the Atlassian Access subscription. If there is a subset of users an org admin does not want to apply any Access features to (SSO, 2SV, etc.), they can be placed in this policy (cannot be the default policy) and these users will not be billable for Access. |
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. |
With a subscription to Atlassian Access, you can use a non-billable policy when you don’t want to pay for certain users. 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 Access. A non-billable policy has limited security for its members. When you edit authentication policies and make a policy non-billable, you won't be able to:
You can easily update your policy back to all security settings. Once you do its members may count towards your Atlassian Access 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 another policy non-billable and add them to it. For more information, please see Understanding Authentication Policies. |
With just one authentication policy for an entire organization, you risk slowing your teams down where authentication is needlessly cumbersome or compromising your data where authentication is too lean. Thus, administrators may want to establish varying authentication policies for different sets of users and configurations. Organizations commonly assign different authentication policies for full-time employees, contractors, and outside partners. Some even assign policies by team. |
For more information, please see our Understanding Atlassian Access and Understanding Authentication Policies documentation. |
Monthly subscriptions
Atlassian Access is billed by the total number of unique users accessing any of the Atlassian Access 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 Access uses progressive pricing. Please use the Atlassian Access Online Calculator tool to get an estimate. |
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. |
Atlassian Access is available for free for eligible Community and Academic customers. Please Contact Us to learn more. |
Atlassian Access is billed when a managed account has access to any of the supported products:
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. As an organization admin, you can disable a user's Atlassian account to remove their access from Atlassian applications. 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. To disable a user's Atlassian account in Atlassian Access
Disabled accounts will not count towards your Atlassian Access bill. You can always re-enable a user's account later from the managed user screen. |
There are two kinds of users: managed and billable. To view the managed users, the organization admin will:
Billable users are managed users that have access to the below cloud products:
To see the total number of billable users, an organization admin will:
|
Yes. If a user signs up for the free versions of Jira Software, Jira Service Management, Jira Work Management, or Confluence cloud on a domain governed by Atlassian Access they will be included as a billable user under their Atlassian Access subscription. Please note, with Access you'll only ever be charged once per user who has access to a cloud product. If a user has access to both a paid Jira Software site as well as a free Jira Software site, they will be counted once towards your bill each billing cycle. |
Billable users are any enabled managed users that have access to any of the Atlassian Access supported products listed below. Managed users in a non-billable authentication policy will not be considered billable users. Atlassian Access supported products:
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 each user. |
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:
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:
|
Annual subscriptions
Atlassian Access is billed by the total number of unique users accessing any of the Atlassian Access supported products (Jira, Confluence, Bitbucket, Jira Service Management Agents, Trello). No matter how many products or site a user has access to, they are counted a single unique billable user. |
Atlassian Access uses progressive pricing like Jira and Confluence Cloud, so the more users you have we have built in a pricing discount. Please use the Atlassian Access Online Calculator tool to get an annual subscription estimate. |
Billable users are any enabled managed users that have access to any of the Atlassian Access supported products:
No matter how many products or sites a user accesses, you only pay for Atlassian Access once per user. You do not pay by specific product or site. |
You must purchase a one year subscription of Atlassian Access upfront. Annual subscriptions are tier-based and currently offer a discount that equates to 2 months free on an annualized basis. |
Atlassian Access is available for free to qualified academic institutions. Please Contact Us to learn more. |
Atlassian Access is billed when a managed account has access to any of the supported products:
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. As an organization admin, you can disable a user's Atlassian account to remove their access from Atlassian applications. 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. To disable a user's Atlassian account in Atlassian Acccess
You can always re-enable a user's account later from the managed users page. |
To see the total number of billable users, an organization admin will:
|
At this time, it is not possible to generate an upgrade quote from my.atlassian.com or within admin.atlassian.com. Please Contact Us to request an upgrade quote. |
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. |
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. 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, please Contact Us to request an upgrade quote. |
Unsubscribing & Refunds
To unsubscribe an Atlassian Access trial or paid subscription, the organization admin will:
SAML single sign-on and two-step verification functionality will immediately end and the following changes will occur:
|
When you are unsubscribed from Atlassian Access you'll see the following changes take effect immediately:
Your organization and verified domains are unaffected by unsubscribing, and you will still be able to view, manage and update the Atlassian accounts for your managed users. |
Refunds for Atlassian Access 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. |
Server 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. |
Terms of Service
Use of Atlassian's cloud products are governed by the Atlassian Terms of Service and Product Specific Terms. |
Within Atlassian's current price structure, we're unable to make any changes to the Atlassian Terms of Service. 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 a standard Terms of Service 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 Terms of Service have been very carefully authored to be fair to both you and us. |