> From the [Strife user guide](https://strife.app/docs/user-guide/content-list-and-filter/labels). Every page is listed in [llms.txt](https://strife.app/docs/llms.txt).

# Labels

Tag pages with labels to find and filter them, group labels into submenus, and what administrators set up in the team's settings.

Labels tag your pages so you can find them again. Add labels when you compose a page, or later under **Properties** in the [editor panel](https://strife.app/docs/user-guide/getting-the-basics/editor-panel.md): click **Add label** and tick the labels you want. In the content list, you can then [filter](https://strife.app/docs/user-guide/content-list-and-filter/filter.md) on one or more labels.

<figure><img src="https://strife.app/docs/assets/label-picker.webp" alt="Properties in the editor panel with the label picker open from Add label: the group Blog opens as a submenu with the labels Press release, Engineering, Changelog and Advent, each with a checkbox and a colour."><figcaption><p>Picking labels, with a label group as a submenu</p></figcaption></figure>

Labels are shared by all languages of a page. On a team with more than one language you change them in the default language: in a translation, the Labels field is locked, like the page's other shared fields.

### Managing labels

Administrators create, rename and delete labels in the team's settings, under **Labels**. There they also choose where each label can be used: on content, in the media library, or both. Labels for media let you filter the media library too (see [Find, sort and filter media](https://strife.app/docs/user-guide/media-repository/sorting-media-library.md)).

### Label groups

When a team has many labels, an administrator can organize them in **label groups**, for example a "Categories" group for the labels that say what a page is about, separate from labels used for your workflow. A label belongs to at most one group, and groups are optional: labels without a group work as before.

Groups are managed in the same place as labels, with **Create Group**. With groups in place, the label picker in the editor panel shows each group as a submenu, and the labels without a group on their own.

A few things are always safe:

* **Renaming a group** only changes its name.
* **Moving a label into a group** applies everywhere the label is already used.
* **Deleting a group** keeps its labels: they lose their group, and stay on every page that has them.

### A label field for one group

Besides **Labels**, a template can have label fields of its own, and a developer can limit such a field to one label group: a **Level** field, say, that takes only the labels in a "Level" group. That field's picker then shows only the group's labels, in one list without submenus. Labels the page already has in the field from other groups stay, and you can remove them, but you can't add a label from outside the group.

If the field's group no longer exists, the field offers no labels. In the new interface, its picker says that the field's label group is missing. Tell the developer who set up the template.

To limit a field, the developer needs the group's ID. An administrator copies it in the team's settings under **Labels**, with the copy button on the group's row. In the new interface, open the group's menu and choose **Copy ID**.
