Atlassian
The Atlassian connector supports Identity & Access collection from Jira and Confluence. You can select which of those products Superviso should include.
Required values
- Email for the Atlassian account associated with the token
- API Token created for that account
- Domain for the Atlassian site, such as
example.atlassian.net
Required access
The account must have administrator access sufficient to read users and groups. The connector identifies this as the
Administrators privilege.
Use a dedicated account where practical and enable only the Jira or Confluence collection options you need.
Before you start
Create the credentials listed above in the provider’s administration tools.
Configure in Superviso
- Open Settings → Connectors and choose Add connector.
- Select Atlassian from Provider.
- Associate the intended asset, or use the new-asset option when appropriate. Enable only the supported synchronization options you need.
- Enter Email, API Token, and Domain. Enable only the required Jira and Confluence filters.
- Recheck the required privileges, scope, and filters, then choose Create connector. Resolve any validation errors shown by the form.
- Open the saved connector, choose Sync connector when available, and confirm the synchronization scope.
- Open Logs, wait for execution to finish, and inspect the result and any errors. Open the relevant Identities, Privileges, or Resources page for the enabled integration to verify collected records.
Expected outcome
The connector is saved for Atlassian with the intended integration and collection scope. Synchronization logs show progress, results, and imported records.
If setup or synchronization fails
Check the exact account or organization identifier, required form values, credential validity, granted access, and selected filters. Inspect the failed log’s details before retrying. If only some records are missing, check their scope and provider permissions. For synchronization status and source-managed fields, see Connectors and synchronization logs.