> 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/customize-and-configure-cortex-xsoar/work-with-slas/create-an-sla-field.md).

# Create an SLA Field

By default, the system comes with several SLA and Timer fields.

The SLA fields count down the time remaining, while a Timer field serves as a counter, counting the time that has elapsed since started. If no SLA is defined, the SLA fields serve as a counter.

1. Navigate to Settings → OBJECTS SETUP → Incidents → **Incident Fields**.
2. Click **New Field**.
3. Under **Field Type** field, select **`Timer/SLA`**.
4. Enter a name and optional tooltip for the field.
5. Define a duration for the SLA of this field. If no value is entered, the field serves as a counter.

   By default, the SLA field shows hours and minutes. You can change this to days and hours, by clicking **Hours**.
6. Determine the risk threshold for this timer. When the timer falls below this threshold, it is considered at risk. By default, the threshold is 3 days, which is defined in the [global system parameter](/xsoar-6-administrator-guide/6.13/learn-about-cortex-xsoar/customize-and-configure-cortex-xsoar/work-with-slas/configure-the-global-risk-threshold.md).
7. Under **Run on SLA Breach**, select the script to run when the SLA time has passed. For example, email the supervisor or change the assignee.

   Only scripts to which you have added the SLA tag will appear in list of scripts that you can select.

   ![SLA\_Field.png](/files/dq2rpmS08eo9mHd4d147)
8. 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 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/customize-and-configure-cortex-xsoar/work-with-slas/create-an-sla-field.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.