Edit authentication settings and members
Available authentication policy settings for your organizations
With authentication policies, you configure settings for different sets of users. These sets of users come from your managed accounts. When you test settings on a subset of users, you reduce the risk of rolling out an error to your entire organization.
You need an Atlassian Guard Standard subscription to create more than one authentication policy and apply single sign-on (SSO), two-step verification, and user API token settings to an authentication policy. The settings you can configure through authentication policies are:
Setting | Description | Requires Atlassian Guard Standard |
|---|---|---|
Single sign-on through SAML or Google Workspace | Enforce members to log in to Atlassian products with your identity provider. | |
Two-step verification | Require members to set up and use a second step when logging in.
| |
Make it optional to set up and use a second step when logging in. |
| |
User API tokens | Control whether members create new or use existing API tokens to authenticate to your organization’s product data. | |
Third-party login | Allow members to log in to Atlassian products with third-party accounts. |
|
Prevent members from logging in to Atlassian products with third-party accounts. |
| |
Password requirements | Choose minimum strength for user passwords. |
|
Choose when a password expires. |
| |
Idle session duration | Choose how long members can be idle before we log them out. |
|
Add settings to your authentication policies
Single sign-on (SSO)
SSO allows your users to log in using your organization's identity provider to access all your Atlassian cloud products. Create one authentication policy to test an SSO configuration on a few accounts before turning it on for your whole organization.
Set up SSO for SAML or Google Workspace
When you select SAML SSO, you’re redirected from the authentication policy to the SAML SSO configuration page. Learn how to configure SAML single sign-on.
When you select Google Workspace, you’re redirected from the authentication policy to the Google Workspace setup page. Learn how to set up Google Workspace
Once you’re done configuring SAML SSO or Google Workspace SSO, you need to enable SSO in the policy.
To enable SSO:
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 enforce.
Select Enforce single sign-on.
Warning: What happens if you enforce SSO on users who are not in an identity provider? |
Enforce two-step verification
Two-step verification adds a second login step. The second step keeps the user accounts secure even if the password is compromised. When account logins are secure, your organization's products and resources are safer.
You can require members to set up and use a second step when logging in or make it optional.
If you enable SSO, you can only set up two-step verification in your identity provider and not your authentication policy. Learn how to enforce two-step verification |
Third-party login
Control whether members can log in to your products with third-party accounts such as Google, Microsoft, Apple and Slack accounts.
If you enable SSO, you can only manage third-party logins in your identity provider and not in your authentication policy. |
User API tokens
Users create API tokens to authenticate themselves into an organization and to run scripts. Members can access your organization's product data with Atlassian’s product APIs. User API token settings control whether members can make API calls with an API token to your organization's products.
By default, your organization's user API token settings are set to allow access. With the user API token setting, you can allow or block members from:
Creating a new API token
Using an existing API token
To block user API tokens:
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 block.
Select Block members from creating a new or using an existing API token.
Select Update.
Amount of time to update user API tokens
When you allow or block user API tokens, we apply the update the next time a member tries to make an API call with a token to run a script into your organization.
It can take up to 10 minutes to complete the update. If a member tries to access your products with a user API token before we complete the update, they can still access the organization.
Learn about how users manage API tokens
Password requirements
You can choose the minimum strength that all passwords must comply with. By default, passwords do not expire. However, you can set an expiration period by defining the number of days for password expiration.
If you enable SSO, you can only set up password requirements in your identity provider and not your authentication policy. |
Idle session duration
Idle session duration is the amount of time a member stays logged in before we log them out, and they have to log back in. Learn how to update idle session duration
Add members to your authentication policies
Members come from your managed accounts, and you add them to different policies. Enter members individually or in bulk to your authentication policy.
To enter members individually:
Go to admin.atlassian.com. Select your organization if you have more than one.
Select Security > Authentication policies >
Select Edit.
Select Members tab > Add members.
Enter a user name or email address (only up to 20 users).
Select Add.
To enter members in bulk:
Go to admin.atlassian.com. Select your organization if you have more than one.
Select Security > Authentication policies >
Select Edit.
Select Members tab > Add members.
Select Bulk entry > Select Upload to add CSV file (only up to 10,000 emails from your managed accounts are allowed).
Select Add.
We’ll notify you with an email when your bulk member update is complete. You can view your audit logs to check which members were added or could not be added. Learn more about audit logs
Change policy for members
You may need to move members from one policy to another policy. You can move individual members by going to Change member’s policy or Add members. You can only move members in bulk by using Add members.
To change the policy for individual members:
Go to admin.atlassian.com. Select your organization if you have more than one.
Select Security > Authentication policies.
Select Edit for the policy the member belongs to.
Select Members tab > Change member’s policy.
Choose a different policy for this member.
You can move members from one policy in a directory to a policy in a different directory. Learn more about directories
To change the policy for more than one member:
Go to admin.atlassian.com. Select your organization if you have more than one.
Select Security > Authentication policies.
Select Edit for the policy to move members to.
Select Members tab > Add members.
Select Bulk entry > Select Upload to add CSV file (only up to 10,000 emails from your managed accounts are allowed).
Select Add.
We'll add members to the new policy and apply the change next time the member logs in.
A member can only be in one policy at a time.
Export members from an authentication policy
You can export a list of all your members in an authentication policy to a CSV file.
Go to admin.atlassian.com. Select your organization if you have more than one.
Select Security > Authentication policies.
Select a policy > Members.
Select Export members to a CSV file.
We’ll send you an email with a link to download the CSV file. It may take a while if you have a large number of member accounts. The download link in the email expires in 24 hours. Anyone with the link can download the CSV file.
Member details in your CSV file
This is the information included in the CSV file for each member of an authentication policy.
Member information | Authentication settings | Product details |
|---|---|---|
Name | SAML single sign-on (if member logs in with SAML single sign-on) | Bitbucket, Confluence, Jira, Jira Service Management, OpsGenie, StatusPage, Trello (listed with the sites they use to access products) |
Two-step verification enabled (if two-step verification is enabled for members) | ||
Last active time (the date the user was last active) | Password requirements (password strength and expiration) | |
Status (active or deactivated) | Idle session duration (length of time members can be inactive before we log them out) | |
Billable (members who count towards your Atlassian Guard Standard bill) | ||
Policy name (name of the authentication policy) | ||
Policy type (billable or nonbillable) |
Was this helpful?