> ## Documentation Index
> Fetch the complete documentation index at: https://docs.serval.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Sensitivity labels

> Restrict who can view sensitive tickets

A sensitivity label is a security classification that you apply to tickets that may contain sensitive information. You can manually apply sensitivity labels to tickets, and you can define ticket filters where Serval will automatically apply these sensitivity labels.

Tickets with a sensitivity label are not generally visible. They are visible to members who are granted access to the sensitivity label, and to participants on the ticket (e.g. assignee, requester).

> [!NOTE]
>
> Sensitivity labels are a narrow security control for tickets that must stay hidden from most of the workspace, such as legal or HR requests. They aren't a way to organize work. To give people a shared list of tickets, use [saved views](https://docs.serval.com/sections/documentation/ticketing/manage-collaborate/filter-sort.md). To route tickets to the people who work them, use [assignment groups](https://docs.serval.com/sections/documentation/ticketing/ticket-configuration/assignment-groups.md). To control what a role can do with tickets, use [roles and permissions](https://docs.serval.com/sections/documentation/platform/permissions.md).

## Example: restrict tickets for one litigation matter

Your legal team works its own tickets: contracts, NDAs, policy questions. One matter is different. Tickets about the Acme lawsuit are under privilege, and only the attorneys on that case should read them, not everyone who helps out on the legal team.

1. Go to **Settings -> Ticketing -> Sensitivity Labels** and click **+ Sensitivity label**.
2. Name the sensitivity label **Litigation - Acme v. Example Corp**.
3. Under **Applies to**, pick **Tickets chosen manually**.
4. Under **People with access**, add the attorneys on the case, then save.
5. Open each ticket about the case and apply the sensitivity label from its **Sensitivity Labels** section, or select the tickets in the list and apply the sensitivity label in bulk.

The attorneys on the case can view those tickets. Everyone else, including the rest of the legal team, can view a labeled ticket only if they're a participant on it, for example as its requester or assignee. When a new ticket about the case comes in, anyone with the **Apply sensitivity labels to tickets** permission can apply the sensitivity label. If the case's tickets share something a filter can match, such as a ticket type, pick **Tickets that match a filter** instead and Serval applies the sensitivity label as tickets come in.

***

## Create a sensitivity label

Managers of a workspace can create sensitivity labels, change their settings, and grant people access to view tickets that have a sensitivity label. Applying a sensitivity label to a ticket and removing a sensitivity label from a ticket is a separate **Apply sensitivity labels to tickets** action: Managers hold **Apply sensitivity labels to tickets** by default, and other roles can be granted the action through a [custom role](https://docs.serval.com/sections/documentation/platform/permissions.md#custom-workspace-roles).

To create a sensitivity label:

1. Go to **Settings -> Ticketing -> Sensitivity Labels**.
2. Click **+ Sensitivity label** in the top right.
3. Give the sensitivity label a name, and optionally a description.
4. Under **Applies to**, select which tickets get the sensitivity label:
   * **Tickets chosen manually**: someone with **Apply sensitivity labels to tickets** (Managers by default) applies the sensitivity label to tickets one at a time or in bulk, from the ticket's **Sensitivity Labels** section or the ticket list.
   * **Tickets that match a filter**: Serval applies the sensitivity label to tickets that match the filter you specify. Conditions can match ticket properties (including your workspace's custom ticket types), the ticket's assignment group (available once the workspace has assignment groups configured), the requester's built-in fields (Department, Job title, Email, Timezone, and Locale), and requester custom fields. Conditions joined by **AND** must all match, and switching a connector to **OR** starts a new set of conditions. A ticket matches the filter when it satisfies any one set.
   * **All tickets in this workspace**: the sensitivity label applies to every ticket in the workspace, including tickets that also have other sensitivity labels.
   * **Catch-all: tickets with no other sensitivity label**: Serval applies the sensitivity label to every ticket that has no other sensitivity label. See [Catch-all sensitivity label](#catch-all-sensitivity-label).
5. Under **People with access**, add the groups and members who can view tickets that have the sensitivity label.

> [!NOTE]
>
> When you save a sensitivity label, Serval rechecks every existing ticket in the workspace against the sensitivity label's filter in the background, so matching tickets get the sensitivity label and tickets that no longer match lose the sensitivity label. New and updated tickets are checked as they change. A sensitivity label that someone applied to a ticket by hand stays until someone removes it.

## Catch-all sensitivity label

By default, a ticket with no sensitivity label is visible to everyone in the workspace. A catch-all sensitivity label restricts that visibility: if enabled, Serval will restrict tickets without any sensitivity label only to the group of people granted access to view catch-all tickets, plus each ticket's participants.

The catch-all never sits alongside another sensitivity label. When another sensitivity label is applied to a ticket, Serval removes the catch-all, and if that sensitivity label is later removed, Serval applies the catch-all again. This is what sets the catch-all apart from **All tickets in this workspace**, which applies to every ticket whether or not the ticket has other sensitivity labels.

Each workspace can have one catch-all sensitivity label. To make a sensitivity label the catch-all, choose **Catch-all: tickets with no other sensitivity label** in the sensitivity label's settings. A catch-all sensitivity label can't also have a filter or apply to all tickets.

> [!WARNING]
>
> Setting a catch-all changes who can view tickets across the whole workspace. Once the catch-all applies, every ticket now has restricted visibility, so people who aren't granted access to a sensitivity label can view only the tickets they requested, are assigned, are subscribed to, or were mentioned in.

As with filter-based sensitivity labels, saving a catch-all rechecks the workspace's existing tickets, and new or updated tickets are checked as they change.

***

## Filter tickets by sensitivity label

On your workspace's ticket list, open **Sensitivity label** and select one or more sensitivity labels. The list shows tickets that have any selected sensitivity label and that you have access to. Select a sensitivity label again to remove that sensitivity label from the selection, or select **All tickets** to clear the selection. Your selection stays in the page URL so you can reload or share it.

A view saved to a sensitivity label always shows tickets with that sensitivity label, so its sensitivity-label selector is locked. If you manage a selected sensitivity label but aren't granted access to view that sensitivity label, you see who has access before the ticket list. Choose **Grant myself access to view** for each selected sensitivity label you can't view to see the combined results, or choose **Back to all tickets** to clear the selection.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.