> 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/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/playbooks/playbook-task-fields/create-section-headers.md).

# Create Section Headers

Create section headers to organize Cortex XSOAR 6.15 playbook tasks.

Section headers tasks are used to manage the flow of your playbook and help you organize your tasks efficiently. You create a Section Header task to group a number of related tasks under the Section Header.

Section headers can also be used for time tracking between phases in a playbook. When you start time tracking, you should apply the Start action for the section header. Since you are using this to time track a particular phase of an investigation, you should add a stop timer section header when the phase completes. The time tracking data can be used to display in dashboards and report time trends.

1. In the playbook, edit the playbook.
2. Click **+** (Create task).
3. Select the **Section Header** option.
4. Enter a meaningful name for the section header.
5. For a time tracking header:
   1. Click the **Timers** tab.
   2. Select the action to take when the timer is triggered. (Start, Stop, or Pause).
   3. Select the field on which the timer is applied.

      ![playbook-section-header.png](https://content.gitbook.com/content/8xEMUKpU65o1wagTHaO3/blobs/MNE9EYvCp35o8WkXavnm/9659e72bb54bcce7ff3854d84bb506c3e99e6bf7ade6d46fa8fa44b17ca6f817.png)
6. Click **Save**.


---

# 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/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/playbooks/playbook-task-fields/create-section-headers.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.