> 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-cloud-runtime-security/cases-and-issues/analyze-and-resolve-cases/additional-case-actions/assign-a-case-team-and-restrict-access.md).

# Assign a case team and restrict access

You can assign individual users and entire user groups to specific roles within a case team. For sensitive or high-risk cases, you can also restrict access to a case so that only assigned case team members can see or take action.

For more information about the different team roles, see [Overview of case teams and roles](/cortex-cloud-runtime-security/cases-and-issues/overview-of-cases/overview-of-case-teams-and-roles.md).

{% hint style="warning" %}
To change the scope and access of a case, you must have the **Restrict Case Access** permission under **Cases & Issues**.
{% endhint %}

### How to assign a case team and restrict access

{% stepper %}
{% step %}

#### **Select the main case assignee**

Click the assignee icon and select a user.

{% hint style="info" %}
This is the primary owner responsible for managing and resolving the case.
{% endhint %}
{% endstep %}

{% step %}

#### **Define the case team**

1. Click **Manage case team**.
2. Add users or user groups, and select their specific roles (Collaborator or Watcher).
   {% endstep %}

{% step %}

#### **Restrict case access**

Under **General access**, select **Team Only**.

{% hint style="info" %}
Restricting case access limits visibility exclusively to the main case assignee and any users or user groups assigned to the case team as **Collaborator** or **Watcher**.
{% endhint %}
{% endstep %}

{% step %}

#### **Save your changes**

{% endstep %}
{% endstepper %}

#### Alternative methods

You can also run this process using these alternative methods:

* **Agentic Assistant:** Use natural language prompts in the Agentic Assistant to assign a user or user group to roles in the team, and restrict case access.
* **Playbooks:** Create a playbook task that assigns team members and changes the default case scope. For more information, see [Playbook examples](/cortex-cloud-runtime-security/cases-and-issues/analyze-and-resolve-cases/additional-case-actions/assign-a-case-team-and-restrict-access/playbook-examples.md).
* **API:** Run the **setCase** command with the following arguments:

<details>

<summary>setCase arguments</summary>

For more detailed information about using these arguments, see [setCase](/cortex-commands-guide/case-commands.md).

<table data-header-hidden><thead><tr><th width="240"></th><th></th></tr></thead><tbody><tr><td><code>case_team_operation</code></td><td>Add, replace, or remove team members</td></tr><tr><td><code>case_team_ids</code></td><td>Specify users (email) or user groups (UUID)</td></tr><tr><td><code>case_team_member_types</code></td><td>Define the team member type (Individual user or user group)</td></tr><tr><td><code>case_team_roles</code></td><td>Set the team member role (contributor or watcher)</td></tr><tr><td><code>access_mode</code></td><td><p>Set case visibility:</p><ul><li><code>CASE_SCOPE</code>: (default) any user whose scope permits can view the case.</li><li><code>TEAM_ONLY</code>: restricts access to team members only.</li></ul><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>You cannot set a case to <code>TEAM_ONLY</code> if no case team has been assigned.</p></div></td></tr></tbody></table>

</details>

### Important considerations

Before restricting access or assigning teams, keep the following rules in mind:

* **Permissions required:** To change the access settings of a case, you must have the **Restrict Case Access** permission under **Cases & Issues**.
* **Team management:** When case access is restricted to **Team Only**, only assigned team members have permission to add new team members to the case. For more information see [Overview of case teams and roles](/cortex-cloud-runtime-security/cases-and-issues/overview-of-cases/overview-of-case-teams-and-roles.md).
* **Automatic reversion:** If a case has no assigned team members, the scope automatically reverts to **Case Scope**.
* **Audit trail:** Any changes made to the case assignee or the case team are permanently recorded in the **Case Timeline**.


---

# 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/cortex-cloud-runtime-security/cases-and-issues/analyze-and-resolve-cases/additional-case-actions/assign-a-case-team-and-restrict-access.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.