Skip to main content

​
After this article

You will be able to connect Sentry to Lumos via SCIM to sync Sentry organization members and deprovision users during offboarding, Access Reviews, and license management.

​
Capabilities

​
Required plan and roles

  • Sentry plan: at least the Sentry Business plan. Your organization must have SAML and SCIM enabled before connecting the integration.
  • Sentry role: the setup must be performed by at least an Org Admin.
  • Permission scoping: the integration authenticates with a Sentry SCIM token. Lumos uses it to list organization members (sync) and to delete organization members (deprovisioning). There is no separate read-only token variant. If you only want visibility, do not enable deprovisioning workflows against this integration in Lumos.

​
Read-only access vs provisioning

Is read-only possible? No. Sentry uses a single SCIM token for both syncing organization members and deleting them. There’s no separate read-only token variant, so any connection carries the ability to deprovision even if you never trigger it. What full provisioning requires. A Sentry Business plan with SAML and SCIM enabled, an Org Admin performing setup, and the organization’s SCIM token generated from Sentry’s SCIM documentation. Follow the steps below. Watch out for. Deprovisioning through this integration is a hard delete: the member and their data are permanently removed from Sentry, and the license is reclaimed. If you only want visibility and don’t intend to deprovision through Lumos, don’t enable deprovisioning workflows against this integration, since the underlying token can’t be restricted to read-only.

​
Instructions

Phase 1: Prepare Sentry
  1. Confirm SAML SSO and SCIM are enabled for your Sentry organization (Business plan requirement).
  2. In Sentry, go to Settings → General Settings and copy your organization slug.
  3. Generate and retrieve your SCIM token following Sentry’s SCIM documentation, and copy it.
Phase 2: Connect in Lumos
  1. Find the Sentry card in your Lumos integrations (reconnect an existing card or add a new one).
  2. Paste the organization slug into the Organization Slug field.
  3. Paste the SCIM token into the SCIM Token field.
  4. Click Connect Sentry.

​
Troubleshooting

Everyone’s name shows as “N/A”. Expected Sentry behavior. Sentry’s SCIM /Users endpoint returns name.givenName and name.familyName as the literal string N/A, so Lumos displays the name from your source of truth instead. This is not a sync failure. Connection fails. Confirm your organization is on the Business plan with SAML and SCIM enabled, the organization slug matches Settings → General Settings exactly, and the SCIM token is current (regenerating a token invalidates the old one). Deprovisioning concerns. Deprovisioning via this integration is a hard delete: the user and their data are permanently removed from Sentry. If you only need to remove access temporarily, handle it in Sentry directly rather than through a Lumos deprovisioning workflow.