Connect & Integrate Atlassian

Last updated: May 13, 2026

Introduction

This guide covers using YeshID's Atlassian integration to connect your Atlassian Cloud organization.

Once connected, YeshID imports:

  • Users and group memberships

  • Groups

  • Directories

  • Domains

  • Workspaces (Jira, Confluence, etc.) and their access grants

  • Service accounts

  • API tokens

YeshID can also create users (by inviting them to a directory) and deactivate users. Write actions require a concrete Directory ID; read-only imports work across all directories.

Steps

  1. Sign in to Atlassian Admin Sign in to https://admin.atlassian.com as an organization administrator.

  2. Find your Organization ID In the admin console, your Organization ID is the UUID in the URL once you've selected an organization (e.g. https://admin.atlassian.com/o/<organization-id>/...). Copy it.

  3. Create an API key Navigate to Settings → API keys and click Create API key.

    • Name: YeshID

    • Type: API Key (without scopes)

    • Expires on: pick a date that matches your rotation policy

    Copy the API key value when shown — you can't view it again after closing the dialog.

  4. (Optional) Note your Directory ID If you want YeshID to create or deactivate users, you need a concrete Directory ID. Find it in Settings → Directory in the admin console, or leave the field as - to import across all directories in read-only mode.

  5. Connect the integration in YeshID In YeshID, open the Atlassian integration and enter:

    • Organization ID — from step 2

    • API Key — from step 3

    • Directory ID — a concrete directory ID for write actions, or - for read-only imports across all directories

    • Use Lifecycle API (optional) — enable to deactivate/activate users via Atlassian's Lifecycle API instead of the org suspend/restore endpoints

    Save the integration.

  6. Run a sync Start an Import Users and Import Resources sync. YeshID pulls users, groups, directories, domains, workspaces, service accounts, and API tokens under your organization.

FAQ

What permissions does the API key need?

The API key inherits the permissions of the organization administrator who creates it. Create the key as a user with Organization admin access so YeshID can read directories, groups, workspaces, and API tokens.

Why - for Directory ID?

Atlassian's v2 directory endpoints accept - as a wildcard that returns users across all directories in the organization. YeshID uses this for read-only imports. Write actions (create user, deactivate user) require a real directory ID because they target a specific directory's user store.

Should I use a real user or a service account?

A dedicated Atlassian service account or bot user is recommended. It keeps the integration working when a real user leaves and isolates the scope of access. Make sure it has Organization admin rights.

What's the difference between Lifecycle API and suspend/restore?

The Lifecycle API is Atlassian's newer endpoint for managing user state and gives you finer control over deactivation reasons and audit metadata. The legacy suspend/restore endpoints toggle access at the org level. If you're unsure, leave Use Lifecycle API off — YeshID's default is the org suspend/restore path.

Why are some workspaces or tokens missing?

If the API key's owner doesn't have admin visibility into a workspace or API token, YeshID skips it rather than failing the whole import. Re-issue the API key as an Organization admin to surface everything.

What happens if my sync hits a rate limit?

YeshID automatically backs off and retries on Atlassian 429 responses, honoring Retry-After when Atlassian provides it and applying exponential backoff with jitter otherwise. Atlassian Cloud enforces three independent limits (per-second burst, hourly points quota shared across tenants, per-issue write) and YeshID handles all three. Large imports may take a little longer near these limits, but they will complete.

Does this integration require any Atlassian product subscription?

You need a paid Atlassian Cloud organization. The integration uses Atlassian's admin APIs, which are available on all paid plans. Free plans have limited admin API access.