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. To route tickets to the people who work them, use assignment groups. To control what a role can do with tickets, use roles and permissions.
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.- Go to Settings -> Ticketing -> Sensitivity Labels and click + Sensitivity label.
- Name the sensitivity label Litigation - Acme v. Example Corp.
- Under Applies to, pick Tickets chosen manually.
- Under People with access, add the attorneys on the case, then save.
- 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.
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. To create a sensitivity label:- Go to Settings -> Ticketing -> Sensitivity Labels.
- Click + Sensitivity label in the top right.
- Give the sensitivity label a name, and optionally a description.
- 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.
- Under People with access, add the groups and members who can view tickets that have the sensitivity label.
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.

