> For the complete documentation index, see [llms.txt](https://docs.yourv.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yourv.id/content-id/manage-assets/categorize-assets-custom-labels.md).

# Categorize Assets (Custom Labels)

You can use Custom Labels to categorize your assets. 

Custom Labels are used for our [Custom Allowlist](/content-id/manage-claims/exempt-channels-from-claims-custom-allowlist.md), to filter your assets, and are displayed in our royalty reports.

### Common Use Cases

You can use Custom Labels for any purpose that requires categorizing your assets. See our guide on [naming conventions](/content-id/manage-assets/categorize-assets-custom-labels/recommended-custom-label-naming-conventions.md) for more details.

### Auto-Generated Custom Labels

You can see all Custom Labels when clicking on any asset's detail view under "Metadata". Every asset has auto-generated labels that start with an underscore ("\_"): 

* All of your assets contain a "*\_licensor\_\[your ID]*" label. 
* Sound recording assets have one "*\_artist\_\[artist name]*" label for each artist and one "*\_track\_\[artist name\&artist name&...]\_\[track title]*" label per asset. 
* If the asset was created from a [channel linked to out MCN](/content-id/extras/link-your-youtube-channel-to-our-mcn.md), it will have a "*\_channel\_\[channel id]*" label.

### Add / Remove Custom Labels

To edit your Custom Asset Labels, click the "Edit" button in the top right of the Asset detail page (only visible on a large screen, not a phone). Add as many labels as you want (press "Enter" to add a new label), and click "Save" on the top right to save the labels.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.yourv.id/content-id/manage-assets/categorize-assets-custom-labels.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.