Confluence
A Confluence Cloud site and the spaces containing approved company knowledge
Ownership and availability
You retain ownership of the Atlassian site and its spaces. Obelo encrypts the OAuth credentials and remains limited by the authorizing user's Confluence permissions.
Start in Settings → Integrations and check the provider’s current status. This guide describes the configured setup path, not a guarantee of production enablement. Provider approval, plan access and resource permissions still apply.
Before you connect
- A Confluence Cloud account with access to the target site and spaces
- Permission to authorize an OAuth app for the Atlassian site
- An Obelo workspace owner or admin completes authorization
Connect an existing account
- Open the provider in Settings → Integrations for the intended website.
- Select the Atlassian site that belongs to this company
- Approve the minimum content, space-summary, and offline access requested by Obelo
- Return to Obelo and verify the site before using Confluence content
If you need a new resource
- Create a Confluence Cloud site and a marketing or company-knowledge space
- Add the pages and reference material approved for Obelo
- Invite the teammate who will authorize the site connection
Permissions to check
- Content and space read access lets Obelo retrieve only material the authorizing user can already view
- Content write access is used only for approved page creation; offline access keeps scheduled workflows connected
Verify and troubleshoot
After the site and knowledge space are ready, return and authorize the Confluence connection.
Confluence returned no accessible site or space. Choose a different Atlassian site or ask its administrator for access, then reconnect.
Confirm the selected account or resource and inspect the verification or sync result. A saved connection is not proof that an import or publication has completed. Test the intended workflow with an appropriately reviewed item.
Disconnect or change access
Use the provider’s management controls in Obelo to disconnect when supported. Revoke the grant or rotate a dedicated credential at the provider if access must end immediately. Review already-imported data separately; disconnection does not remove content already published elsewhere.
Something unclear or out of date?
Suggest a correction