Skip to main content
Sentry organizes everything you monitor into a three-level hierarchy: organizations contain teams, and teams own projects. Understanding this structure helps you manage access, route alerts to the right people, and keep your data organized.

​
The hierarchy

Organization
└── Team A
│   ├── Project: frontend
│   └── Project: mobile-ios
└── Team B
    └── Project: backend-api

Organization

The top-level container for your Sentry account. It holds all members, billing settings, integrations, and global configuration. Everything in Sentry belongs to an organization.

Teams

Groups of members that own one or more projects. Teams let you control who gets notified, who can configure alerts, and who is responsible for a given service.

Projects

Represents a single application, service, or component you want to monitor. Each project has its own DSN (SDK key), issue stream, alert rules, and settings.

​
Organizations

Your organization is the top-level account in Sentry. It has:
  • Members — everyone with access to your organization
  • Billing and plan — subscription and usage limits apply at the organization level
  • Integrations — connections to Slack, GitHub, PagerDuty, and other tools
  • Global settings — data retention, security policies, and feature configuration
You can switch between organizations using the organization selector in the top-left of the Sentry UI.

​
Teams

Teams group members together and link them to projects. A team can own multiple projects, and a project can belong to multiple teams. Teams are used to:
  • Route issue alerts to the right group of people
  • Assign ownership rules so the correct team is notified when an issue occurs in their code
  • Control project access — members only see projects owned by their teams (unless open membership is enabled)
To create a team, go to Settings → Teams → Create Team.

​
Projects

A project corresponds to one application or service you’re monitoring. When you install the Sentry SDK, you configure it with a DSN that identifies which project receives the events. Each project has its own:
  • Issue stream and search filters
  • Alert rules
  • SDK configuration and DSN
  • Performance settings and thresholds
  • Source map and debug file uploads
To create a project, go to Projects → Create Project and select the platform your application uses.

​
Member roles

Roles control what members can do within your organization.
RoleDescription
OwnerUnrestricted access to the organization, its data, and settings. Can manage billing, add or remove members, and modify all projects.
ManagerAdmin access across all teams. Can add and remove members, create and delete projects and teams.
Admin (retired)Admin access on teams they’re a member of. Can create teams and projects, manage memberships within their teams.
MemberCan view and act on events and most organization data. Can invite new members by default.
The Admin role has been retired in favor of the Manager role. Existing admins retain their access, but new members should be assigned Member or Manager.

​
Team roles

Within a team, members have one of two roles:
RoleDescription
Team AdminFull admin access within the team, including managing team membership and project settings.
ContributorCan view and act on events in the team’s projects.
  • Switch organizations: Click the organization name in the top-left navigation bar.
  • Switch projects: Use the project selector at the top of most pages, or navigate to Projects in the sidebar.
  • View all projects: Go to Projects in the left sidebar to see every project in your organization with a summary of recent activity.
If you manage multiple services, consider creating a project per service rather than per environment. Use environments to separate production, staging, and development data within the same project.