Setup your Atlassian integration and get all the insights in Torii's dashboard
Prerequisites
Before integrating Atlassian, make sure that:
-
You have an organization set up at https://admin.atlassian.com/
-
You are an Organization Admin and not just a Site Admin.
More information is available here. -
At least one domain has been verified for that organization
-
You see users on your Atlassian admin dashboard
Integration
Torii integrates with your Atlassian Cloud installation and syncs each Atlassian product's list of users, licenses, and last usage date.
You will need to provide your Organization ID and API Key for the integration.
Connect Atlassian integration to Torii
-
Go to the Integrations page
-
Connect to Atlassian
-
Select the permission level
-
Mandatory - enter the Organizational ID
-
Mandatory - Create an API key
- Go to admin.atlassian.com. Select your organization if you have more than one.
- Select Settings > API keys.
- Select Create API key in the top right.
- Enter a name that you’ll remember to identify the API key.
Please note: By default, the key expires one week from today. If you’d like to change the expiration date, pick a new date under Expires on. You’re unable to select a date longer than a year from the date of creation. - Select Create to save the API key.
- Copy the values for your Organization ID and API key, and paste them into the required fields in Torii (4+5)
The following fields (6&7) are optional; fill them in only if you want to use Torii to "Create and delete users."
Please note the following:
- Atlassian prerequisites for configuring user provisioning
- Verify your domain using DNS or HTTPS method, and NOT Google Workspace -
Paste the Provisioning API Key / SCIM Token
-
Paste the Directory ID, note to paste only the final part of the “Directory Base URL”, For example - https://api.atlassian.com/scim/directory/
[DIRECTORY_ID]
Click here for Atlassian's instructions.
-
Click Connect
-
Repeat for every team you wish to connect
Additional Notes
Actions
- For creating/deleting users: Syncing Atlassian users into the newly created Directory, using the customer identity provider is required.
- For adding/removing users from groups: users can only be added and removed from groups created in Atlassian and not via an external directory. In addition, based on your Atlassian setup, some groups can not be added to (such as "atlassian-addons-admin" and other predefined groups) or removed from (such as "org-admins").
- Note if you try to delete a user (using Torii action) that hasn’t synced into the newly created directory, the deletion action will succeed with the message “User Not Found”
Get additional information in Atlassian and Jira Cloud Integrations: A more profound look.
Retrieving licenses for specific sites
- The Atlassian API does not provide any information on whether a user has a paid license or not, nor whether they are using a company or personal domain. As such, Torii models each user who returns from the API as having a general license for the sub-app in Atlassian (Jira etc.).
- To help differentiate between paid users and users logging in using non-company domains, Torii provides support for bringing in license data for specific sites only.
- During integration connection, you can fill in the optional "Get licenses only from these sites" field. You can fill in as many sites as you want, comma-separated, and instead of fetching all licenses found, Torii will only fetch licenses from those sites.
Q&A
Q: Which licenses are synced?
A: Licenses for the products listed under the "Product access" dropdown are synced; valid to April 2022 are: Analytics, Bitbucket, Compass, Confluence, Jira Administration, Jira Ops, Jira Product Discovery, Jira Service Management, Jira Software, Jira Work Management, Opsgenie, Statuspage, Team Central, and Trello.
A: According to this Atlassian document: deactivated users immediately lose access to Jira Cloud and all other Atlassian account services.