Admin settings for Grafana IRM
The Admin & API tab in Grafana IRM settings provides organization-wide configuration options that affect how users and teams interact with IRM.
To access these settings, go to Alerts & IRM > IRM > Settings > Admin & API.
Access IRM API endpoints
The Admin & API tab displays the base URLs for the IRM APIs. These values are specific to your Grafana Cloud stack and are configured automatically during plugin provisioning.
Use these endpoints for programmatic access or when setting up infrastructure as code.
For more detail about using the IRM APIs, refer to the API reference.
Notification channel visibility
Control which notification channels are available to users in their personal notification rules.
Use the toggles to show or hide specific notification channels, such as Slack or Microsoft Teams.
When an integration is installed, the toggle is enabled by default, allowing users to select the channel in their personal notification rules.
If a notification channel is disabled:
- The channel no longer appears in a user’s IRM profile.
- The associated configuration tab is hidden from the IRM profile UI.
Note
These toggles only control visibility for users. They don’t enable or disable the integration itself. To manage integrations, go to IRM > Integrations > Apps. For more detail, refer to IRM integrations.
Manage direct paging integrations
Control how direct paging integrations are created and managed in your organization.
By default, IRM automatically creates and manages a direct paging integration for each team. These integrations allow teams to be paged directly through the UI, messaging apps, or API.
When Manually manage direct paging integrations is enabled:
- IRM stops automatically creating direct paging integrations for new teams.
- Existing direct paging integrations remain unchanged and can be managed manually.
- You can create and delete direct paging integrations through the API or infrastructure as code tools like Terraform.
Note
Enabling this setting doesn’t delete existing direct paging integrations. You can import existing integrations into your IaC tooling or delete and recreate them manually.
This setting is useful for teams that manage their direct paging integrations through infrastructure as code.
Prefer important notification policy for direct paging
Control the default notification urgency when users page responders through Slack.
When Prefer important notification policy is enabled, direct pages sent through Slack use the recipient’s important personal notification policy instead of the default policy. This ensures that direct pages trigger higher-urgency notifications, such as phone calls or repeated messages.
When disabled, direct pages use the recipient’s default personal notification policy.
Require resolution notes
Enforce documentation requirements when resolving alert groups.
When enabled, responders must provide a resolution note before resolving an alert group. This helps teams maintain a consistent response process and improve post-incident visibility.
This requirement also applies in Slack — if an alert group is resolved, you can’t use the 🤖 (:robot_face:)
reaction to remove the last remaining resolution note. For more information about Slack reactions, refer to the IRM Slack documentation.
Note
This requirement is enforced in the IRM UI, Slack, and bulk resolve operations. The OnCall public API resolve endpoint doesn’t enforce this requirement. If your team resolves alert groups through the API, consider adding resolution notes programmatically.
Require team membership for updates
Restrict resource updates to users who are members of the resource’s team.
When enabled:
- Users must be a member of a team to create or update resources owned by that team.
- For alert groups, this includes acknowledging, resolving, silencing, and other state changes.
- The restriction applies across all surfaces: the IRM UI, mobile app, Slack, Microsoft Teams, and the public API.
- Resource write permissions are still required in addition to team membership.
The following users bypass this restriction:
- Users with the Admin basic role or IRM Admin RBAC role.
- Service accounts.
When disabled, any user with appropriate write permissions can update resources regardless of team membership.
Note
This setting only restricts write operations. All users with read access can still view resources from any team, subject to team visibility settings.
Affected resources
This setting applies to the following resource types:
- Alert groups (acknowledge, resolve, silence, and other state changes)
- Integrations
- Escalation chains and policies
- On-call schedules and shifts
- Shift swaps
- Routes
- Outgoing webhooks
- Resolution notes
- Labels
For more detail on how teams work in IRM, refer to Teams.
Disable schedule updates in the past
Prevent modifications to on-call schedules for past events and enforce future-only scheduling.
When enabled:
- Users can’t create overrides or shift swaps with start times in the past.
- Users can’t delete overrides or shift swaps that are already in progress or in the past.
- When deleting a rotation, users can’t delete past shifts.
- When editing a rotation, users can only use the Save as new option.
- All new schedule entries must have a start date/time set to Now or a future date/time.
This setting only applies to web-based schedules.
For Terraform or API-based schedules, use the until parameter to end a rotation and create a new one.
Manage linked Slack profiles
Admins can view and manage linked Slack profiles on behalf of users in their organization. In the IRM Users list, any profile associated with a user is shown in the Linked profiles column.
Profiles can be automatically synced if the user’s email in Grafana matches the email used in Slack.
Sync all Slack profiles
To sync all linked profiles for IRM users:
- In your Grafana Cloud stack, go to Alerts & IRM > IRM > Users.
- In the Linked profiles column, click the Sync user profiles icon.
Any users with matching Slack profiles are synced and displayed in this column.
Unlink a Slack profile
To manually unlink a Slack profile for an individual user:
- Next to any user with a linked profile, click the options menu (three dots).
- Select Unlink Slack to remove the linked profile from this user on the current stack.
