What connects

The connection uses a public Notion OAuth integration. The integration requests the ability to see pages and databases shared with it and read the content of the sources selected by the user.

An IntellaOne administrator configures the server-side Notion public-integration client credentials and callback URL, including the read-content capability.
The customer Notion workspace administrator or connected user approves the integration's access, then pages or databases must be shared with it; unshared content is not visible to the picker.
After OAuth, the user chooses which visible pages and databases become answer sources.

Information used

Selected page content is converted into citable knowledge. A selected database contributes its row-pages, while a selected page can include bounded block text and child pages.

Page titles, supported page properties, database row properties, and supported block text.
Selected child pages discovered beneath a selected page are included as separate knowledge documents.
Only selected sources are synced; an unshared, deleted, or deselected source stops surfacing after reconciliation completes.

Why it is useful

Teams can keep approved playbooks, product notes, and enablement material in Notion while giving IntellaOne a source-scoped, citable retrieval set instead of an unrestricted workspace mirror.

How the workflow behaves

Selected content syncs on a scheduled 30-minute cadence, not as a real-time mirror. Changed pages are re-read using their edit timestamps and become available as knowledge sources after the sync completes.

A completed reconciliation removes pages that are no longer shared, selected, or present.
Transient API failures do not delete existing sources.
Large database listings and page trees resume with cursors; reconciliation is suppressed during the resume cycle so an incomplete listing cannot remove valid content.
Notion is read-only in this integration: no page or database writes are performed.

Prerequisites and limits

Before connecting, an IntellaOne administrator must configure the server-side public Notion integration, OAuth callback, client credentials, and read-content capability. The customer Notion workspace administrator or connected user must authorize the integration and share the pages or databases that should be available for selection. Notion API rate limits, source size, and the bounded traversal limits can delay a complete sync.

Availability still depends on the provider account, plan, permissions, and application setup; a catalog status is not a guarantee that every account can use every provider feature.

Security and privacy boundaries

Newly saved connector credentials are encrypted before storage.

Connected tools sync server-side under the user's own credentials. Requested permissions and data flows are connector-specific.

Availability still depends on the provider account, plan, permissions, and application setup; a catalog status is not a guarantee that every account can use every provider feature.

Source selection is the privacy boundary: content is not synced merely because it exists elsewhere in the Notion workspace. IntellaOne requests read access and performs no outbound Notion writes.

Unsharing or deleting content is reconciled without silently treating a transient provider failure as deletion.
Citations identify the selected knowledge source rather than granting access to unselected workspace content.