incident.io is designed to help you handle all kinds of incidents across your business, from disks running out of space, to laptops getting lost on a train. However, most of the time, most people want to only see incidents, as well as configuration, for their team(s). Essentially, only show items that are most relevant to their day-to-day work.
So, if you tell us about your teams and who is in each team within Catalog, you'll be able to leverage:
Escalation paths belonging to a team are automatically linked in Catalog, so each team can control what it means to page them
With alert routes and workflows, you don't need to set up loads of new configuration for each team; Instead, use attributes on your teams to adjust where alerts and messages go. Learn more about alert routing and workflows.
When viewing escalation paths and schedules, those owned by your team will always appear at the top of the list — super useful if you're a manager who's not on-call but wants to keep an eye on your team's rota!
When browsing incidents and alerts, we'll only show those related to your team
Creating teams
In Settings → Teams, jump into the three-step team setup wizard.
First, tell us about any existing teams configuration you have, that you'd like us to use. If you're already managing team memberships in another system, we can sync them across.
You can sync teams and their members from:
An identity provider or HR system like Okta or HiBob using SCIM
Cortex
Linear
Opslevel
Slack
If you manage teams and their members somewhere else, let us know!
If you want to just create a few teams to try things out, you can manage membership manually instead:
Finally, you can add any extra attributes to your Team type. These can be really useful in Workflows and Alert Routes, for example to send messages to a different channel for each team. If you're not sure, you can always come back later to set up new attributes!
If you want to migrate to using SCIM to manage team memberships later, you can run this wizard again, from Settings → Teams → Configure.
Managing your teams
There are three different ways you can manage teams:
1. Manually in incident.io
If you just have a few teams, this is the quickest way to get started. You can add, remove, and manage members of teams from Settings → Teams, and change which schedules and escalation paths they own:
2. With SCIM, or another integration
If you've got your team memberships managed in a SCIM-compatible provider like Okta, Google Workspace, or Microsoft Entra ID, we will automatically sync changes to team members.
You can create new teams linked to SCIM Groups in Settings → Teams, and change which schedules and escalation paths they own, but you'll need to add and remove members in your SCIM provider.
3. Using catalog-importer or Terraform
If you're already using catalog-importer or Terraform to manage your Catalog, you can also use this to manage teams and their members! This is really powerful if you have this data in code already, and want to manage relationships between teams, services, and other infrastructure components in code.
You can read more about using catalog-importer here.
You won't be able to manage your teams and their members in Settings → Teams, but you can still link them to schedules and escalation paths here.
Automatic filtering by team
By default, some pages in the dashboard will be filtered by the teams you're a member of. So if you're in the "Payments" team, you will see all incidents that affect the Payments team.
You can change this default when prompted to, or from Preferences → My dashboard.
Pro tip: you can always access your preferences by using our ⌘+K menu and searching "preferences".
Incidents and alerts
By default, incidents will be filtered using the "Affected teams" custom field, and alerts will be filtered by the "Team" attribute. You can change which custom field and alert attribute we use, or disable this entirely, in Settings → Teams → Configure.
Escalation paths and schedules
If you're using incident.io On-call, you'll can link your teams to escalation paths and schedules when setting them up. You can change this later when editing the schedule or escalation path, or when editing the team.
If you're managing schedules or escalation paths with Terraform, you'll need to also set the team_ids attribute, and you won't be able to manage this in the incident.io dashboard.
Routing alerts and escalations to teams
To make alert routing to escalation paths easier, when you attach an escalation path to a Team, we'll automatically link that back in Catalog:
You can use this to automatically route alerts to teams:
If your alerts are tagged by service, you can route escalations based on the service's owning team. Read more about how to route alerts in 📄 Creating escalations and incidents from alerts.