> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/on-call-management-and-escalations/on-call-schedules/my-on-call-shifts.md).

# My on-call shifts

See all your on-call shifts in one calendar, take over a colleague's shifts, hand yours to someone else, and subscribe to them from a calendar app.

**My on-call shifts** shows all your on-call time in one calendar, whichever schedule or escalation policy it comes from. From there, take over a colleague's shifts, hand your own to someone else, or subscribe to your shifts from a calendar app.

To open it, click **My on-call** in the top bar. When the window is too narrow for the full top bar, **My on-call** moves into its **…** menu. The page is also the first tab on the **On-call schedules** and **Escalation policies** pages. Stakeholders and viewers don't have it.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2Fgit-blob-bc24d700b0dd426b78d161d6f460af8d88910dea%2Fmy-on-call-shifts.png?alt=media" alt="The My on-call shifts page. Take on call, Override my shifts and Export as calendar sit in the header, above tabs for My on-call shifts, On-call schedules and Escalation policies. A small month calendar on the left marks days with an orange dot, and a month calendar on the right shows each shift as a bar labeled with its level and schedule, such as Level 1: SRE Team Primary On-call."><figcaption><p>A dot in the small calendar marks each day on which you are on call.</p></figcaption></figure>

## What counts as being on call

An escalation policy appears here when at least one alert source uses it. A policy that only event flows or routing keys reach doesn't appear. Within such a policy, you appear on every level that escalates to:

* you by name,
* a schedule you are a member of, or
* a team you are a member of.

How the calendar shows a level depends on how you are in it:

* **Through a schedule:** your shifts from that schedule, with overrides applied. The entry is named after the level and the schedule, for example **Level 1: SRE Team Primary On-call**.
* **By name or through a team:** one continuous entry, from the day the policy was last changed onward, because that level can reach you at any time. The entry is named after the level and the policy.

## Choose which levels you see

**My escalation policies**, below the small calendar, lists every level you are in. Tick the levels whose entries you want in the calendar. When you are in more than three levels, **Select all** or **Deselect all** sits above the list.

The icon at the end of each row says how you are in that level: a calendar for a schedule, one person for your name, and two people for a team. Hover over a row and click its arrow to see the policy's full chain of levels.

On your first visit, every level is ticked. ilert saves your selection to your user account, together with the **Timezone** at the bottom of the calendar and the **Month** or **Week** view. The same setup then applies in any browser you sign in from. The timezone starts as the one in your profile.

The selection matters beyond this calendar:

* **Override my shifts** only offers your shifts from the ticked levels, and it is unavailable while no level is ticked.
* The calendar export uses it unless you turn that off. See [Subscribe from a calendar app](#subscribe-from-a-calendar-app).
* The mobile app counts only the ticked levels for your on-call status. See [On-call widget in the mobile app](/on-call-management-and-escalations/on-call-schedules.md#on-call-widget-in-the-mobile-app).

## Take over someone else's shifts

Taking someone's on-call puts you on their shifts as an override. Their schedule itself doesn't change.

{% stepper %}
{% step %}

### Choose the person

Click **Take on call**. In **User**, choose whose shifts you want to take.
{% endstep %}

{% step %}

### Set the time range

Set **Start** and **End**, or use the links below them. **now**, **tomorrow** and **next week** set Start to now, 24 hours from now or 7 days from now. **+1 hour**, **+3 hours** and **+1 week** add to End each time you click them. The links work once you have chosen a user.

ilert lists that person's shifts that overlap the range, grouped by schedule. It covers every schedule an escalation policy uses, whichever levels you ticked. While a team is selected in the top bar, only that team's escalation policies count, so choose **All teams** there to see every shift.
{% endstep %}

{% step %}

### Pick the shifts

Every listed shift is ticked. Untick the ones you don't want, and any that have already ended.

A ticked shift is taken over from its start to its end, even where it runs past **End**. To take only part of one, click its pencil, change the times, and confirm with the check mark.
{% endstep %}

{% step %}

### Confirm

Click **Take on call**. ilert confirms with **Shifts have been successfully overridden**.
{% endstep %}
{% endstepper %}

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2Fgit-blob-75cfce867375efd4528d14d723c48e9c28c5f57e%2Ftake-on-call-dialog.png?alt=media" alt="The Take someone else&#x27;s on-call dialog. User is set to Humza Vega, with Start and End fields and shortcut links beneath each. Below, the shifts found in that range are grouped by schedule. Each shift has a ticked checkbox, its start and end, and a pencil icon. Take on call and Cancel are at the bottom."><figcaption><p>Each shift is listed with its full start and end, even where it runs past the range. The pencil takes only part of it.</p></figcaption></figure>

To confirm the change, open the schedule. Its **Overrides** row shows you on those shifts.

## Hand your shifts to someone else

{% stepper %}
{% step %}

### Choose who takes over

Click **Override my shifts**, or drag across days in the calendar. In **User**, choose who should take your shifts.
{% endstep %}

{% step %}

### Set the time range

Set **Start** and **End**. The button starts the range now and ends it an hour later; dragging in the calendar uses the days you selected. ilert lists your shifts in the range, from the levels ticked in **My escalation policies**.
{% endstep %}

{% step %}

### Pick the shifts and confirm

Untick the shifts to keep, or shorten one with its pencil, as when taking on-call. Then click **Override my shifts**.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Overrides only apply to on-call schedules. If an escalation policy names you directly, handing over your shifts doesn't take you out of that policy. Ask someone who can edit the policy to change it.
{% endhint %}

Handing over a shift takes write access to the schedule. That means the **User**, **Admin** or **Account owner** role, or the **Team User** or **Team Admin** role in a team that owns the schedule. A **Responder** can take other people's shifts but can't hand over their own; ilert rejects the request with a message that you may only override for yourself. The person taking over can't be a stakeholder or viewer. See [User roles and permissions](/users-and-access-management/user-roles-and-permissions.md).

On a schedule owned by a [private team](/users-and-access-management/teams.md#private-teams), only admins and members of a team that owns the schedule can override its shifts. Members whose team role has no write access can only put themselves on shifts.

## Limits that apply to both dialogs

* **Start** and **End** must be at least 3 minutes and at most 3 months apart. If End is later than that, ilert shows **You can only override a shift within the first 3 months after the start date.** and moves End back. The limit applies to the range, not to the overrides: a listed shift is still taken over whole, however long it is.
* A shift that has already ended can't change hands, and a shift that is under way changes hands from now. ilert stops at the first ended shift that is still ticked, with **Cannot add override retroactively on schedule** and the schedule's name.
* Each dialog loads at most 250 on-call entries for the range and doesn't say when it hits that limit. For a long range, or someone with many shifts, use shorter ranges.
* ilert saves the overrides one after another. When it stops with an error, the ones before it are already saved, so check the schedules before you try again.

## Remove an override

This page can't remove overrides, not even the ones you created here. Open the schedule instead, click the override in its calendar, and choose **Delete selected override**. The override is removed at once, without a confirmation. See [Overrides](/on-call-management-and-escalations/on-call-schedules.md#overrides).

## Subscribe from a calendar app

Click **Export as calendar** and choose how to use your shifts:

| Option                          | What you get                                                                                                        |
| ------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
| **Subscribe to calendar**       | A subscription your calendar app keeps up to date. Clicking it hands the link to the calendar app on your computer. |
| **Download calendar file**      | An `.ics` file with your shifts as they are now. It doesn't update.                                                 |
| Copy icon next to either option | A short link to paste into any calendar app that subscribes by URL.                                                 |

**Apply my filter selection to calendar export** is ticked by default and limits the export to the levels ticked in **My escalation policies**. ilert writes that selection into the link itself, so changing your ticks later doesn't change a calendar you already subscribed to. Copy the link again to pick up a new selection. With the option unticked, the export includes every escalation policy you are in.

The export covers your shifts from the first day of last month to the end of the month after next. Each shift becomes an event named **On-call duty**, followed by your name, the schedule or policy, and the level. Each event has a reminder 15 minutes before it starts.

{% hint style="warning" %}
The link works without signing in to ilert. Anyone who has it can see your shifts, so share it only with your calendar app.
{% endhint %}

## Related

* [On-call schedules](/on-call-management-and-escalations/on-call-schedules.md)
* [Escalation policies](/on-call-management-and-escalations/escalation-policies.md)
* [Coverage requests](/on-call-management-and-escalations/on-call-coverage-requests.md), for asking a colleague to take a shift from the mobile app


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ilert.com/on-call-management-and-escalations/on-call-schedules/my-on-call-shifts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.