Notion · reference material
Keeps page references and update times; the content stays in Notion and is never copied.
INTEGRATIONS / ADMIN GUIDE
Choose an integration, settle the direction of data, then connect with the least access
For workspace admins setting up connections. Check the exact scopes each integration asks for when you connect it.
Pick the connection that matches your workflow
Slack · event notifications
Sends the events you choose to a channel, with a link back to the decision record.
Linear · follow-up work
Creates issues from confirmed decisions; one-way by default, status is not written back.
Google Drive · source files
References file names, owners and links; files are never uploaded, moved or overwritten.
Every integration follows the same setup path
- 1
1 · Name the source of truth
Say which system may edit; the others only reference it or receive notifications.
- 2
2 · Narrow the access
Select only the pages, channels, teams or folders you need, authorized by an admin.
- 3
3 · Map and verify
Use one test record to check the title, link, owner, de-duplication and who can see the result.
- 4
4 · Record an owner
Save the connection owner, a review date and how to disconnect, so nothing depends on one person’s account.
Limits and troubleshooting
Is two-way sync supported?
Integrations reference, notify or create tasks in one direction. Two-way sync would need conflict handling, idempotency and rollback to be verified first.
Does disconnecting delete external data?
No. Documents, messages, tasks and files in the other system stay where they are.
Why can’t some members open a link?
References never bypass the source system’s permissions; check sharing in the source.
What happens when a member leaves?
Move the authorization to a workspace admin and check owners and member mappings again.
Decide before you configure
First decide which system is the source of truth
If the same field can be edited on both sides, don’t connect yet. Record who owns the data and any exceptions, then authorize.