Manage your organization’s Atlassian accounts
Gain control over your employee's Atlassian accounts.
Control how users get access to products
You must be an organization admin to change or update these user access settings.
This page covers the settings that control how users get access to products in your organization.
Users with product access also have organization access. Each user that joins your organization takes up a license seat for each of the products they have access to. If you go over the number of users in your plan, we'll let you know by email.
Approved domains
Approve your company’s domains to help your users access your products quickly.
You might use this to:
Approve your company domain so onboarding is easier for your employees.
Approve client domains so they can always get access.
To add an approved domain:
Go to admin.atlassian.com. Select your organization if you have more than one.
Select Products > User access settings > Approved domains.
Select Add domain and enter the URL for the domain you want to approve.
For each product, select a product role and indicate if admin approval is required.
Product role column:
None: Assigns no product role, which means users with the approved domain won’t be able to access that product.
User: Assigns the user role, which allows users to access the product when they are logged in to an account with the approved domain.
Customer: Assigns the customer role to users who access your Jira Service Management help center. They need to be logged in to an account with the approved domain. Learn more about Jira Service Management customer accounts
Admin approval column:
Check Required: Organization admins need to approve access requests from users with the approved domain. Learn more about access requests
Uncheck Required: Users with the approved domain can join your product without approval.
Select how to Notify org admins:
When users get access: Organization admins get an email every time a new user joins.
Only when users need admin approval: Organization admins only get an email when someone requests access to a product.Users on approved domains:
Users with approved domains:
Must create an Atlassian account before logging in to your products.
Can view your products from specific Join Product locations, such as start.atlassian.com
Can join your selected products with or without an invitation.
Must verify their account every 6 months.
Customers on approved domains (Jira Service Management only):
Must create an Atlassian account before accessing your help center.
Can join your selected help center with or without an invitation.
Must verify their account every 6 months.
Configure how users with non-public domains access your products
The Any domains feature allows you to decide how users with non-public email domains access your products. A non-public (or private) email domain is hosted by a private server and is more secure than a public email domain. Examples of public email domains are outlook.com, icloud.com, or gmail.com.
Email domains from private companies are considered to be private domains. Examples of private domains are sony.com, atlassian.com, or samsung.com.
You might use this feature to:
Make it easier for users with a private email domain to request access to your product.
Automatically allow users with a private email domain to join your product. This is also known as an ‘open site’ or ‘open product’.
By default, we configure any domains to allow any user with a private domain to request access to your product (and any new products you add). An organization admin needs to approve these requests first. You can make changes to these default settings at any time.
To manage how users with private email domains access your products:
Go to admin.atlassian.com. Select your organization if you have more than one.
Select Products > User access settings > Approved domains.
Select Any domain.
For each product, select a product role and indicate if admin approval is required.
Product role column:
None: This means people won’t be able to access your product.
User: Allows users to access your selected product when they are logged in to an account with a private domain.
Customer: Assigns the customer role to users who access your Jira Service Management help center. They need to be logged in to an account with a private domain. Learn more about Jira Service Management customer accounts
Admin approval column:
Check Required: Organization admins need to approve every request for access from users with private domains before they can join. Learn more about access requests
Uncheck Required: Users with private domains can freely join your product without any approval from an organization admin. Unchecking this option creates an ‘open site/product’ and users won’t be able to use Atlassian teams.
Select how to Notify org admins:
When users get access: Organization admins get an email every time a new user joins.
Only when users need admin approval: Organization admins only get an email when someone requests access to a product.
Users with private domains:
Must create an Atlassian account before logging in to your products.
Can view your products from specific Join Product locations, such as start.atlassian.com.
Can join your selected products with or without an invitation.
Must verify their account every 6 months.
Customers with private domains (Jira Service Management only):
Must create an Atlassian account before accessing your help center.
Can join your selected help center with or without an invitation.
Must verify their account every 6 months.
User invites
Control how existing users in your organization invite new people to your products. Learn how product access works
To enable user invites:
Go to admin.atlassian.com. Select your organization if you have more than one.
Select Products > User access settings.
Select User invites.
Select an option from the Existing user permissions column next to your selected product.
To restrict user invites:
Go to admin.atlassian.com. Select your organization if you have more than one.
Select Products > User access settings.
Select User invites.
Select the option Don’t allow invites from the Existing user permissions column next to your selected product.
This prevents people who are users or product admins from inviting people through the product. It won’t prevent organization admins and user access admins from doing this. The Invite people feature will still be visible in the product.
You should also check your Approved domains settings to restrict product access.
To restrict product access from approved domains:
Go to admin.atlassian.com. Select your organization if you have more than one.
Select Products > User access settings.
Select Approved domains.
Select a domain to edit.
Select the None product role next to the product you want to restrict access to.
Select Save to confirm.
Repeat steps 7-9 for each of your approved domains.
Existing user permissions
Here’s an explanation of each user permission setting and when you may want to use it:
Existing user permission | How it works |
|---|---|
Invite anyone | This is the most open invite permission. It allows your existing users to freely invite anyone to your product with any email domain. An organization admin doesn’t need to approve this. Anyone can request access to your product. An organization admin needs to approve the request. When to use it This option is best when you trust your existing users to invite and collaborate only with the people they need to. |
Invite approved domains | Existing users can invite anyone with an email domain you have approved (see Approved domains above). An organization admin doesn’t need to approve this. Anyone can still request access to your product, regardless of their domain. An organization admin needs to approve the request. When to use it This option is best when you trust existing users to add and collaborate with people from specific domains you’ve approved, as needed. |
Require admin approval | Existing users can’t invite anyone to your product, regardless of your approved domain settings. Anyone can still request access to your product for themselves or on behalf of someone else. An organization admin needs to approve the request. When to use it This option is best if you want to maintain control over who has access to products, but your company doesn’t have an official process in place for people to ask for access. |
Don’t allow invites | This is the most restricted permission setting for invites available. Users can’t invite anyone or request access to your product. Organization admins and user access admins can still invite users. To further restrict product access, remove your approved domains. When to use it This option is best if you want to maintain strict control over who has access to products, and your company has an internal request/provisioning process you need people to follow (for example an ITSM solution or helpdesk). |
Invitation links
Anyone can use invitation links to get access to your organization and start using a specific product. This is useful if you:
Want to get your team onboarded quickly.
Work with contractors or clients who need fast access.
Once you have shared an invitation link, anyone can use it to join your selected product. For this reason, you should only share links with people you trust. As an added security measure, links automatically expire after 30 days. To render old links invalid before the 30 day expiry period, you can turn off invitation links at any time or regenerate a new link.
To send an invitation link to someone:
Go to admin.atlassian.com. Select your organization if you have more than one.
Select Products from the header.
From the left side of the page, select User access settings > Invitation links.
Select the toggle for the product you want to create an invitation link for. The link will appear below the toggle. Users with the link will land in the product selected.
Copy the invitation link and share it with users you want to give product access to.
Users who join via invitation links are added to the default access groups for that product.
Learn about default groups and permissions
Was this helpful?