Introduction
This integration enables Sana to ingest and provide access to confluence pages and permissions.
Integration capabilities
The integration allows read operations to your Confluence pages inside of Sana Agents.
Operation type | Supported |
Read | ✅ |
Write | ❌ |
Indexed content:
Operation type | Supported |
Space | ✅ |
Pages | ✅ |
Whiteboard | ❌ |
Database | ❌ |
Blog | ❌ |
Smart Link | ❌ |
Asset limit:
Enterprise tier: 50000 assets
Common use-cases:
Ask questions about content in your confluence pages.
Type of integration
Centralized: Set up per workspaces mirroring the underlying individual access rights for all users.
Availability
Integration type | Free tier | Team tier | Enterprise tier |
Private | ❌ | ❌ | ❌ |
Shared | ❌ | ❌ | ❌ |
Centralized | ❌ | ❌ | ✅ |
Scope and permissions
Scope | Purpose |
Authentication (User details, email) | Verify who the user is and allow access via API rest |
Content and Assets (Content metadata, Content Permission, Custom content, Content attachments, Blogpost, Comments, Content Property, Content restrictions) | Get content details, content and permissions to import to Sana. |
Configuration ( Space permissions, Space details,Space properties, Space settings) | Get space details to define scope of integration and space source of the sync process |
Additional access (Database, Smart Link, Folder, Groups, Inline tasks, Labels) | Allow to get pages that might be child of non-pagers files as well as inherited permissions. |
Integration set-up
To set up confluence centralized properly, 2 steps are required:
Step 1: Confluence admin approves Sana inside Confluence
Step 2: Workspace admin set up Confluence Centralized
Step 3: Everyone set up Confluence (User Permissions Only)
Important note:
All users must set up the integration “Confluence (User Permissions Only)” because Confluence requires each user to grant consent to fetch asset permissions.
Step 1: Confluence admin approves Sana inside Confluence
Sana needs to be approved by a confluence site admin. This can be done in two alternative ways:
The confluence system admin is the one who sets up the centralized Confluence inside of Sana Agents, see "Step 2: Workspace admin set up Confluence" below.
The confluence system admin grants access to the app by navigating to http://admin.atlassian.com/ -> products -> select the site -> connected apps --> settings and enables the two apps "Sana AI (Centralized)" and "Sana AI (Permissions)".
Step 2: Workspace admin set up Confluence
1. Find and click on “Confluence” inside of the list of available integrations.
2. Click “Connect centralized”
3. Sign in to your Atlassian account and accept required scopes
4. Select space to be connected. Either choose all by clicking “Sync all of my Confluence spaces” or select specific spaces to include in the dropdown below.
5. Double check that “Confluence Centralized” is now listed as a connected integration on the integrations page.
Step 3: Everyone set up Confluence (User Permissions Only)
1. Find and click on “Confluence (User Permissions Only)” inside of the list of available integrations.
2. Click “Connect just for me”
3. Sign in to your Atlassian account and accept required scopes
4. Double check that it “Confluence (User Permissions Only)” is now listed as a connected integration on the integrations page.
Known limitations
All users must set up the integration “Confluence (User Permissions Only)” because Confluence requires each user to grant consent to fetch asset permissions.
Sana Agents does not support write operations (i.e., creating and updating new pages)
Sana Agents only supports Pages. Other formats (e.g., Whiteboard and Databases) are not discovered, which means they do not appear as “unsupported file formats”.
Sana Agents does not support filtering by space; only individual pages. Selecting a space in Sana limits conversations to the homepage of that space, not the entire space.
Sana Agents do not show folder structures or understand folder hierarchies, but all pages inside those folders are still accessible
FAQ
Q: How often are the pages synced?
A: This integration is an asset based integration which means that it ingest confluences pages This means that your data needs to be synced regularly, this process will run once a day updating pages and permissions.
Q: Why do I also need to connect the integration “Confluence (User Permissions Only)” if it's a centralized Confluence integration? Shouldn’t my permissions be mirrored already?
A: All users must set up the integration “Confluence (User Permissions Only)” because Confluence requires each user to grant consent to fetch asset permissions.
Q: Can I view other peoples pages?
A: Not completely, you can only see pages that are public or that have been explicitly shared with you or a group that you belong to in confluence.
Q: Can I create, update or delete pages in Confluence through Sana?
A: No, this integration currently only supports read operations.
Data handling & privacy
Sana AI is fully committed to data security and privacy. All data accessed by Sana AI is encrypted both in transit and at rest. Sana does not train any underlying language models on your data, ensuring the privacy of your information. Sana AI is ISO 27001 certified; and SOC 2 and GDPR compliant, and adheres to the highest standards of data security.