# On Call Hours Per User

{% hint style="info" %}
**Availability**

On Call Hours Per User is available on **Pro, Premium, and Enterprise** plans
{% endhint %}

{% hint style="info" %}
**Access Control:**

On Call Hours per User is available at a team level

* **RBAC (Role-Based Access Control):** Users with "read analytics" permission can access team-level analytics for that specific team.
* **OBAC (Owner-Based Access Control):** All users in a team can access team-level analytics for that team.
  {% endhint %}

## Data Retention

Data is retained for 6 months. You can filter upto 31 days of data at a time

## Understanding the chart

<figure><img src="/files/YqWmJogW5e3BB6aYpcCD" alt=""><figcaption></figcaption></figure>

* On Call Hours: The total number of hours a user has been on call as part of their regular schedule rotations, under applied filters. This calculation accounts for any overlapping time across multiple rotations and schedules to avoid double-counting.
* Override Hours: The total number of hours a user has been on call as part of overrides, under applied filters. This calculation accounts for any overlapping time across multiple overrides to avoid double-counting.

### Filters

The following filter fields are available

* Schedule
* Schedule Owner

{% hint style="info" %}
When filters are applied, **on-call hours** and **override hours** are recalculated for each user based on the selected schedules.

To view on-call hours across *all* schedules, make sure no filters are applied.
{% endhint %}

#### **Schedule Owner**

Use the Schedule Owner filter to view on-call hours for schedules managed by specific users or squads.

**Example:** Filter analytics to show the number of hours each user spent on schedules owned by the *Ops Squad*.

## Export

You can export the On-Call Hours per User chart as a CSV file. Once requested, the export will be generated and sent to your email.

## API

The On-Call Hours per User data can also be accessed via API. Refer to the [API documentation](https://apidocs.squadcast.com/#ceb600b4-cb9d-4455-b039-6c0eb73aa206)

*Have any questions?* [*Ask the community*](https://community.squadcast.com/view/home)*.*


---

# Agent Instructions: 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:

```
GET https://support.squadcast.com/analytics/on-call-hours-per-user.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.