Skip to main content
LoginSign Up

On-call overview

Open On-call from the sidebar to see whether you are on duty now, what shifts are coming, who else is covering, and recent pages Incido sent you. Under the same menu you manage organization setup: Teams, Escalation policies, and Escalations.

For team setup and rosters, see Teams and rosters. For schedule configuration, see On-call schedules and Rotations and overrides. For alerting rules, see Escalation policies.

What you see on the landing​

What appears depends on your subscription, whether teams and policies exist, and whether you are on a rotation.

Subscription without on-call. You see an explanation and either a billing link (if you may manage plans) or guidance to contact someone who can.

No teams and no escalation policies. Users who may create both see a short setup explanation and Create team (quick start). Everyone else is asked to contact an administrator.

Teams exist but no escalation policies. A warning explains that escalations cannot be delivered until a policy exists. Users who may create policies see a link to Escalation policies. Users who manage on-call configuration also see Teams and schedules. Create team (quick start) stays in the header when you may add teams.

Not on a rotation. If you do not manage schedules or policies, you see that you are not on a schedule yet and guidance to contact an administrator. This is common when someone joins before rotations are updated.

On a rotation. The landing shows:

  • On-call now — a banner stating whether you are on duty at this moment.
  • Recent notifications for you — up to five escalations from the last 72 hours (your latest attempt per escalation), with policy name, status, and time in your timezone.
  • Acknowledge — for active escalations, acknowledge from the landing without opening the incident first.
  • Your next shifts — up to five upcoming shifts from the next 90 days.
  • Who is on call now — colleagues currently on duty, with schedule name and shift end time.
  • Notification contact methods — read-only summary with a link to change how Incido reaches you across organizations.

Open Escalation details on a notification row to review the full delivery history (every attempt, channel, step, and outcome). The incident title remains the main link to the incident.

Personal schedule and home​

My Schedule (from Home or your personal navigation) shows upcoming on-call shifts across every organization you belong to. It uses the same computed shift data as alerting, without switching tenant context.

Home may also surface on-call widgets when you have shifts in any organization.

Notification preferences live under your profile (Notification contact methods). Those settings apply across organizations; the on-call landing links there by design.

Escalations list​

Escalations under On-call is a read-only index of escalation runs. Open a row for the same detail view linked from Escalation details on the landing.

During an active incident, Bring in responder on the incident view pages additional users, a team, or an on-call schedule outside the normal escalation chain. See Incidents.

Permissions​

Access to schedules and rotations follows the same pattern as teams. You may have access through any of these paths:

  • Organization-wide schedule permissions (for example View:OnCallSchedule).
  • Matching team permissions (for example View team).
  • Team administrator membership on the owning team.

Ask an administrator to align your role if you expect to manage schedules but cannot open them.

What changes on the public frontend​

The on-call landing is an operator tool. Customers on your public status page do not see this UI. Alerting driven by policies and schedules still affects incidents and communications as described in Incidents and Escalation policies.

Operational effects​

Shift times on the landing use your personal timezone when set on your profile; otherwise the organization default applies.

Colleague coverage on the landing is schedule-based only. It does not show escalation chains or who would be paged if someone does not acknowledge.

When you open another member from Users or Responsible People on an incident, their Profile lists Teams in this organization and delivery history scoped to what you may see. That history follows incident retention when closed incidents are purged, as described in Incidents.

Troubleshooting​

You expected to be on-call but the banner says you are not. Confirm you appear on a rotation member list for a schedule in this organization and that computed shifts exist for the current window. The landing reads the same shift rows as the calendar and alerting.

You see a warning that no escalation policy exists. Someone with permission should open Escalation policies and add one, or complete Create team (quick start) with policy creation enabled.

You cannot see schedule or rotation screens you expected. Your role may grant team access, organization-wide schedule access, or team-admin membership on the relevant team. Ask an administrator to align permissions with how you are expected to operate.