> For the complete documentation index, see [llms.txt](https://docs.dinmo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dinmo.io/workspace-management/tags.md). # Manage tags ## Overview Tags are shared labels that help organize models, segments, and computed fields across your workspace. If you have access to Workspace Settings, you can review and manage the tags available to everyone in the workspace. ## Open the tags page 1. Open **Settings**. 2. Under **Workspace**, select **Tags**.
Tags settings page showing tag names, creation dates, and the number of entities using each tag

Review the tags available in your workspace and see where they are used.

## Review tag usage The Tags page lists every tag available in the workspace. For each tag, you can review its name, creation date, and the number of entities using it. Use the entity count to understand whether a tag is used by models, segments, computed fields, or several object types. ## Edit or delete a tag Open the action menu next to a tag to manage it. You can edit a tag to keep naming consistent across the workspace, or delete a tag that is no longer needed. Before deleting a tag, review its usage to avoid removing a label that is still useful to other teams. --- # 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.dinmo.io/workspace-management/tags.md?ask=&goal= ``` `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.