> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/access-control/configuration/add-notes-and-tags-to-doors-and-devices.md).
# Add Notes and Tags to Doors and Devices
Keep important details with your doors and devices, and organize them so you can find what you need fast.
## Before you begin
Notes and tags help you keep your access control system organized. Use **notes** to capture installation or operational details about a door or device that you don't want to lose, such as wiring details, hardware quirks, or maintenance history. Use **tags** to label doors and devices with shared attributes, like `lobby`, `fire-exit`, or `needs-maintenance`, so you can quickly filter for the right doors or devices to find them or to perform bulk actions.
You can add notes and tags to any door, elevator, access controller, aux input, or aux output.
{% hint style="info" %}
#### Tags are shared across your entire organization, not just one site. A tag created at one site can be used at any other site, and renaming or deleting a tag in the tag manager changes it everywhere it's used.
{% endhint %}
## Add notes and tags
{% hint style="warning" %}
You need Access Site Admin permissions to edit notes and tags.
{% endhint %}
#### Add to a door
1. In Verkada Command, go to **All Products > Access**.
2. Select **Doors** and click the door you want to update.
3. In the **Notes** field, enter any details you want to keep with the door.
4. In the **Tags** field, select an existing tag or type a new one and press **Enter** to create it.
#### Add to a device
1. In Verkada Command, go to **All Products > Devices**.
2. Click the access controller you want to update.
3. In the **Notes** field, enter any details you want to keep with the device.
4. In the **Tags** field, select an existing tag or type a new one and press **Enter** to create it.
{% hint style="info" %}
#### **How tags are removed**
Tags only exist while they're in use. When a tag is no longer applied to any door or device, it's automatically deleted from the system. For example, if you create a new tag on a door's page and then remove it from that door, the tag is deleted entirely.
{% endhint %}
#### **Limits**
* Notes can be up to 1,000 characters.
* Tags can be up to 50 characters.
* A single door or device can have up to 50 tags.
## Search and filter with notes and tags
You can use notes and tags to search and filter your doors and devices lists.
#### **Filter by notes**
* **Has notes:** Shows any door or device with text in its notes field.
* **Contains:** Shows doors or devices whose notes include the specific text you enter.
#### **Filter by tags**
* **Any of:** Shows doors or devices that have at least one of the selected tags.
* **All of:** Shows only doors or devices that have every selected tag.
## Manage tags
{% hint style="warning" %}
You need Access System Admin permissions to use the tag manager.
{% endhint %}
The tag manager shows every tag in your organization, along with how many doors and devices use each one.
#### **Open the tag manager**
1. In Verkada Command, go to **All Products > Access**.
2. Select **Access Settings > Tag Manager**.
#### **Use the tag manager**
From the tag manager, you can:
* **Rename a tag:** The new name is applied everywhere the tag is used.
* **Delete a tag:** This removes the tag from all doors and devices.
* **View tagged doors and devices:** Click the number of doors or devices next to a tag to open the doors or devices list, filtered by that tag.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.verkada.com/access-control/configuration/add-notes-and-tags-to-doors-and-devices.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
