Integration Guide: Atlassian Cloud

Published Date: June 24, 2026 | Last Updated: October 9, 2026

Overview

The Atlassian Cloud integration connects Seasoft Identity to the Atlassian organization, allowing Seasoft Identity to monitor and manage user access across Atlassian products such as Jira and Confluence. The connection requires four values: the Organization ID, an Admin API Key, a SCIM URL, and a SCIM Bearer Token.

Before connecting

The Administrator completing this setup must have Org Admin access in Atlassian Admin. The Administrator will need to complete two steps in Atlassian before configuring the integration in Seasoft Identity: creating an Admin API Key and setting up a User Provisioning directory to obtain the SCIM URL and Bearer Token.

API key expiration: Atlassian API keys expire after a maximum of one year. Schedule a recurring task to regenerate the key and update the integration in Seasoft Identity before it expires to avoid an authorization failure.

Step 1: Locate the Organization ID

The Atlassian Organization ID is found in the Atlassian Admin URL after signing in at admin.atlassian.com. It appears in the URL in the format: admin.atlassian.com/o/<organization-id>/...

Copy this value — It is needed when configuring the integration in Seasoft Identity.

Step 2: Create an Admin API Key

Navigate to admin.atlassian.com/o/<your-org-id>/api-keys or go to Atlassian Admin and select Settings → API keys.
Select Create API key.
When prompted, select API key without scopes.
Enter a name for the key (for example, Seasoft Identity) and set an expiration date. Keys can last no longer than one year.
Select Next, review the key details, and select Create API key.
On the confirmation page, copy both the Organization ID and the API key. The API key is only displayed once and cannot be recovered after this step.

Important: Copy the API key before closing this page. It will not be shown again. If lost, a new key must be created.

Step 3: Set up User Provisioning and obtain SCIM credentials

Seasoft Identity also requires a SCIM URL and SCIM Bearer Token from Atlassian. These are generated when the Administrator adds an identity provider directory under User Provisioning in Atlassian Admin.

In Atlassian Admin, navigate to Directory → User provisioning.
Select Add identity provider directory.
Set Identity provider to Other provider and enter a directory name (for example, Seasoft Identity). Select Add.
Atlassian generates a SCIM URL and Bearer Token. Copy both values immediately — the Bearer Token is only shown once.

Step 4: Connect Atlassian Cloud in Seasoft Identity

Navigate to Integrations in the left navigation.
Select + Add Integration.
Search for Atlassian Cloud and select Add.
Enter the Organization ID.
Enter the SCIM URL from Atlassian Directory → User provisioning.
Enter the Admin API Key generated in Step 2.
Enter the SCIM Bearer Token from Atlassian Directory → User provisioning.
Select Test Connection to verify all values are valid. A Connection successful confirmation will appear if accepted.
Select Connect. The integration appears on the Integrations page and an initial sync begins automatically.

Verify the connection

After the initial sync completes, confirm the following on the Integrations page:

The Atlassian Cloud integration displays a status of Active
A sync timestamp is present and reflects the completed sync
User records on the Users page display detected Atlassian permissions in the Access column

Reauthorizing the connection

If the integration loses authorization — most commonly due to an expired API key — it will display an error on the Integrations page. Generate a new API key in Atlassian Admin, then select the integration row in Seasoft Identity, select Configure, and enter the new key.

Configuring Integrations — manage sync schedules, drift detection, and integration settings
Understanding Errors — resolve integration errors and authorization failures