01
Create a read-only credential
Create the credential in Notion with the minimum read scope, paste it into devguard, and the connection is live. The integration page in the product spells out the exact permissions.
Read-only checks confirm your Notion internal integration is valid, verify exactly what it can reach, and produce access-review evidence for the workspace your documentation lives in.
3 read-only checks, run on a schedule. Each failure becomes a finding linked to a control — every check is listed, none are “coming soon”.
Confirms the internal integration token resolves the bot user via GET /users/me (HTTP 200).
integration-connectivity
Governance check: confirms the internal integration is owned by the workspace (`bot.owner.type` == `workspace`) rather than a single user, so its access is administered at the workspace level.
integration-workspace-scoped
Access-review evidence: exhaustively enumerates the workspace user roster via GET /users, paginated with the `start_cursor` query parameter, and fails closed if no members are returned. Notion's public API exposes no per-user guest/admin/two-factor flags, so this is a roster-retrievability check for access reviews, not a control-enforcement one.
member-roster-retrievable
Bring your current platform's test list — we'll map it against these checks, gap by gap
Setup is minutes, not a migration project — and every step stays on your side
Create the credential in Notion with the minimum read scope, paste it into devguard, and the connection is live. The integration page in the product spells out the exact permissions.
The first run starts right after connecting, then repeats on a schedule. Results are timestamped, so your evidence has a history, not a snapshot.
Passing results attach as evidence to the controls they support; failures become findings you triage. When the audit comes, the proof is already connected.
Open any page for its full check register.
You create and scope every credential yourself, and you can revoke it at any time. Checks only read; results and evidence are stored in Switzerland and stay exportable.
Yes. The checks authenticate with a credential you create and scope yourself, and only ever read configuration. devguard holds no write access to Notion and remediates nothing silently.
A failed check becomes a finding linked to the control it supports, with the evidence attached. You decide the treatment — nothing pages your engineers and nothing is auto-remediated.
Checks run from Swiss infrastructure, and results and evidence are stored in Switzerland. Everything is exportable — your evidence stays yours.
20 minutes on how you run certification today. Bring your current test or control list and we'll map it against these checks — honestly, gap by gap.