Slack, Google Drive and Notion, Answered Together
Most real answers are split between a Slack thread, a Drive doc and a Notion page. scri8e reads all three and answers once, with every source shown. It only reads.
Connected Sources
Slack
- Connected by
- An admin, once
- Reads
- Channels you choose, or every channel it can join
- Who sees it
- Private channels: their members only
Google Drive
- Connected by
- Each teammate, their own Drive
- Reads
- Folders you choose, nothing until you do
- Who sees it
- Per file, from Google’s sharing
Notion
- Connected by
- An admin, once
- Reads
- Pages and databases you choose, nothing until you do
- Who sees it
- The whole workspace
Pick a Tool to See the Detail
What each tool contributes, how its permissions carry over, and the limits that are real today.
- Slack IntegrationMessages and threads from the channels you choose. Private channels stay with their members.
- Google Drive IntegrationDocs, Sheets, Slides, PDFs and Office files, each keeping its Google sharing.
- Notion IntegrationPages and databases you choose, visible to your whole workspace.
A document can also be uploaded by hand, visible to the whole workspace or only to the people you name. If your team’s knowledge lives somewhere else, tell us where.
What All Three Have in Common
Three tools, three permission models, and the same four rules underneath all of them.
It only reads
scri8e can open, index and quote. It never posts, edits or sends anything in Slack, Drive or Notion.
You choose what it reads
Each tool has a picker. Remove a Drive folder or a Notion page later, and what was indexed from it is deleted.
Kept current without anyone’s help
Every source is re-read daily, and only what changed is re-indexed.
Real dates, not sync dates
Each document keeps the date it was last edited in its own tool, which is what the freshness verdict is judged on.