Skip to content

Notion

Evidence & policy documents. Read-only snapshots of the Notion pages and databases you choose to share, shown as evidence with how fresh each one is.

Status: available now - you connect this yourself

This source is live in the console. Create the read-only integration below, connect it on its card in Integrate -> Sources, and your dedicated instance starts collecting. It is an evidence source: connecting it does not create any alerts.

What SheerSight reads

SheerSight reads only the pages and databases you share with a Notion integration you create. Typical examples are your policies, a risk register, a vendor list, and access review records.

For each shared page, and for each row of a shared database, SheerSight takes a snapshot that records:

  • the page or row title and its Notion link,
  • when it was last edited in Notion, and the id of the editor (not their name),
  • a content hash and the content length, which let SheerSight tell whether the content changed since the last snapshot.

SheerSight does not keep the text of your pages. Only the hash and length are stored.

Each record carries a freshness measure: how many days since the page was last edited, and whether the content changed since the last snapshot. An item that has not been edited for more than 12 months is marked stale. The threshold is fixed at 12 months.

The page and database data is collected on your dedicated instance. The console card shows whether the source is live and any connection problem. A page-by-page evidence view in the console is not part of this release.

It is read-only. SheerSight never writes to Notion, ever.

What it does not read

  • Pages you have not shared. If a page is not shared with the integration, SheerSight cannot see it and never reads it. A page the integration cannot read is skipped and tried again later, without failing the source.
  • The text of your pages. Only a hash and the length are kept.
  • Anything in your workspace you did not choose. Sharing is page by page (or database by database), and you stay in control of the list.
  • Anything that changes your workspace. The integration only needs read access.

What you'll need

  • A Notion workspace where you can create an internal integration. In most workspaces this needs a workspace owner or admin.
  • A list of the pages and databases you want to share as evidence.
  • Your dedicated instance enrolled.

Create the read-only credential

  1. In Notion, open Settings -> Connections and choose Develop or manage integrations.
  2. Create a new internal integration and name it SheerSight evidence. Choose your workspace.
  3. Under Capabilities, turn on Read content only. Leave Update content and Insert content off. Leave user information off.
  4. Save, then copy the internal integration secret. It starts with ntn_ or secret_. Paste it straight into the SheerSight console (next section).
  5. Share only the pages or databases you want SheerSight to read. On each one, open the ... menu, choose Connections, and add SheerSight evidence. Sharing a page also shares the pages inside it. Very large trees are read in part: there are limits on how many pages, rows and levels of nesting are read in one round, so share the smallest set that makes sense.

Least privilege

The integration can only see what you share with it, and it only has read access. Start with one page or database, check that it appears, then share more.

Connect it in SheerSight

In the console, open Integrate -> Sources -> Notion and fill in:

Field Value
Notion integration token (Read content only) The whole secret you copied in step 4, with no spaces.

There is nothing else to fill in. What the integration can see is decided by the pages you share with it. Press Connect. The token is encrypted in your browser before it leaves your screen, so SheerSight staff never see it in clear. Paste it only into the encrypted field, never into chat or a support ticket.

Verify

  1. The relayed credentials entry moves from pending to applied.
  2. The Notion source badge moves from not connected to live.
  3. The card shows no connection error. Collection then runs on your instance.

Never copy the token into a terminal or a ticket to test it.

Large workspaces take a while

Notion limits how fast an integration can read, so a large tree of shared pages may take a while to capture the first time.

What you see in the console

  • Source status. The Notion card shows whether the source is live, and when a connection problem needs attention it shows the cause and the fix.

Disconnect and revoke

You can stop SheerSight reading Notion at any of these levels. Each one works on its own.

  • Unshare a page. In Notion, open the page's Connections menu and remove SheerSight evidence. SheerSight can no longer read it.
  • Remove the integration. In Notion, open Settings -> Connections -> Develop or manage integrations and delete the integration. The token stops working at once.
  • Disconnect the card. In the console, disconnect the Notion card on Integrate -> Sources. The credential is removed from your instance and collection stops.

For the most complete revocation, do all three. See Connecting sources for what the console shows while a disconnect applies.

Data handling and retention

SheerSight stores page metadata only: the title, link, last-edited time and editor id, the content hash and its length. It does not store the text of your pages. For how long that data is kept, where it runs, and what happens when you offboard, see Data handling & retention. The token itself is encrypted in your browser and decrypted only on your dedicated instance. See Security & trust.

Troubleshooting

  • Badge stays not connected, or the card shows an invalid token message. Copy the whole secret from Notion again (it starts with ntn_ or secret_) and use Update credentials to send it. Check that the integration still exists in Notion.
  • The token is valid but the card reports a restriction. The integration needs the Read content capability. Turn it on in Notion, share the pages, and use Update credentials if you made a new token.
  • The card says the workspace is large. One polling round ran out of its request allowance. The rest is read in later rounds. To read fewer pages, share fewer pages.
  • Connected but no evidence appears. The integration only sees what you share. Open a page's Connections menu in Notion and confirm SheerSight evidence is listed.
  • A page is missing. It was unshared or moved somewhere the integration cannot reach, so it is skipped. Share it again if you want it back.
  • The card says the stored token is not in the right shape. Copy the whole secret again and use Update credentials.
  • The card says the instance could not reach Notion. No action needed, polling retries on its own. If it lasts, check that the instance can reach api.notion.com.
  • First snapshot is slow. Large trees can take a while because of Notion's read limits. Leave it running.
  • Everything is flagged stale. Notion records the last edit, so a page that is read but never edited still ages. Editing a page, even a small change, resets it.
  • Something else. See the FAQ, or email security@sheersafe.com for anything security-related.

What SheerSight can and cannot do

The token is read-only and limited to the pages you share. SheerSight cannot edit, create, move, or delete anything in Notion, and cannot see pages you have not shared. It only reads.