Tags are how you organize resources across SendOps. A tag is a small, colored label you attach to a resource, and the same tags double as **folders**: a tag whose name contains a `/` behaves like a nested folder, so `Marketing/Newsletters` puts a resource in a **Newsletters** folder under **Marketing**. You define your tags once, then apply them anywhere.

## Managing tags

The tag vocabulary lives under **Workspace › Tags**. Each tag has:

- **Name** — the display name. Include one or more `/` characters to nest it as a folder (for example `Marketing/Newsletters`).
- **Key** — a short, org-unique slug shown alongside the name.
- **Color** — an optional accent color picked from a fixed palette (or none).
- **Usage** — a count of how many resources currently carry the tag.

With the **New tag** button you create tags, and each row has a menu to **Edit** (rename, recolor, describe) or **Delete** one. Renaming a parent moves its whole subtree with it — rename `Marketing` and everything under `Marketing/…` follows. Deleting a tag removes it from every resource using it, but never deletes the resources themselves.


  Anyone on your team can see tags, but **creating, editing, and deleting them requires manage-tags access** — granted to the Owner, Org Admin, Developer, and Marketer roles. Without it, the management controls are hidden and the view is read-only.


## Tags as folders

Because a `/` in a tag name marks a nesting level, your tags form a folder tree. On the resource list views that support it, this tree appears as a **folder rail** down the side:

- **All** — a pseudo-folder showing every resource, tagged or not.
- Your **tag folders**, nested and collapsible, each with a count of the resources beneath it (the folder itself plus everything nested under it).
- **Untagged** — a pseudo-folder collecting resources that carry no tag at all.

Selecting a folder filters the list to the resources under it. It's the same idea as Gmail labels: one flat set of tags, presented as a hierarchy you can browse.

## Applying tags to a resource

You add and remove tags right where the resource lives — on its row in the list view or on its detail page. A small tag field shows the resource's current tags as chips; click **Add** to open a type-ahead picker where you can **filter** to an existing tag or **create a new one** on the spot without leaving the page. Remove a tag by clearing its chip.

## Where tags apply

Tags (and therefore folders) work across these resources:

- [Lists](/audience/lists)
- [Segments](/audience/segments)
- [Templates](/templates/template-management)
- Workflows
- Assets
- Broadcasts

Because it's one shared vocabulary, the same tag — say `Q3-Launch` — can group a List, a Template, and a Broadcast together, and each type's list view can be filtered down to that folder.