> 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/cortex-xsiam/configure-cortex-xsiam/automations/lists/create-a-list.md).

# Create a list

Create Cortex XSIAM lists to store reusable automation data.

To create a Text, Markdown, HTML, CSS, or JSON list type:

1. Go to Settings → Configurations → **Object Setup** → Lists → Add a List.
2. Enter a name for the list.
3. From the list, select the **Content Type**.
4. Set **Permissions** for the list. By default, all roles can read and edit the list. You can instead choose specific roles to have read-only or read-and-edit access.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>If you intend to use the list as part of an Automation Exclusion Policy, we recommend choosing specific roles for read and edit access. For more information on using lists in exclusion policies, see <a href="/cortex-xsiam/configure-cortex-xsiam/automations/automation-exclusion-center/manage-automation-exclusion-policies.md">Manage automation exclusion policies</a>.</p></div>
5. Add content as required. For an example of a JSON list and how to use it, see [Use cases: JSON lists](/cortex-xsiam/configure-cortex-xsiam/automations/lists/use-cases-json-lists.md).
6. To save, do one of the following:
   * Click **Save**.
   * Click **Save Version** to save your changes in **Version history for all Lists**. This allows you to revisit and restore previous versions.

{% hint style="info" %}
If you want to edit a list from a content pack, you need to duplicate or detach a list. Detached lists do not receive updated content in subsequent Cortex XSIAM content releases. To retain an updated list, reattach it.
{% 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 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/cortex-xsiam/configure-cortex-xsiam/automations/lists/create-a-list.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 `automate deployments from our CI pipeline` 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.