​
Overview

The Sentry integration monitors your organization’s error tracking and application monitoring setup: projects, teams, members, alert rules, releases, API tokens, and audit logs. LowerPlane uses read-only access via the Sentry API to collect compliance evidence automatically.

​
Prerequisites

You need Organization Owner or Manager permissions in Sentry to create a Personal Token with the required read permissions.

​
How to Get Your API Token

1

Log in to Sentry

Log in to sentry.io and navigate to your organization.
2

Open Personal Tokens

Go to Settings > Developer Settings > Personal Tokens (or visit https://sentry.io/settings/account/api/auth-tokens/).
3

Create a new token

Click Create New Token and give it a Name (e.g. “LowerPlane”). Under Permissions, set each of these to Read using the access dropdown:
  • Organization → Read — org details, integrations, audit logs, auth settings
  • Member → Read — members, roles, and MFA (2FA) status
  • Project → Read — projects and their security settings
  • Team → Read — teams and memberships
  • Issue & Event → Read (optional) — error/issue statistics
Organization and Member are required; Project and Team are recommended. Leave everything else at No Access — LowerPlane is read-only. Note that the Release permission has no Read level (only No Access or Admin), so leave it at No Access.
4

Copy the token

Copy the generated token. This is your Token for LowerPlane.

​
Connecting in LowerPlane

  1. Go to Settings > Integrations in LowerPlane
  2. Find Sentry under Analytics
  3. Enter your Token (the Personal Token you created)
  4. Enter your Organization Slug — the URL-friendly name of your Sentry organization (e.g., my-company). You can find it in your Sentry URL: https://sentry.io/organizations/{organization-slug}/
  5. Base URL — leave as https://sentry.io for standard (US) Sentry. Use https://de.sentry.io for EU-region accounts, or your instance URL for self-hosted Sentry.
  6. Click Connect
To find your organization slug, go to Settings > General Settings in Sentry. The slug is shown under “Organization Slug” and is also the part of the URL after /organizations/.

​
What LowerPlane Collects

Organization Settings

Organization name, slug, 2FA enforcement status, and security configuration.

Members & Teams

All organization members with roles (owner, manager, admin, member), MFA enrollment, and team assignments.

Projects

All Sentry projects with platform, status, and security settings (e.g., data scrubbing, IP restrictions).

Alert Rules

Alert configurations including conditions, actions, and notification targets.

Issues & Releases

Unresolved issue counts, release history, and deployment tracking.

API Tokens & Integrations

Active API tokens and third-party integrations connected to your Sentry organization.

Audit Logs

Organization audit log entries tracking security-relevant changes (requires Business or Enterprise plan).

​
Compliance Mapping

FrameworkControlsWhat It Proves
SOC 2CC7.2, CC7.3System monitoring and incident detection are in place
ISO 27001A.8.15, A.8.16Application logging and monitoring are configured

​
FAQ

All Sentry plans (Developer, Team, Business, Enterprise) are supported. However, audit logs are only available on Business and Enterprise plans.
No. LowerPlane uses read-only API scopes. It never creates, modifies, or deletes any Sentry data.
Sentry data syncs every 24 hours by default. You can trigger a manual sync from the integration settings.
Yes. Set the Base URL when connecting: use https://de.sentry.io for EU-region cloud accounts, or your own instance URL (e.g. https://sentry.acme.com) for self-hosted Sentry. It defaults to https://sentry.io for standard US cloud.