Connect Atlassian to Black Cat SSPM
Connect your Atlassian organization so Black Cat can review users, multi-factor coverage, API tokens, groups, and Jira and Confluence sharing settings.
≈ 10 min · audit access · no write-capable permission
What Black Cat reads, and why
| Permission | What it lets Black Cat do | Status |
|---|---|---|
org.admin.policy.read | Lets Black Cat review organization policies such as two-step verification, data residency, IP allowlisting and external user rules. | Required |
org.admin.event.read | Lets Black Cat see administrative events, including permission and role changes. | Required |
read:jira-work | Lets Black Cat review Jira project permissions and whether any project is open to the public. | Optional |
read:confluence-space.summary | Lets Black Cat review Confluence spaces and whether anonymous or public link access is allowed. | Optional |
org.admin.user.read | Lets Black Cat list users, their product access, account status and last activity. | Optional |
org.admin.group.read | Lets Black Cat list groups and their membership, including groups nobody belongs to. | Optional |
org.admin.token.read | Lets Black Cat list user API tokens, their labels and how old they are. | Optional |
org.admin.directory.read | Lets Black Cat see how accounts are provisioned into your organization directory. | Optional |
What you'll need
- Organization identifier Required — Shown in the address bar of admin.atlassian.com when you open your organization.
- Organization API key Required — Created by an organization admin in the Atlassian admin console, under API keys.
- Site names to review — Optional — a comma-separated list of Jira and Confluence sites; leave it empty to cover the whole organization.
Where to create it
- Setup guide (Atlassian) ↗ (opens in new tab)
- Developer documentation (Atlassian) ↗ (opens in new tab)