> ## Documentation Index > Fetch the complete documentation index at: https://docs.qlero.io/llms.txt > Use this file to discover all available pages before exploring further. # Using Tags > Label works with tags so you can filter them, update them in bulk and target CWR deliveries. Tags are coloured labels that you define once for your record company and attach to records. They let you group works the way your team thinks about them, such as a priority list, a sub-catalogue, a signing year or a clean-up batch, without changing anything about the works themselves. Once a work is tagged, you can filter on the tag, change tags on many works at once and limit a CWR delivery to tagged works. Tags never affect royalty calculations or statements. They are purely a way to organise and select records. Today you can tag works, and CWR deliveries and delivery plans can select works by tag. Other record types will follow, and this article grows with them. > [!NOTE] > > Tags are included in every plan. You need write access to Repertoire to create, edit or delete tags and to tag works. Using tags in a CWR delivery or delivery plan needs write access to Deliveries. Because tags currently apply to works, the Tags page only appears for record companies with publishing. ## How tags work A tag belongs to one record company and has a name, a colour and an optional description. Names are unique within the record company. A work can carry any number of tags, and a tag can sit on any number of works. Keep names short and specific enough that the meaning is obvious in a list, such as **Priority**, **Catalogue 2019** or **Needs ISWC**. Use the description to record what the tag is for and who maintains it. ## Create and manage tags Tags are managed in one place, so everyone in the record company works from the same list. **1. Open the Tags page** Open the record company, go to **Configurations** and select **Tags**. The page lists every tag with its colour and description, and you can search by name or description. **2. Create a tag** Select **Create**. Enter a **Name**, pick a colour from the palette or set a custom colour, and optionally add a **Description** that explains what the tag is used for. Save the tag. **3. Edit a tag** Open the row menu of a tag and select **Edit**. Renaming or recolouring a tag updates it everywhere it is used; you do not need to re-tag anything. > [!TIP] > > You can also create a tag while tagging a work. Type a new name in the tag picker and select **Create tag**. The tag is added to the work and appears on the Tags page like any other. ### Delete a tag > [!WARNING] > > Deleting a tag removes it from every work it is on. This cannot be undone. A tag that is used by a CWR delivery plan cannot be deleted; remove it from the plan first. Open the row menu of the tag, select **Delete** and confirm. Creating, editing and deleting tags is recorded in the [Audit log](https://docs.qlero.io/labels/monitoring/audit-log-and-emails.md). ## Tag works ### Tag one work Open the work from **Repertoire › Works**. Its tags are shown under the title. Select **Add tag** (or **Tag** when the work already has tags), then search for and select a tag. Remove a tag by selecting the cross on its chip. Changes are saved immediately. ### Tag many works at once **1. Select the works** In **Repertoire › Works**, filter the list if needed and select the works to change. You can also use **Select all** to include every work that matches the current filters. **2. Open Edit Tags** Select **Edit Tags** in the bulk actions bar. **3. Choose what to add and remove** Pick the tags to add under **Add tags** and the tags to remove under **Remove tags**. Tags the works already have, and tags you do not pick, are left as they are. Confirm to apply the change. ### Filter works by tag Use the **Tags** filter above the works list and pick one or more tags. The list shows works that carry any of the selected tags. Combine it with the other filters, for example to find untagged priority candidates by contract, and tag the result in bulk. ## Use tags in CWR deliveries A CWR delivery sends works to a delivery partner. Tags let you narrow which works a run includes, on top of the **Work selection** setting that decides whether a run sends every work or only works that are new or updated since the last delivery. When you create a run under **Deliveries**, or create or edit a delivery plan under **Deliveries › Delivery plans**, two fields control this: | Field | Effect | | - | - | | **Only works tagged** | Leave empty to include works regardless of their tags. Otherwise, only works with any of the selected tags are included. | | **Skip works tagged** | Works with any of the selected tags are excluded, even if they match **Only works tagged**. | A tag cannot be both included and excluded in the same selection. For example, tag the works you want to register first with **Priority** and the works that are not ready with **On hold**. A delivery plan with **Only works tagged** set to **Priority** and **Skip works tagged** set to **On hold** delivers the priority works, minus any that are also on hold, on every run. When a work is ready, remove **On hold** and the next run picks it up. Each run records the tag filters it used, and the run page shows them as **Only works tagged** and **Skipped works tagged**, so you can see later why a work was or was not included. ## Where tags apply today | Area | What you can do | | - | - | | Works | Tag single works, tag works in bulk and filter the works list by tag. | | CWR deliveries and delivery plans | Include or exclude works by tag when a run is created or scheduled. | Support for other record types will be added over time, and this article is updated as it arrives. ## Next steps Decide on a small set of tags with your team before tagging in bulk, then use the **Tags** filter in Repertoire to check the result. * [Using filters in Repertoire](https://docs.qlero.io/labels/repertoire/using-filters.md) * [Setting up your configurations](https://docs.qlero.io/labels/getting-started/configurations/customizing-your-types-and-groups.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.