> For the complete documentation index, see [llms.txt](https://docs.opsnow.io/opsnow-user-guide-v0.2/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opsnow.io/opsnow-user-guide-v0.2/menu/tag-manager/tag-explorer-tab.md).
# Tag Explorer Tab
The Tag Explorer tab displays the status of tags for each resource in a table format. You can review and select resources to apply tags in batches.
1. Use filters to search for resources by Account, Region, Product, Tag Group, or Tag.
2. View the tagging status of all resources:
1. **Properly tagged:** Shows the percentage and number of resources that have the correct tag keys and values.
2. **Not tagged:** Shows the percentage and number of resources that have no tags applied.
3. **Empty values**: Shows the percentage and number of resources with a tag key but no corresponding value.
3. Displays the billing tag application status for all resources. If a required billing tag is not configured, go to ‘Tag Policy(tab)’ to create the necessary billing tag.
1. **Compliant:** Shows the number and percentage of resources that have both the required billing tag keys and values applied.
2. **Not-Compliant:** Shows the number and percentage of resources that are missing required billing tags or have tag keys without corresponding values.
4. Displays the tagging status of resources in a table format. Review the billing tag entries for resources that have no tag key (*\*) or have tag keys without values (*\*).
5. Click the **\[Add Tags]** button to assign tags. You can also select multiple resources from the table to apply tags in batches.
6. Click the **\[Edit Tag Values]** button to update tag values. Batch editing is available by selecting multiple resources from the table.
7. By clicking the **\[Download]** button, you can export the resource tag status table as a file. This allows you to review tagging statuses and details offline.
---
# 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.opsnow.io/opsnow-user-guide-v0.2/menu/tag-manager/tag-explorer-tab.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.
