Incident IntelligenceSignals become incidentsBacktraceGrouping you can readLive logsStream · list · aggregateUptime monitoringHTTP · TCP · ping, 10sPerformance (APM)Per-transaction timingSession ReplayTyped event timelinesAgent Access (MCP)Production context for AIIntegrationsGitHub · Slack · Jira · …
Integrations→Pricing→Docs→Changelog→
Start free trial →
Organization

Members and teams

Invite teammates, understand visible roles, and use teams to grant project access across your organization.

Organization access controls who can see projects, triage errors, configure integrations, and connect repair agents. Use members for people and teams for project access boundaries.

How access works

Errorgap shows organization members with their role and team memberships. Teams group projects together, then members inherit access through the teams they belong to.

  • Members are users who can sign in to the organization.
  • Roles describe the highest visible privilege for a member.
  • Teams connect groups of people to the projects they need.
  • Project access should follow ownership and on-call boundaries.

Review members

  1. Open the organization area.
  2. Select Members.
  3. Search by name or email when the list is long.
  4. Filter by role or team to audit a specific access group.
  5. Open a member to review or edit their team memberships.

Invite and remove members

Invite people from the Members page when they need access to Errorgap. After a person joins, add them to the team that owns the projects they need. Remove members who no longer need access from the member actions menu.

  • Invite with the email address the teammate uses for work.
  • Add new members to at least one team if they need project access.
  • Remove former teammates promptly so their access is not left active.
  • Review organization admins separately because they can change broader settings.

Create teams

Create teams around ownership. A team can represent a product area, service group, on-call rotation, or any other durable access boundary.

  1. Open Organization, then Teams.
  2. Select New team.
  3. Enter a stable, recognizable team name.
  4. Create the team, then assign projects before adding many members.

Assign projects

A team should include the projects that its members are expected to monitor or repair. Select projects from the team card and save the changes.

  • Grant access to projects the team owns or supports.
  • Avoid broad access when a narrower team would be clearer.
  • Rename teams when ownership changes, but keep names recognizable to responders.
  • Delete teams only after confirming no one relies on that access path.

Keep access clean

Treat access reviews as part of operational hygiene. Review members and teams after reorganizations, offboarding, and major project ownership changes.