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

​
What it’s used for

Keldyn uses Notion as a source of organisational pages: wikis, project notes, and database rows your team already treats as working documents. After the first sync, those pages appear under Notion in the Knowledgebase index browser. Unlike Drive and Confluence, Notion’s own sharing is the access boundary. The integration can only see pages you explicitly share with it during consent (and any you share later in Notion). Indexing everything visible is therefore the safe default — “visible” already means you chose those pages.

​
Before you begin

1

Decide which pages to share

During Notion’s consent screen you pick pages (and optionally their children) to share with the Keldyn integration. Pages you do not share are never readable, even after you connect.
2

Use a workspace you are allowed to connect

You connect as a Notion user. Keldyn receives a workspace-scoped token for the pages granted on that consent screen.
3

Keldyn only ever reads

The Keldyn Notion integration is read-only. It never creates, edits, or archives pages.

​
Set up the integration

1

Open Integrations

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

Connect

Select Connect. Notion opens a consent screen. Choose the pages (or top-level pages whose children should be included) that Keldyn may read, then approve access.
3

Optionally narrow the tree

If you shared a large set of pages, you can further limit indexing to specific root pages in the integration settings. Leave this empty to index everything already shared with the integration.
4

Run the first sync

After Notion returns you to Keldyn, wait for the first backfill or select Sync now. Open Knowledgebase and search for a phrase that appears only on a shared page to confirm it landed.
Pages appear in the index browser under Notion/{workspace}/{parent pages}/…. Nested pages are their own documents. Headings become separately retrievable sections. A child page is linked, not inlined, so the same text is not indexed twice.

​
What Keldyn indexes

Toggle content is indexed rather than hidden. Checkbox state is preserved. Database rows can carry Type, Product, and Team (or similar) properties; Keldyn uses those so a Notion row filters like a Library document.

​
What data Keldyn collects and why

Keldyn never writes to your Notion workspace. It collects only the data needed to search and cite the pages you shared. Notion access tokens do not expire. There is no refresh token. If Keldyn starts reporting an auth error, the integration was removed from the Notion workspace — reconnect rather than waiting for a token to renew.

​
Permissions

Notion does not use scope strings. Access is granted page by page on the consent screen (and later via Share → the Keldyn integration in Notion). That grant is the boundary.

​
Who can read indexed pages

Anyone on the team who can open Knowledgebase can read every indexed Notion page, including pages that were private to a small group in Notion. Notion sharing does not carry over into Keldyn. See Knowledgebase privacy. If a page should not be searchable, unshare it from the Keldyn integration in Notion, or use Remove from index in the Knowledgebase browser. Unsharing one page is treated as an access gap for that page; removing the integration entirely fails the sync without wiping the rest of the index until you disconnect in Keldyn.

​
Keeping the index current

Keldyn checks shared pages about every ten minutes and re-reads pages edited since the last successful sync. You can also trigger an immediate pull with Sync now.
  • Editing a page in Notion updates its passages on the next sync.
  • Archiving or trashing a page unpublishes it. It stops appearing in search; an existing citation still resolves. Notion keeps archived pages readable through its API — that is why Keldyn must stop citing them as current.
  • Reconnecting forces a full re-read of every shared page.
Disconnecting Notion unpublishes only the Notion documents. Nothing is deleted in Notion. Reconnecting and syncing restores them.

​
Troubleshooting

A search that should have hit a Notion page usually means one of the following:
  • Page was not shared with the Keldyn integration during consent (or later in Notion).
  • Page was archived — archived pages are unpublished on the next sync.
  • Root-page filter is too narrow — a settings allowlist can hide pages that are otherwise shared.
  • Reauth required — the integration was removed from the workspace. Select Reconnect and share the pages again.
You can add or remove pages later from Notion: open the page → Share → the Keldyn integration.

​
Next steps

Knowledgebase

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

Otter.ai

Index meeting transcripts from chosen Otter channels.