Manage teams in Grafana IRM
Teams in Grafana IRM organize resources and control visibility across your incident response setup. IRM teams are automatically synced from Grafana teams created at the organization level.
How IRM uses Grafana teams
IRM syncs teams from your Grafana organization automatically. Changes you make to teams in Grafana, such as adding or removing members, are reflected in IRM after the next sync cycle.
To create or modify teams, go to Administration > Teams in your Grafana instance. IRM-specific team settings are managed separately in IRM > Settings > Team Access Management.
Note
To view and manage a team in IRM, users (including administrators) must be members of that team. If an administrator needs to manage a team they aren’t part of, they must first add themselves to the team in Grafana, make the necessary changes, and can then remove themselves.
Configure team settings
The IRM team settings page (IRM > Settings > Team Access Management) displays a list of teams and lets you configure:
- Team visibility: Control whether all Grafana users or only team members and administrators can see the team and its resources.
- Default team: A user-specific setting that pre-selects a team when creating new resources.
Team visibility
Team visibility determines who can see a team and access its resources:
- Administrators (users with the Admin basic role or IRM Admin RBAC role) can view all teams and their resources, regardless of membership.
- Editors and Viewers can only see teams they are members of, unless the team’s visibility is set to All users of Grafana.
To change a team’s visibility, go to IRM > Settings > Team Access Management and update the Who can see the team name and access the team resources setting for the team.
Warning
Grafana supports team-specific user permissions (Admin, Editor, or Viewer within a team), but IRM doesn’t use these team-level roles. IRM uses organization-level basic roles and IRM RBAC roles instead. For more detail, refer to Roles and permissions.
Organize resources with teams
Teams help you filter and organize resources throughout IRM:
- Assign a resource to a team when you create it.
- Alert groups created through an integration inherit the team from that integration.
- Use team filters on resource pages (integrations, schedules, escalation chains) to focus on your team’s resources.
Cross-team resources
You can create integrations in one team and use resources from other teams in the same escalation workflow:
- Set up multiple routes for an integration that use escalation chains from different teams.
- Include users, schedules, and outgoing webhooks from other teams in your escalation chains.
If a user has access to one team but not another, resources from the other team appear as 🔒 Private resource.
This allows you to distribute escalations across teams while maintaining visibility boundaries.
Require team membership for updates
To restrict who can edit team resources, enable the Require team membership for updates setting in Admin settings.
When enabled, only team members can modify resources owned by that team (subject to resource write permissions). Other users can still view the resources based on team visibility settings.
For a full list of affected resources and bypass rules, refer to Require team membership for updates.
