What is a non-billable policy?
Who can do this? |
When users are either manually invited or sign themselves up, you can decide whether to include them in your Atlassian Guard Standard subscription.
With an Atlassian Guard Standard subscription, you can create a non-billable policy when you don’t want to pay for certain users. We won't bill you for users in a non-billable policy. You can only have one (1) non-billable policy.
You can set a default policy into a non-billable policy. You can only create a non-billable policy in a local directory.
When you edit authentication policies and make a policy non-billable, you won't be able to:
Enforce single sign-on
Require two-step verification
Block user API tokens
Add users that you sync from your identity provider to the policy
You can't add the users you sync from your identity provider (e.g., Okta, Azure AD, Google Workspace) to a non-billable policy.
If you sync users that are part of a non-billable policy, we move them to a different policy and directory. You can find these users in the default policy of your local directory.
You can easily update your policy to include all security settings. Once you do, the users in the policy may count towards your bill. Manage your bill for Atlassian Guard Standard.
Make a policy non-billable
To make a policy non-billable:
Go to admin.atlassian.com. Select your organization if you have more than one.
Select Security > Authentication policies.
Select Edit for the policy you want to make non-billable.
Select Make policy non-billable in the (•••) menu
Update a non-billable policy to add all security settings
To update a non-billable policy to all security settings:
Go to admin.atlassian.com. Select your organization if you have more than one.
Select Security > Authentication policies.
Select Edit for the non-billable policy.
Select Add all security settings to policy.
Update policy.
Make a default policy non-billable
When you don’t want users who are manually invited or sign themselves up to count towards your Atlassian Guard Standard subscription, we can automatically add them to a default non-billable policy.
Before you make a non-billable policy a default policy, you must link the domain for user accounts you want in the local directory. We add new user accounts from the domain you link to the default authentication policy of the local directory.
To link domains to a directory:
Go to admin.atlassian.com. Select your organization if you have more than one.
Select Security > Identity providers.
Select the Directory you’d like to view.
Select View domains to link the domain to the local directory.
Select Link domain.
Select one or many domains to link to the local directory.
To make a policy non-billable:
Go to admin.atlassian.com. Select your organization if you have more than one.
Select Security > Authentication policies.
Go to the default policy in your local directory.
Select Edit on the default policy.
Select Make policy non-billable.
Was this helpful?