Confluence integration

"Bring team knowledge into your GRC workspace — browse, create and edit Confluence pages from Brainframe, and import them as live documents in your folders."
Connect your Atlassian Confluence Cloud site, search pages across spaces, and pull policies, runbooks and evidence into Brainframe without copy-pasting.

The Confluence integration connects Brainframe to Confluence Cloud through the Confluence REST API v2 (API token authentication). Once configured, you can manage pages from the integrations area — and import Confluence pages as Brainframe documents so they stay linked to the source page and can be viewed and edited in context.

Confluence is classified as a Documents integration (alongside SharePoint and similar connectors), not a Tasks integration. You add Confluence content from folder and table views; the document bolt (⚡) menu is reserved for task integrations (JIRA, Asana, Monday.com, Azure DevOps, etc.).

1️⃣ Before You Begin

To configure the integration you will need:

• 🛠 A Brainframe account with permission to save credentials (see Credential scope below).
• 🔐 An Atlassian account with access to the Confluence Cloud site on your domain (e.g. yourcompany.atlassian.net).
• 🎫 An API token for that account at Atlassian API tokens.
• 📂 Sufficient Confluence permissions to view, create and edit pages in the spaces you expect to use.

⚠️ Brainframe targets Confluence Cloud (*.``atlassian.net with /wiki REST paths). Self-hosted Server/Data Center sites are not supported by the current integration model.

💡 If you already use the JIRA integration on the same Atlassian site, you can reuse the same domain, email and API token — but you must save a separate Confluence credential entry in Brainframe (each integration type has its own configuration).

2️⃣ Configure the Integration

Step 1 — Create an API token in Atlassian

1. Log in to your Atlassian account.
2. Open Atlassian API tokens.
3. Click Create API token, give it a label (e.g. Brainframe GRC – Confluence), and copy the token immediately.
4. Note the email address of the Atlassian account that owns the token.

📌 The token inherits that user’s Confluence space permissions. For workspace-wide access, use a service account with access to the relevant spaces.

Step 2 — Enter credentials in Brainframe

Go to Workspace Settings → Integrations → Confluence → Configure (/integrations/confluence/config).

Fill in:

Then click Save configuration. Brainframe validates the credentials against the Confluence API before storing them.

📌 If no credentials exist yet, opening Confluence Pages redirects you to this configuration page automatically.

Credential scope

Individual credentials take priority over workspace credentials when both exist for the same user.

Legacy workspace credentials

Older workspaces may still have legacy Confluence credentials from the previous auth/addIntegration flow (domain, email, token stored as CONFLUENCE).

• If only legacy credentials exist, Brainframe uses them automatically.
• The configuration page shows a Legacy Confluence credentials detected notice when this applies.
• Saving new encrypted credentials replaces the legacy row.

To remove legacy credentials without adding new ones, use Delete legacy configuration on the config page (admin).

3️⃣ Using the Confluence Integration Page

Open Workspace Settings → Integrations → Confluence (or the Integrations sidebar menu when Confluence is enabled).

The gear icon opens credential configuration. New page opens the create form.

🔎 Search and filters

Results are paginated (Load more, 25 pages per request). The header shows Showing X pages.

📊 Page table

➕ Create, view, edit and delete

Create / edit fields

Imported documents show page content as HTML in view mode (sanitized) and support markdown editing in edit mode, using the same editor component as JIRA descriptions.

4️⃣ Document Integrations — Importing Pages into Folders

Confluence pages enter your GRC workspace primarily through import, not through the document bolt menu.

Add from integrations (folder NEW menu)

In any folder, open the NEW menu (plus button):

1. Choose Add from integrations (cloud icon).
2. The integrations browser opens in import mode.
3. Filter by Documents (optional) or pick Confluence from the catalog.
4. Search for pages, or click New page to create one in Confluence first.
5. Click Import on a row, or select multiple pages and use bulk import.
6. Choose the target folder and document type in the folder selection step.

The imported document points to the live Confluence page. Opening it shows the inline Confluence viewer inside the Brainframe editor — title, metadata, body, Edit, Open in Confluence, and Delete (which removes the page in Confluence and can archive the Brainframe document).

Add from integrations (table view)

In a table view toolbar, click the cloud button:

• Tooltip: Add from integrations
• Same import browser as the folder NEW menu.
• Pre-selects the current table’s document type when you pick a folder/type for import.

Use this to build a table of linked Confluence policies, procedures, meeting notes, or evidence pages alongside native Brainframe documents.

Inside the Confluence browse step

📌 Import creates a new document in the folder you choose. It does not automatically link the page as a sub-task under another open document. For task-style linking, use a Tasks integration (JIRA, Asana, …) from the document bolt → Task from integrations menu instead.

5️⃣ Document Bolt Menu — What Confluence Does Not Do

The document header bolt (⚡) menu includes Task from integrations, which opens the browser filtered to Tasks integrations only:

• JIRA, Asana, Monday.com, Azure DevOps, SolarWinds Service Desk, …

Confluence is not listed there — it is a Documents integration. To add Confluence content while working on a document, import the page into a folder (section 4) and link it to your GRC record using normal Brainframe Link to other document flows if needed.

Other bolt menu items (unchanged):

6️⃣ Inline View on Imported Documents

When a Brainframe document is tied to Confluence:

• The editor area renders Confluence Inline View instead of a static HTML snapshot.
• Content is loaded live from Confluence on each view.
• Edit updates title and body in Confluence; changes appear on refresh.
• View in Confluence / Open in Confluence opens the canonical page in Atlassian.
• Delete removes the page in Confluence; the Brainframe document can be archived.

This replaces the older legacy model that imported a one-time HTML snapshot with an embedded “Open in Confluence” button.

7️⃣ Sidebar Integrations Menu

When Confluence is configured and enabled for your user/group, it appears under Integrations in the sidebar (among enabled integrations).

• Opens /integrations/confluence — the page browser described in section 3.
• Greyed-out entries mean the integration is visible in menu configuration but not enabled or not accessible — ask an administrator to enable it under Workspace Settings → Menu interface.

8️⃣ Permissions Summary

📌 All Confluence API calls are proxied through the Brainframe backend. Tokens are never exposed to the browser after save.

9️⃣ Tips for GRC Use Cases

🔟 Troubleshooting

Related integrations

For task linking from documents, see the JIRA integration documentation. For directory and security imports, see Microsoft Entra ID and Aikido documentation respectively.

Updated on: 14/07/2026