Confluence

Liddr reads pages from the configured space during ingest, and — for reverse sync — publishes approved architecture ADRs as pages into that space. Confluence reuses the Jira connector's Atlassian email + API token, so configure Jira credentials first.

What Liddr accesses

Direction	Access
Ingest (read into your knowledge graph)	Read-only
Reverse sync (Liddr writing back)	Read & write — only when a Forge action publishes back to this source

Setup

1. Ensure the Jira connector has a working email + API token (same Atlassian account).
2. In Liddr: Settings → Connections → Confluence, set the Confluence base URL if it differs from <jira base URL>/wiki (the default).
3. Set the Space Key in the connector's Advanced settings — comma-separated for multiple spaces.
4. Test, then run an Ingest.

Required scopes

Classic API token (recommended)

Ingest — minimum

• No token scopes — access follows the account's Confluence permissions
• Account needs: View permission on each configured space

Reverse sync — additionally

• Account needs: Add pages permission in the space ADRs publish to

TIP

Minimum equals maximum: grant the service account only the configured spaces via space permissions — published ADR pages will show that account as the author.

API token with scopes

Ingest — minimum

• read:confluence-content.all
• read:confluence-space.summary

Reverse sync — additionally

• write:confluence-content

TIP

Choose "API token with scopes" and select Confluence. Space permissions still apply on top of the scopes.

Reference

• Atlassian docs: manage API tokens