01
Create a read-only credential
Create the credential in Intercom 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 on Intercom verify the workspace identity, produce a teammate access review, and confirm the audit trail is on for the tool that talks to your customers.
4 read-only checks, run on a schedule. Each failure becomes a finding linked to a control — every check is listed, none are “coming soon”.
Connectivity check: confirms the access token authenticates and resolves the current admin via /me (HTTP 200). A non-200 (e.g. 401) indicates an invalid token.
account-connectivity
Fails if the token does not resolve to an admin identity with a verified email (`type` is not admin, or `email_verified` is not true).
verified-admin
Access-review check: fails if the number of workspace teammates exceeds the approved maximum (seat / offboarding review). Also fails if no teammates are returned, to avoid a vacuous pass. The /admins endpoint returns the full roster in a single response.
teammate-access-review
Audit-trail control: fails if no admin activity-log entries are returned for the review window, which would mean the audit trail is not queryable. Supply a Unix timestamp for the start of the window.
audit-log-availability
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 Intercom 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 Intercom 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.