> 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/customize-cases-and-issues/create-a-case-domain.md).

# Create a case domain

Create custom Cortex XSIAM case domains to organize case workflows, statuses, resolution reasons, and access control.

{% hint style="warning" %}
Before you add a custom domain, please review the built-in options. For more information, see [Case and issue domains](/cortex-xsiam/detect-investigate-and-respond-to-threats/investigation-and-response/overview-of-cases/case-and-issue-domains.md).

We recommend using the built-in domains where possible. Custom domains might not be supported by all content. In addition, custom domains affect Cortex XSIAM’s ability to learn, correctly identify, and score future cases.

Smart grouping and SmartScore are not supported for custom domains.
{% endhint %}

Create custom Cortex XSIAM case domains to separate work efforts and organize case management workflows. Each domain can use tailored statuses, resolution reasons, and access controls.

### Manage Cortex XSIAM case domains

View all case domains under **Configurations** → **Object Setup** → **Cases** → **Domains**. You can edit built-in domain properties and create custom domains.

Consider the following information:

* You can't merge cases with different domains.
* SmartScore and smart grouping are not supported for custom domains.
* For SBAC, use the Cases and Issues scoping area to define case and issue domains that enable you to control access to your domains. For more information, see [Manage user scope](/cortex-xsiam/onboard-cortex-xsiam/post-deployment/manage-user-roles-and-access-management/manage-user-scope.md).
* Domains might affect custom content that is connected to cases and issues. Review your custom content to ensure it is associated with the intended domains. This includes:
  * Automation Rules
  * Starring Rules
  * Notifications
  * Issue Exclusions
  * Scoring Rules
  * XQL that accesses the cases or issues datasets in Scheduled Queries and Widgets

### Create a custom Cortex XSIAM case domain

* Adding custom domains requires a View/Edit RBAC permission for Case Properties (under Object Setup).
* Once created, a custom case domain cannot be deleted or renamed.

1. Go to Settings → Configurations → Object Setup → Cases → Domains .

   The existing domains are listed.
2. Click on + New Domain.
3. Assign a name and color to the domain, and an optional description.
4. In the Status field, select one or more statuses that are relevant to the domain. These statuses will be available for selection in the cases and issues associated with this domain.
5. In the Resolution Type field, select one or more resolution reasons that are relevant to the domain. These reasons will be available for selection in the cases and issues associated with this domain.
6. Click Save.
7. (Optional) Update SBAC scoping to enable access to the domain.
   1. You can perform the following:
      * To enable access to the domain for a User Group, go to Settings → Configurations → Access Management → User Groups.
      * To enable access to the domain for a User, go to Settings → Configurations → Access Management → Users.
      * To enable access to the domain for an API key, got to Settings → Configurations → Integrations → API Keys.
   2. When editing an existing User Group, User, or API key, in the Scope tab you can update the granular scoping for the new Endpoints domain.
   3. Click Save.

<br>


---

# 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/customize-cases-and-issues/create-a-case-domain.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.