Skip to main content

​
Overview

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 syncs every 24 hours and 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.

​
How to Connect

Notion connects with an internal integration token — a Connection created in your Notion workspace with the Read user information capability. A standard Notion plan works; no paid or enterprise plan is required.
1

Create a Notion Connection (Access token)

Open notion.so/my-integrations (or Notion → Settings → Connections → Develop). Click New connection, set the 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, so member sync will fail.
2

Enable 'Read user information' and copy the token

Open the new connection’s Capabilities and enable Read user information (choose including email addresses if offered, so DSALTA can match users to your People page by email). Then copy the connection’s access token — it starts with ntn_ or secret_.
3

Connect

In the DSALTA sidebar, go to Integrations, find Notion, and click Connect. Paste the Connection access token in the secure window and submit.
4

Finish

DSALTA verifies the token, then runs an initial sync — usually a few minutes — after which the compliance checks below activate.

​
Automated Compliance Checks

Each check below runs automatically every 24 hours. Click any check for step-by-step remediation guidance.

​
Troubleshooting

Re-authenticate from Integrations → Notion → Reconnect. This can happen if the connection was deleted or its access token was regenerated in Notion.
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 trigger a manual sync from the integration settings.