> 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.13/learn-about-cortex-xsoar/onboarding-in-cortex-xsoar/users-and-roles/roles-in-cortex-xsoar/shift-management/managing-shifts.md).

# Managing Shifts

You can define shifts for various roles and then add them to automations, playbooks and incidents.

1. Define a Role.
2. In the **Shifts** field, click **Add Shift** and add the required period.

   Weekly shifts start on Sunday and are specified in the UTC time zone format.

   For example, we create a role called First Shift and add a shift starting on Sunday and ending Monday.

   ![shift.png](/files/8jvS39mL16WyvVZ5fnmO)
3. Click **Save.**
4. (Optional) To add the role to a user, in the **Users** tab, select the user you want to add.

   ![roles.png](/files/9xCR0tdKLIV8JhrsMTZ1)
5. Click **Roles**.
6. From the drop-down list, select the role you created.

   ![add-roles.png](/files/dek2dt1VP1lo0C0ahq8s)
7. Click **Save**.

   You can also assign the role to a playbook or automation as required.
8. (Optional) You can view on-call users’ details in a dashboard by adding the required widgets.

   ![shift-dashboard.png](/files/Tx6aNUYSUVYQtgeTzzwy)

   When assigning an incident, you can manually assign it to analysts who are on-call or the incidents can be assigned automatically, for example, the **`AssignAnlystToIncident`** automation.


---

# 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://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.13/learn-about-cortex-xsoar/onboarding-in-cortex-xsoar/users-and-roles/roles-in-cortex-xsoar/shift-management/managing-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.