Teams and rosters
A team groups people who share on-call responsibility. Each team owns one or more on-call schedules. Escalation policies reference teams or their schedules when deciding who to page.
Open Teams under On-call to list teams, open a team, or run Create team (quick start). For your personal on-call summary, see On-call overview.
Team view layout
When you open a team, the page combines roster, live coverage, and schedules:
- Main column — searchable Team members table (who belongs to the team and their role).
- Sidebar — Who is on call now for this team.
- Below the members table — recent team escalations and the team's on-call schedules (links into each schedule's rotations and calendar).
In the Team details block (key and name):
- Related escalation policies — up to five linked badges when you may open escalation policies. Disabled policies are labeled in the badge. View all escalation policies opens the policy list with Team in routing preset to this team when more than five apply.
- Components — up to five linked badges when you may open the component catalog. View all components opens the component list filtered to this team when there are more than five. See Components, Severities, And Status Catalogs for how component assignment works.
Team members
The Team members section lists everyone on the team and whether each person is an Administrator or Member.
- Team administrators manage the roster for their own team.
- Users with organization-wide team management permissions can adjust any team's roster without being listed on that team.
- Adding a member only selects from users who already belong to the organization. The roster does not create dashboard accounts.
Use table actions to add, edit, or remove members.
Team settings
Edit team opens a modal with:
- Key and name — stable identity for API and configuration import/export.
- Receive alerts — when off, the team does not receive alerts through escalation steps that target the team, even if schedules exist.
Team enabled status in the list view toggles Receive alerts for quick changes.
Schedule limits
Two limits apply when you add schedules:
| Limit | Rule |
|---|---|
| Per team | Up to five schedules per team. |
| Subscription | Your plan caps total schedules in the organization (for example Starter allows one schedule organization-wide; Pro allows three; Business allows fifteen). |
You may hit the plan cap before the per-team cap. Add schedule on the team view is hidden when either limit is reached.
Create team (quick start)
Create team (quick start) is available from the Teams list and the On-call landing when your role allows creating teams and escalation policies.
The wizard steps:
- Team — name and key.
- Rotation — who is on the rotation, shift length (default one week), and handoff settings.
- Alerting (optional) — whether to create a matching escalation policy.
Incido creates a primary schedule automatically (using your user timezone) with a primary key. When policy creation is enabled, it builds routing and a first team-target step without separate schedule or policy keys.
Minimum severity acts as a floor: the new policy matches incidents at that severity and every more severe level in your organization (lower order on severity levels means higher severity).
Components (optional) assigns unowned catalog components to the new team and scopes policy routing to incidents affecting those components. Leave empty to match any incident at or above the severity floor. Components already assigned to other teams are omitted from the picker.
Assign role on acknowledge (optional) picks an incident responder role so acknowledgements from this policy assign that role on the incident. Incident responder roles are configured under Settings.
Adding a schedule without quick start
On the team view, use Add schedule when limits allow. After save you land on the schedule view to configure rotations and overrides. See On-call schedules.
There is no top-level Schedules entry in the sidebar. Bookmarks to schedule URLs still work.
Permissions
- View team — open the team view; team members can view their own team without org-wide View team.
- Update team — edit team settings and roster (team admins or org-wide Update team).
- Create team — add teams and run quick start (with Create escalation policy for the policy step).
Schedule access also respects organization schedule permissions and team-admin membership on the owning team. See On-call overview.
Troubleshooting
You cannot add another schedule. Check both the per-team limit (five) and your subscription's total schedule cap on billing or plan details.
A team member cannot see the team. They must be added to the roster, or have organization-wide View team.
Components on the team view look incomplete. Only users who may open the component catalog see component badges. Others still see schedules and members.