> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/users-and-roles/roles-in-cortex-xsoar/shift-management.md).

# Shift Management

Manage user shifts and on-call schedules in Cortex XSOAR 6.15.

Shift management helps you define multiple shifts within Cortex XSOAR. Each shift can be assigned to a user role so you are able to assign one or more analysts across different shifts.

You can do the following:

* Enable incidents to be routed automatically to analysts based on shifts, workload, and machine learning recommendations, ensuring full staff coverage for incoming incidents.
* Define multiple shifts, which can be added to a role, and in turn assigned to a user. To manage shift periods for users, see [Managing Shifts](/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/users-and-roles/roles-in-cortex-xsoar/shift-management/managing-shifts.md).
* Automatically route incidents to analysts based on shifts, workload, and machine learning recommendations in playbooks and automations. For example, the **`AssignAnalystToIncident`** automation, automatically assigns the incident based on who is on call and who is active (not set to away).

After assigning the role to users, Cortex XSOAR recommends who to assign incidents. When assigning an analyst to an incident, these shifts can be taken into account.

{% hint style="info" %}

### Note

If you want to consider on-call users only, run the `getOwnerSuggestions` command.
{% endhint %}


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/users-and-roles/roles-in-cortex-xsoar/shift-management.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.