Skip to main content
The Confluence integration indexes selected Confluence Cloud spaces into Knowledgebase. Once connected, Keldyn reads those spaces on a schedule and turns pages (and supported attachments) into searchable, cited passages — with a link back to the page in Confluence. This is a knowledge connector. It does not collect control evidence.
Knowledge integrations are managed by Keldyn admins. Connecting Confluence does not appear for other roles.

​
What it’s used for

Keldyn uses Confluence as a source of organisational wiki pages: policies, runbooks, design records, and the pages your team already treats as canonical. After the first sync, those pages appear under Confluence in the Knowledgebase index browser. Choose spaces that are already meant to be shared with compliance and security reviewers. The spaces — not the Atlassian account — are what limit what Keldyn reads.

​
Before you begin

1

Use Confluence Cloud

This integration connects Confluence Cloud through Atlassian OAuth. It does not connect Confluence Data Center or Server.
2

Use an account that can open the spaces

You connect with your own Atlassian account. Keldyn only ever reads spaces and pages that account can already view.
3

Pick the spaces to include

Decide which space keys to index (for example SEC or ENG). Without at least one space selected, Keldyn indexes nothing — it will not fall back to the whole site.
4

Keldyn only ever reads

The connection requests read-only Confluence scopes. Keldyn never creates, edits, or deletes pages.

​
Set up the integration

1

Open Integrations

In the Keldyn web app, go to Integrations, filter to Knowledge, and select Confluence.
2

Choose the spaces to index

Select one or more Confluence spaces. This is recorded before you grant access, so you state what you are exposing before Atlassian asks for consent.
3

Connect

Select Connect and complete the Atlassian consent screen. Review the requested read-only access and approve it. If the account can access more than one Confluence site, Keldyn uses the first site Atlassian returns for that grant.
4

Run the first sync

After Atlassian returns you to Keldyn, wait for the first backfill or select Sync now. Open Knowledgebase and search for a phrase that appears only in a selected space to confirm the pages landed.
Pages appear in the index browser under Confluence/{space}/{parent pages}/…. Child pages are their own documents. Headings on a page become separately retrievable sections, so a question about one heading does not have to retrieve the whole page.

​
What Keldyn indexes

An attachment is indexed as its own document, filed under its host page. A long attached policy is cited as itself, not as the one-line page it was attached to.

​
What data Keldyn collects and why

Keldyn requests read-only access and never writes to Confluence. It collects only the data needed to search and cite the spaces you selected.

​
Permissions and scopes

Keldyn requests these Atlassian scopes. All are read-only. The granted scopes cover the Confluence site. The spaces you select are what stop Keldyn reading the rest of the wiki.
Atlassian rotates refresh tokens. Keldyn stores the replacement as soon as it is issued. Restoring an old database backup over a live connection can invalidate the stored token — if that happens, reconnect.

​
Who can read indexed pages

Anyone on the team who can open Knowledgebase can read every indexed page from the selected spaces, including pages that were restricted to a few people in Confluence. Space and page restrictions do not carry over. See Knowledgebase privacy. If a page should not be searchable, keep its space off the allowlist, or use Remove from index in the Knowledgebase browser. Removing it from the index does not delete it from Confluence.

​
Keeping the index current

Keldyn checks the selected spaces about every five minutes and re-converts pages that changed since the last successful sync. You can also trigger an immediate pull with Sync now.
  • Editing a page in Confluence updates its passages on the next sync.
  • Deleting a page, or losing access to a selected space, unpublishes those documents. They stop appearing in search; an existing citation still resolves.
  • Reconnecting forces a full re-read of every selected space.
Disconnecting Confluence unpublishes only the Confluence documents. Drive, Notion, Otter, and Library documents are left alone. Nothing is deleted in Confluence.

​
Troubleshooting

A search that should have hit a Confluence page usually means one of the following:
  • No spaces selected — the connector is connected but indexes nothing until you choose at least one space.
  • Wrong site — the Atlassian account has several sites, and Keldyn bound the first one returned. Reconnect from the account that owns the site you want.
  • Page restricted from the connecting account — Keldyn cannot read a page that account cannot open.
  • Reauth required — the grant was revoked or the refresh token was lost. Select Reconnect and complete Atlassian consent again.

​
Next steps

Knowledgebase

Search cited passages and browse the index after the first sync.

Notion

Index Notion pages shared with Keldyn.