Skip to main content
Confluence Logo
Confluence Cloud

Team workspace and documentation platform

✅ Ready📖 Documentation Available

​
Overview

Confluence is Atlassian’s team workspace and documentation platform, widely used for knowledge bases, product docs, meeting notes, and collaborative content. The Confluence connector syncs spaces, pages, blog posts, comments, attachments, and user information, enabling comprehensive knowledge-base search across your Confluence content.
This page is for Confluence Cloud, the version Atlassian hosts for you. If you run Confluence on your own servers, use the Confluence Data Center connector instead.

​
What Gets Synced

​
Configuration Guide

The accessible Confluence Cloud connector registers Index Page Comments and Index Blogpost Comments, but its reviewed sync path does not read those two indexing settings. Do not rely on either toggle to exclude comments until Novaplan verifies its behavior in the deployed Enterprise version. If comments must be excluded, agree on a verified source or connector scope before syncing sensitive spaces.
The Confluence connector supports two authentication methods. Both sync the same data — pick whichever fits your rollout.

​
Verify Confluence account mapping

Test account mapping with representative users before asking everyone to change Atlassian profile visibility. Making an email visible is a privacy decision and may not be necessary when the connector can resolve the account through Jira.
This check applies to both authentication methods (OAuth and API Token). Why mapping matters. Novaplan AI uses email addresses to match Confluence users with their permissions. The accessible connector skips users whose email is absent from Confluence’s user search, but it can also try to link active workspace users through Jira user search. For OAuth, that fallback requires Grant Jira user access and the read:jira-user scope in the Atlassian app. The fallback may fail if Jira is unavailable, lacks permission, or cannot find the user; verify the deployed result before changing profile settings. If an affected user needs to change visibility, they can review these settings in their Atlassian account:
  1. Click your profile picture in the top right → select Account Settings.
Access User Profile Settings
  1. Select the Profile and visibility tab.
  2. Scroll down to the Contact section.
  3. In the Who can see this? dropdown for your email address, consider Your organization if your administrator confirms that a visibility change is needed and your privacy policy permits it. Anyone makes the address more broadly visible.
Set Email Visibility to Organization
Only you and admins may prevent Confluence user search from returning the address, but the Jira lookup can still resolve some users when configured. Test the mapping rather than assuming success or failure.
📖 Official documentation: Configure User Email Visibility in Confluence
Profile email visibility is a per-user setting. Coordinate a change with the affected person and your privacy administrator only after a mapping test shows it is needed.

​
Choose an authentication method

​
Step 1: Access the Atlassian Developer Console

  1. Go to developer.atlassian.com/console/myapps/ and sign in with your Atlassian account (must have admin access to your Confluence workspace).
  2. You’ll see the My apps page where you create and manage OAuth 2.0 integrations.
Atlassian Developer Console - My Apps

​
Step 2: Create a new OAuth 2.0 integration

  1. Click Create in the top-right corner.
  2. Select OAuth 2.0 integration from the dropdown.
  3. Fill in the application details:
    • Name: Enter a meaningful name (e.g., Novaplan AI Confluence Connector).
    • Access type: Select Resource-level.
    • Check the box to agree to Atlassian’s developer terms.
  4. Click Create.
Create OAuth 2.0 Integration Form
You must select “Resource-level” access type. Novaplan AI does not ask for a site URL — the connector uses the exact site you authorize during the OAuth step. If you choose Account-level, authentication will not work.
OAuth 2.0 (3LO) integrations use rotating refresh tokens by default, which improves security by limiting token validity and enabling automatic detection of refresh-token reuse.

​
Step 3: Review the application overview

After creation, you’ll land on the app overview page. It shows:
  • App ID — your application’s unique identifier
  • Distribution status — whether the app is shared publicly
  • Permissions — API scopes configured for the app
  • Authorization — OAuth 2.0 (3LO) authorization settings
Use the left sidebar to navigate between Permissions, Authorization, and Settings.
Application Overview Page

​
Step 4: Configure OAuth 2.0 authorization

  1. In the left sidebar, click Authorization.
  2. Find OAuth 2.0 (3LO) in the authorization types list.
  3. Click Add to enable OAuth 2.0 authorization for your app.
Add OAuth 2.0 Authorization
  1. Get the Redirect URL from Novaplan AI:
    • In Novaplan AI, go to Workspace Settings → Connectors, find Confluence, and click + Setup for a new instance.
    • The connector panel opens as a right-side drawer. On the Authenticate Instance tab, copy the Redirect URL.
Novaplan AI Confluence Authenticate Instance tab — copy the Redirect URL
  1. Paste the copied URL into the Callback URL field in Atlassian Developer Console.
  2. Click Save changes.
Add Callback URL in Atlassian
The Callback URL must match exactly between Atlassian Developer Console and Novaplan AI. Any difference — trailing slash, protocol, casing — causes authentication to fail.

​
Step 5: Add API permissions

  1. In the left sidebar, click Permissions.
  2. You’ll see a list of available Atlassian APIs.
  3. Add scopes for both User identity API and Confluence API.
Add API Scopes
User Identity API scopesClick Add next to User identity API and select:
User Identity API Scopes
The offline_access scope is automatically included when you configure OAuth 2.0 (3LO). It enables refresh tokens so scheduled synchronization continues when users are not actively logged in.
Confluence API — Classic scopesClick Add next to Confluence API. You’ll see two tabs: Classic scopes and Granular scopes. Configure scopes from both.First, the Classic scopes tab:
Classic scopes provide broader access patterns required for certain API endpoints. Some features may not work correctly without them.
Confluence API — Granular scopesNext, the Granular scopes tab. Add these read permissions:
Confluence API Granular Scopes - Part 1
Confluence API Granular Scopes - Part 2
Atlassian recommends not adding more than 50 scopes to your app. Both Classic and Granular scopes are required for full connector functionality.

​
Step 6: Copy Client ID and Client Secret

  1. In the left sidebar, click Settings.
  2. Scroll to the Authentication details section.
  3. Copy:
    • Client ID — used as Client ID in Novaplan AI.
    • Secret — used as Client Secret in Novaplan AI. Copy it immediately.
OAuth 2.0 Credentials
Store the Client ID and Client Secret securely. The secret can be regenerated if needed, but you’ll have to update your Novaplan AI configuration with the new value.

​
Step 7: Authenticate Instance tab — enter credentials

The connector drawer in Novaplan AI has three tabs: Authenticate Instance, Authorize, and Configure Records. Start on the Authenticate Instance tab.
  1. Confirm the Redirect URL matches the Callback URL you saved in Atlassian in Step 4.
  2. If your admin has pre-registered an OAuth app, pick it from the OAuth app dropdown. Otherwise leave it blank and enter credentials manually.
  3. Enter:
    • Client ID — from Step 6
    • Client Secret — from Step 6
    • Grant Jira user access — select Yes or No (see note below).
  4. Click Next to move to the Authorize tab.
Authenticate Instance tab — enter Client ID, Client Secret, and Grant Jira user access
Grant Jira user access. Choose Yes only if your Atlassian OAuth app includes Jira and you’ve added the read:jira-user scope. Novaplan AI will request that scope during authorization and may use Jira to resolve user emails when Confluence profiles hide them. Choose No if you don’t use Jira on this site or haven’t added that scope.

​
Step 8: Authorize tab — complete the OAuth flow

On the Authorize tab, all the OAuth authorization work happens. The tab shows an Authenticate button to kick off the OAuth handshake.
Novaplan AI Authorize tab with the Authenticate button
  1. Click Authenticate to start the OAuth flow. A popup opens to Atlassian’s authorization page.
  2. Select your Confluence site from the dropdown.
Choose Confluence Site
Authorize this shared Team connector with the Atlassian account agreed with your administrator. It needs access to the Confluence spaces you intend to sync. Each viewer’s email and Confluence permissions are matched separately in Novaplan AI.
  1. Review the permissions requested by the connector and click Accept.
Accept OAuth Permissions
  1. The popup closes and returns you to Novaplan AI. The connector tile shows an Authenticated badge with a Reauthenticate option.
  2. Click Next to move to the Configure Records tab.

​
Step 9: Configure Records tab — sync settings, filters, and indexing

On the Configure Records tab, control how the connector syncs and what gets synced.Sync settings — configure your synchronization preferences first:
  1. Sync Strategy — Scheduled or Manual.
  2. Sync Interval — how often to sync (default: 60 minutes).
Configure Sync Strategy
Scheduled sync runs automatically at the specified intervals. Manual sync requires you to trigger synchronization on-demand.
Sync filters — narrow the spaces, pages, and blog posts processed by this Team connection. The accessible connector still reads Confluence users and groups for identity and permission mapping. Do not treat these content filters as a guarantee that no other source metadata is read.
Confluence Filters Configuration
Available sync filters:
  1. Space Keys — filter by Confluence spaces.
    • Operator: In (include only) or Not In (exclude)
    • Value: one or more space keys (e.g., ENG, MKT, PROD). Space keys are case-sensitive.
    • Finding space keys: check your space URL — https://yourinstance.atlassian.net/wiki/spaces/SPACEKEY/overview — the SPACEKEY is what you need.
  2. Page IDs — filter specific pages (includes all child pages automatically).
    • Operator: In or Not In
    • Value: one or more page IDs (e.g., 88375321, 90341377)
    • Finding page IDs: check your page URL — the number after /pages/ is the page ID.
  3. Blogpost IDs — filter specific blog posts.
    • Operator: In or Not In
    • Finding blogpost IDs: the number after /blog/YYYY/MM/DD/ in the URL.
  4. Modified Date — filter by last modification date. Operators: Is After, Is Before, Is Between.
  5. Created Date — filter by creation date. Same operators.
Indexing filters — are intended to control which synchronized pages, blog posts, comments, and attachments are processed for AI search. Turning indexing off does not by itself prevent source retrieval. Verify the comment controls as described in the warning above.
  • Pages: Index Pages / Index Page Attachments / Index Page Comments (all default: enabled)
  • Blog posts: Index Blogposts / Index Blogpost Attachments / Index Blogpost Comments (all default: enabled)
Example configurations:
  • Sync only Engineering space: Space Keys → Operator In, Value ENG
  • Exclude archived spaces: Space Keys → Operator Not In, Value ARCHIVE, OLD
  • Sync specific documentation tree: Page IDs → Operator In, Value 88375321
  • Recent content only: Modified Date → Operator Is After, Date 2024-06-01
  • Index pages but not attachments: disable the Index Page Attachments toggle
Click Save to save your configuration. Novaplan AI confirms the instance is ready with a final dialog — “Instance is configured and ready to sync” — offering two choices: I’ll do it later or Start syncing now.
Instance is configured and ready to sync — I'll do it later or Start syncing now
Choose Start syncing now to kick off the initial sync immediately, or I’ll do it later to enable the connector without an immediate sync. Monitor the Indexing Progress to track sync completion.

​
Supported Features

The Confluence connector syncs the following data from your Confluence Cloud workspace:
  • Spaces — all accessible spaces and their configurations
  • Pages — full page content with formatting preserved
  • Blog Posts — all blog post content and metadata
  • Comments — comments on pages and blog posts
  • Attachments — files attached to pages and blog posts
  • Users — user profiles and account information
  • Groups — user groups and memberships
  • Permissions — content restrictions and space permissions
  • Folders — folder structure and organization
  • Audit Logs — activity records for compliance
This connector works with Confluence Cloud only. If you run Confluence on your own servers, use the Confluence Data Center connector.

​
Troubleshooting

​
Common issues

Invalid client credentials error (OAuth):
  • Verify Client ID and Client Secret are correct — no extra spaces
  • Check that the OAuth app is active in Atlassian Developer Console
  • Regenerate the secret if necessary and update Novaplan AI
Callback URL mismatch error (OAuth):
  • Ensure the Redirect URL in Novaplan AI exactly matches the Callback URL in Atlassian
  • Check for trailing slashes, protocol differences (http vs https), or casing
  • Update both configurations to use the same URL
API token authentication fails:
  • Confirm the token was copied correctly — no leading/trailing whitespace
  • The token may have been revoked or expired; create a new one at id.atlassian.com/manage-profile/security/api-tokens
  • Verify the Email field matches the Atlassian account that created the token
  • Verify the Base URL matches your Confluence site (must include https://, no trailing slash, match *.atlassian.net)
Base URL format issues (API Token):
  • Must include the protocol: https://
  • Must not include a trailing slash — use https://acme.atlassian.net, not https://acme.atlassian.net/
  • Must match the actual Confluence Cloud site (usually *.atlassian.net)
  • Do not include paths like /wiki or /spaces/...
Authorization failed (OAuth):
  • Verify you’re signing in with an account that has Confluence access
  • Ensure your Confluence site is selected during authorization
  • Check that all required API scopes are configured
No data syncing:
  • Verify the connector status shows Active
  • Check that the authenticating user (OAuth) or token-owning user (API Token) has access to Confluence spaces
  • Ensure spaces are not restricted or archived
  • Review sync logs for specific error messages
Token expired or sync stopped:
  • OAuth tokens may expire per Atlassian’s policies; disable and re-enable the connector to re-authenticate
  • API tokens can be revoked from the Atlassian account page; generate a new one and update the Authenticate Instance tab
  • Check if the OAuth app is still active in Developer Console
Permission denied for specific content:
  • Verify the authenticating user has read access to the content
  • Check space permissions in Confluence
  • Review page restrictions that may limit access
If you modify OAuth application settings in Atlassian Developer Console (Client ID, Secret, Callback URL, or scopes), update the configuration in Novaplan AI and re-authorize. For API tokens, re-enter the token in the Authenticate Instance tab if you regenerate it.

​
Data Sync Behavior

​
Initial sync

  • Fetches all accessible content from connected Confluence spaces
  • Indexes pages, blog posts, attachments, and comments
  • Respects user permissions for content visibility
  • Duration depends on the size of your Confluence workspace

​
Incremental sync

  • Uses timestamp-based synchronization to detect changes
  • Only syncs new or modified content since last sync
  • Reads every attachment of a page or blog post. If a temporary error interrupts the attachment list, the connector keeps the attachments already read and retries that time window on the next sync. If the first list request fails permanently, it uses attachments included in the search results.
  • Efficiently handles additions, updates, and deletions
  • Reduces API calls and sync duration

​
Permission handling

  • Syncs content based on the authenticating user’s permissions
  • Each user sees only content they have access to in Confluence
  • Respects space permissions and page restrictions
  • Maintains Confluence’s access control model
  • Attachments, comments, and replies inherit a restricted page’s visibility. Changes to the page restriction also update their stored visibility.
  • A restriction for a group that has not yet synced remains restricted. Group members gain access after the group syncs and the page is read again.
  • Temporary failures reading space permissions, group membership, or page restrictions preserve the access already stored and are retried on a later sync. A failed restriction read does not open the page to its whole space.

​
FAQ

Both methods sync the same data through one configured Team connector instance. They do not require every Novaplan AI viewer to authorize the connector separately. Verified account mapping and source permissions determine what each viewer can find; agree on the authenticating account and method with Novaplan and your Atlassian administrator.
Example: Use Confluence Connector to search and retrieve documentation. Use Confluence Toolset to let agents create or update Confluence pages.
There are three common causes:
  1. Viewer identity or Confluence access does not match - A viewer’s Confluence email or space permissions may not map to their Novaplan AI account. The account authorizing the shared connector does not have to match every viewer.
    • Fix: Ask your administrator to check the affected viewer’s account email and Confluence access, then confirm the connector’s designated account can read the space.
  2. Records show in “All Records” but not in search - Documents display in the All Records section but don’t appear in search query results.
    • Fix: Verify sync filters in the connector settings and ensure indexing has completed. Check that the data matches your search query criteria.
  3. Data not yet indexed - The connector is still syncing or hasn’t completed the initial indexing process.
    • Fix: Go to Workspace Settings → Connectors, check the sync status, and wait for indexing to complete.
Yes. When creating a Confluence connector, the admin has the option to apply filters and select specific Confluence spaces for indexing. This allows you to limit the scope of indexed content to only the spaces that are relevant to your organization’s needs.
Yes. Under Configure Records, use the Space Keys filter to select the space and the Page IDs filter with In to select the pages. The documented page filter also includes their child pages. Keep Index Pages enabled if you want the selected pages to be searchable by content. Enable Manual Indexing controls when synchronized records are indexed; it is not required to select a page subset. The accessible connector source registers this page filter as page_ids (displayed there as Page Name), so confirm the exact label in your deployed workspace.

​
Ready to Get Started?

Connect your Confluence workspace to Novaplan AI using the approved account and filters above. Search results reflect the content that was synced and each viewer’s Confluence permissions.