Confluence

Connect Confluence to collect compliance as code evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In Confluence:

   1. Signed in as the Atlassian account whose email you will enter, go to https://id.atlassian.com/manage-profile/security/api-tokens.
   2. Select Create API token with scopes (or Create API token for a classic, unscoped token).
   3. Give the token a name that describes its purpose and select an expiration date (1 to 365 days).
   4. For a scoped token, select the app (Confluence) and select the read-only scopes the token needs, then select Create.
   5. Select Copy to clipboard and paste the token into API token. You can't recover the token afterwards.
   6. Optional, for organization-level user data: go to Atlassian Administration (select your organization if you have more than one), then select Organization settings › API keys.
   7. Select API keys with scopes then Create API key (or Create API key then API keys without scopes and Create API key), enter a Name, and select the expiration date (keys can last no longer than a year).
   8. Select Create, then copy the API key into Safeguard's Organization admin API key (optional) field. You can't recover the API key later.

   Where to find the other values:

   • Email: The email address of the Atlassian account that created the API token.
   • Site URL: Your Confluence Cloud site address, https://<your-site>.atlassian.net.
   • Organization ID (optional): Go to https://admin.atlassian.com and select the organization; the ID is in the page URL after /o/ (https://admin.atlassian.com/o/&lt;your_organization_id&gt;/overview).

   Confluence shows the secret only once, so copy it before you leave the page.

   Source: support.atlassian.com, support.atlassian.com, support.atlassian.com, checked 2026-10-07.

   The permissions Safeguard needs: Organization admin API key, read:jira-work. Safeguard's compliance tests for Confluence need the credential on the API token tab: an OAuth connection cannot read everything they check.

2. On Compliance › Connectors, open Confluence, click Connect, choose API token and fill in:

   Field	What to enter
   Email	Required.
   API token	Required. Stored encrypted and never shown again.
   Site URL	Required. For example: https://acme.atlassian.net
   Organization ID (optional)	—
   Organization admin API key (optional)	Stored encrypted and never shown again.

3. Click Connect with token.

Frameworks

Safeguard's automated tests read Confluence and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.

These tests are switched on per workspace by the Safeguard team.

Related

• Compliance As Code connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks