Confluence support

Last updated date:

Connect, reconnect, and troubleshoot Confluence without sharing credentials or customer content through support channels.

1. Before you start

  • Choose the Confluence Cloud site and spaces that should contribute to Seedling.
  • Create an API token for a dedicated account or service account and grant it Can use plus view access only to approved spaces and restricted pages.
  • For a scoped token, select the read scopes above. Seedling looks up the site's cloud ID and calls Confluence through api.atlassian.com.
  • Do not send Confluence credentials, customer content, personal information, or private record data by email or through an ordinary support ticket.
Confluence basic authenticationAtlassian's Confluence Cloud API-token authentication guidance.

2. Connect Confluence

  1. In Seedling, open Connections and choose Confluence.
  2. Choose personal or workspace scope deliberately; Seedling never promotes an actor-owned connection into workspace access.
  3. Enter the exact Confluence Cloud site URL, account email, and API token.
  4. Seedling verifies the site and account, then stages space permissions and content restrictions for conservative access diagnostics.
  5. Allow the first Confluence synchronization to finish, then verify the expected resource population and member access policy.

3. Authorization and connection problems

Confluence API token rejected
Confirm the confluence api token is active, was entered without surrounding whitespace, and belongs to the intended Confluence account and environment.
Missing permission or resource
Restore the exact read permission or provider-side resource access described in this guide. Seedling does not substitute a broader credential or silently treat a forbidden Confluence population as empty.
Wrong account or scope
Disconnect before retrying with the intended Confluence identity, account, and Seedling connection scope. Seedling does not infer account ownership from a display name or email address.

4. Missing or delayed data

  1. Confirm the token account can open the affected space, page, blog post, comment, or attachment in Confluence.
  2. Check inherited space permissions, page restrictions, archived content, and site URL/account-email mismatch.
  3. For personal content confirm connection ownership; for workspace content check the connection-wide restricted policy.
  4. Allow incremental synchronization and provider retry handling to complete. A temporary provider failure does not delete previously synchronized data.
  5. If the issue remains, contact support@tryseedling.ai with the Seedling workspace, safe timestamps, and non-sensitive provider record identifiers. Do not include credentials or record contents.

5. Rotate or replace access

Never use email or an ordinary support ticket to transfer the old or replacement credential.

  1. Create replacement confluence api token for the same Confluence account with the same or narrower released permissions.
  2. Replace the credential on the exact Seedling connection and repeat identity, scope, and capability verification.
  3. After Seedling confirms the replacement, revoke the old confluence api token in Confluence.