Manage settings for Grafana IRM
The Admin & API tab in Grafana IRM settings lets admininstrators manage global configuration options that affect how users and teams interact with IRM. From this tab, you can customize various settings, as well as access your API endpoint URLs.
To access these settings in the Grafana Cloud main menu, go to Alerts & IRM > IRM > Settings > Admin & API.
Notification channel visibility
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 do not enable or disable the integration itself. To manage integrations, navigate to IRM > Integrations > Apps. For more detail, refer to IRM Integrations.
Manually manage direct paging
Enable manual control over direct paging integrations in your organization.
By default, Grafana IRM automatically creates and manages direct paging integrations 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:
- You take manual control over the creation and management of direct paging integrations
- Grafana IRM stops automatically creating direct paging integrations for new teams
- Existing direct paging integrations remain unchanged and can now be managed manually
This setting is especially useful for teams that want to manage their direct paging integrations through infrastructure as code (IaC) tools like Terraform or Crossplane.
Note
Enabling this setting does not delete existing direct paging integrations. You can either import existing integrations into your IaC tooling or delete and recreate them manually.
Require resolution notes
Enable this setting to enforce documentation requirements when closing alert groups.
When enabled, responders must provide a resolution note before closing an alert group. This requirement helps teams maintain consistent response process and improve post-incident visibility.
Require team membership for updates
Use this setting to restrict update access to users who are members of a team. This is helpful if you want team resources to be visible to everyone, but editable only by team members.
When enabled:
- Users must be a member of a team to create or update resources owned by that team
- Resource write permissions are still required
Note
Admin users can edit any resource, even if they are not a member of the associated team.
For more detail, refer to Manage teams in Grafana IRM
Disable schedule updates in the past
Enable this setting to prevent modifications to on-call schedules for past events and enforce future-only scheduling. This ensures historical records remain accurate and prevents unintended changes to past schedule entries.
When enabled:
- Users cannot create overrides or shift swaps with start times in the past
- Users cannot delete overrides or shift swaps that are already in progress or in the past
- When deleting a rotation, users cannot 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
Note
This setting only applies to web-based schedules. For Terraform/API-based schedules, you can manage past schedule modifications using the existing
until
parameter to end a rotation and create a new one.
Access IRM API endpoints
The Admin & API tab displays the base URLs for IRM APIs:
- OnCall API URL:
http://oncall-engine.default.svc.cluster.local:8080
- Incident API URL:
http://incident-api.incident.svc.cluster.local:8080
Use these endpoints for programmatic access or when setting up infrastructure as code.
For more detail about using the IRM APIs, refer to the IRM API documentation.
Note
For authentication, use Grafana Cloud service account tokens. OnCall API keys are deprecated and should no longer be used (Existing tokens will continue to work).