Ask Questions About Your Notion Pages.
Your wiki, your runbooks and your team databases, read alongside Slack and Google Drive so one answer can draw on all three. One thing to know before you connect: everything shared with scri8e is visible to your whole workspace.
- Connected by
- An admin, once
- Reads
- Pages and databases you choose
- Permissions
- Workspace-wide
- Re-reads
- Daily
- Access
- Read-only
Who owns the on-call rota now?
Dana took it over from Sam at the start of the quarter. The Team Directory row and the runbook both name her, and the handover was announced in the engineering channel.
Pages, Databases and Every Row in Them
Notion makes you share each page with an integration before it can see it. scri8e then reads only what you pick from that list.
What it reads
- Pages and databases shared with the scri8e integration that you then select
- Each database row, with its properties and its page body
- Edits, picked up on the daily re-read using Notion’s own last-edited time
What to know first
- Everything you select is visible to everyone in your scri8e workspace, whatever its sharing inside Notion.
- Nothing is read until you pick pages or databases.
- A page Notion hasn’t shared with the integration is invisible to scri8e. Share it in Notion first.
Why Notion Is Workspace-Wide
Slack and Google Drive tell scri8e who can open each document. Notion’s API doesn’t tell any integration who a page is shared with, on any plan, so page-level sharing can’t be mirrored.
- What scri8e does
- Treats everything shared with it as readable by your whole workspace, and says so on the connect screen.
- What it won’t do
- Guess at page-level sharing, or promise a fix Notion’s API doesn’t allow.
- What we suggest
- Share only pages the whole team may read. Keep pay, hiring and other restricted pages out of the selection.
Read Next
Your Wiki, Plus Everything It Missed.
We’re setting teams up a few at a time, each one on a call. Book 20 minutes, or write to us first if you’d rather.