sentry-enterprise-rbac
Configure enterprise role-based access control in Sentry.Use when setting up team permissions, SSO integration,or managing organizational access.Trigger with phrases like "sentry rbac", "sentry permissions","sentry team access", "sentry sso setup".
When & Why to Use This Skill
This Claude skill automates the configuration of Sentry Enterprise Role-Based Access Control (RBAC). It streamlines the complex process of setting up team permissions, SSO/SAML integrations, and SCIM provisioning, ensuring secure, scalable, and organized access management for enterprise-level monitoring environments.
Use Cases
- Enterprise Onboarding: Automating the creation of organizational teams and project assignments to ensure new departments have immediate, structured access to monitoring tools.
- Security Compliance: Implementing centralized identity management through SSO/SAML and SCIM to enforce automated user provisioning and deprovisioning.
- Access Governance: Configuring scoped API tokens and audit logging to maintain the principle of least privilege and meet strict security auditing requirements.
| name | sentry-enterprise-rbac |
|---|---|
| description | | |
| allowed-tools | Read, Write, Edit, Grep |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
Sentry Enterprise Rbac
Prerequisites
- Sentry Business or Enterprise plan
- Identity provider configured (for SSO)
- Team structure documented
- Permission requirements defined
Instructions
- Create teams via dashboard or API following naming conventions
- Add members to teams with appropriate roles (admin, contributor, member)
- Assign projects to teams based on service ownership
- Configure SSO/SAML with identity provider settings
- Set up SAML attribute mapping for email and optional team assignment
- Enable SCIM provisioning for automated user management
- Create organization API tokens with minimal required scopes
- Implement access patterns (team-isolated, cross-team visibility, contractor)
- Enable audit logging and review access regularly
- Follow token hygiene practices with quarterly rotation
Output
- Teams created with appropriate members
- Projects assigned to teams
- SSO/SAML configured
- API tokens with scoped permissions
Error Handling
See {baseDir}/references/errors.md for comprehensive error handling.
Examples
See {baseDir}/references/examples.md for detailed examples.