Skip to main content

Notion access and destinations

Who this is for​

This guide is for a person or administrator considering a Notion destination. Organisational worker access is not an individual Notion identity or personal Abe consent. The full caller, destination and delivery journey is not yet verified; this guide supplies no personal setup menu or sign-in flow.

Start here​

Before a supported setup can proceed, the responsible administrator must establish the exact workspace and destination, current authority to use it, and the services allowed there. A person must separately approve any requested personal app access and choose whether to receive updates.

Do not assume that a server worker's access enables every staff member to read or write a Notion page. No individual destination should appear in Abe's choices until its identity and authority are verified. No key or workspace secret belongs in a user chat. Server setup belongs in the Developer and API guides.

While that acceptance is pending, use Evidence search or the direct professional-development finder where supported. Save no patient notes or consultation content through this professional-information path.

What success looks like​

A future accepted flow must show the exact intended destination and an independently confirmed result. Accepted, unknown and failed outcomes are different. A worker's successful request does not establish a human account connection, personal permission or receipt in the correct destination. A read licence does not authorise extended actions.

If it does not work​

Stop if the workspace or recipient is uncertain. Check the existing status with the responsible administrator before resending. An unknown result must stay unresolved until reconciled; do not create duplicate content to test whether the first attempt worked. For a missing offered destination, use the direct service rather than an unrelated page. See Troubleshooting.

Stop or change your choices​

Pause your personal alerts separately from a worker's workspace access. Disconnect any actual Abe app grant through Manage and cancel; the workspace owner must separately manage organisational worker access. A pending outcome is not confirmed revocation. Paid cancellation remains its own choice and does not transfer ownership of personal preferences.