How DSALTA integrates with Notion — data collected, setup guide, and automated compliance checks.
Overview
How to connect
Automated checks
Useful links
DSALTA connects to Notion using read-only API access to collect compliance evidence automatically. DSALTA syncs your Notion workspace members and runs access reviews against your People directory. Data feeds into your Data Library modules.
Read-only access. DSALTA never modifies, creates, or deletes resources in your Notion workspace. The connection only reads workspace member information.
DSALTA collects this integration’s data when you connect it — you can refresh it at any time with Sync from integrations on the Integrations page. The compliance checks below re-run once a day at 02:00 America/New_York.
DSALTA reads the Notion user roster — names and email addresses, which appears on your Access page. Notion’s users API exposes no role or account status, so every member is listed as an active Member.It calls these Notion endpoints:
/v1/users/me
/v1/users
Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Notion environment.
There is no Reconnect button. Open Integrations → Connected, click Manage on the Notion card, and check the Status tab — it shows either Connected and working properly or Connection issues detected. To restore a broken connection you must Disconnect and connect again, which permanently deletes the data and tests collected from Notion. This can happen if the connection was deleted or its access token was regenerated in Notion.
Data is not syncing
Confirm the connection still has the Read user information capability enabled — a Personal Access Token or a connection missing this capability cannot read members. Verify the token is current, then click Sync from integrations on the Integrations page (Connected tab) — it refreshes every connected integration at once.
Notion Connection access token (Access token auth) with the ‘Read user information’ capability. Read-only.Before you begin
A Notion account (standard plan works)
A Notion Connection with ‘Access token’ auth and the ‘Read user information’ capability (a Personal Access Token will NOT work)
Open Integrations in the DSALTA sidebar, find Notion, and click Connect to open the connect panel. Leave it open — it lists every value you need, and you create those in the steps below.
2
Create a Notion Connection (Access token)
Open notion.so/my-integrations (or Notion → Settings → Connections → Develop). Click New connection, set Authentication method to ‘Access token’ (a workspace-scoped token), select your workspace, and click Create connection. Do NOT use a Personal Access Token — it lacks the user-read scope. A standard Notion plan works; no paid or enterprise plan is required.
Pick Access token, not OAuth, and note what Notion says about it on that dialog: it is a “Workspace-scoped static API token, shared across collaborators”, “Limited to 1 workspace”. One connection therefore covers one Notion workspace — if you run several workspaces, create one connection per workspace. Deleting the connection later “permanently revokes its access token and removes it from this workspace”, which is what shows up in DSALTA as Disconnected.
3
Enable 'Read user information' and copy the token
Open the new connection’s Capabilities and under User capabilities, select Read user information including email addresses — this exact option is required, because DSALTA matches Notion users to your People page by email. Then copy the connection’s Internal Integration Secret / access token (it starts with ‘ntn_’ or ‘secret_’).Untick the Content capabilities while you are on this screen. A new connection arrives with Read content, Update content and Insert content enabled — DSALTA never touches page or database content, it calls only /v1/users/me and /v1/users — so clear all three and leave Read user information including email addresses as the connection’s only capability. The Connections list then describes it as user-information only, which is the state you want to hand an auditor.
4
Connect Notion
Paste the Connection access token, then click Connect.What the Access page will show: workspace members only. Notion’s list-users endpoint states “Guests are not included in the response”, and DSALTA additionally drops bot users, so integrations and guests never appear. Notion exposes no workspace role and no suspended flag on this endpoint, so every row lands as role Member, status Active, and MFA Unknown — treat the page as a membership list, not a permissions report.
DSALTA validates the credential when you click Connect. On success the integration moves to the Connected tab, and Manage → Status reads Connected and working properly. Checks begin reporting after the first sync.
If the connection is rejected. Invalid token, or the connection lacks the ‘Read user information’ capability.The on-screen message is generic — see Connection error messages.
Each check below re-runs once a day, at 02:00 America/New_York, while this integration is connected. Click any check for step-by-step remediation guidance.
.png?fit=max&auto=format&n=tsMQJyneJ1xquFUo&q=85&s=4d401cc03b547d99b6f75a6bd170c334)
