> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/documentation/settings/tags-in-rewst.md).
# Tags
## What are tags in Rewst?
*Tags* let you earmark the automations that you care about most, for quick searching and access. Tags can be added by users with the [permission levels](https://docs.rewst.help/documentation/user-management/roles) of member, staff, and admin.
## Add tags to workflows
{% hint style="success" %}
The below directions will walk you through how to use tags for workflows, as an example. These same directions will work for how to add tags to forms, scripts, and templates, all found under Automations in the left side menu of Rewst. Once a tag is created, it can be applied to any automation type.
{% endhint %}
1. Navigate to **Automations** **>** **Workflows** in Rewst.
2. Click **⋮** to the right of your relevant workflow.
3. Select **Edit Attributes**.\
4. Open the **Tags** drop down in the **Edit Workflow Attributes** dialog to choose an existing tag from the list. Alternatively, begin typing in the drop down field and select the box to **Create tag**. This action will also add that new tag to your drop-down list for all future tag selections.\
\
5. Click **Submit** when finished tagging. If successful, you’ll see a green **Workflow saved!** confirmation pop up at the top of your screen. Now, tags for that workflow will appear in the tag column of your workflows page.
## Tag workflows in bulk
{% hint style="warning" %}
Bulk editing workflow tags will overwrite all previous tags currently set for those selected workflows.
{% endhint %}
1. Check the checkbox to the left of each desired workflow in your workflows page.
2. Click .
3. Follow steps as usual to edit or create new tags for your selected workflows. Note that if your multiple selections will result in overriding existing tags, the dialog will display a warning message.\
4. Click **Submit** when finished tagging. If successful, you’ll see a green Workflow saved! confirmation pop up at the top of your screen. Now, tags for that workflow will appear in the tag column of your workflows page.
## Filter by tag
1. Open the **Tags** drop-down menu under the header of your workflows page. Click **Include** to add one or more tags to filter criterial for your total tag list.\
\
2. Your returned list will filter results to only display workflows tagged with your chosen tag.
## Color code tags
For quick visual reference of categories, tags can be color coded.
1. Navigate to **Settings > Tags** in the left side menu.
2. Here you can edit individual existing tags via the pencil icon, delete existing tags via the trashcan icon, or add new tags via the **+** sign to the top right of the **Manage Tags** screen.
## Example use cases for tags
* Give better visual indicators for your long list of automations, not just text. For example, you could choose to make all Powershell workflows red.
* Tags can also be used to mark associations between pieces of a larger workflow. Consider a parent workflow which contains several child workflows and a form. Each piece of that parent workflow could be tagged with one tag. Then, you’d select that tag to isolate everything for just that one workflow, regardless of the pieces you used to create it.
* Try creating tags for the development status of a workflow: In Development, In Testing, In Production, etc. If your MSP has multiple builders on staff, different individuals will know not to edit or experiment on an In Production workflow, which could cause problems for their team.
* Try making all internal MSP operations a different color than the client facing/ service desk automations.
## Workflow design to optimize tags
Designing your workflow to intentionally optimize the use of tags sets you up for better organization as you grow your number of automations and assets in Rewst. Names of workflows, actions, and variables should tell a story of what's happening and reduce the need for comments to explain what your reasoning. Learn more about our best practices for naming conventions when designing workflows [here](/documentation/automations/workflows/best-practices-for-designing-workflows.md).
Tags alongside a naming convention provide a good way of organizing workflows, especially when Crates have been unpacked and there are several pages of workflows in your total list.
* Create three standard tags — Development, Testing, and Production — and apply one to every workflow. Builders can see at a glance what's safe to edit and what's live. This is especially important when multiple people are building in the same organization: a workflow tagged Production signals that changes could break something for a real customer.
* Tag all the pieces of a complex build with a shared tag so you can isolate them from the rest of your workflow list. For example, an automated ticket dispatching workflow might include subworkflows for checking tech availability, matching skillsets, and updating the ticket. Tagging all of them Ticket Dispatching lets you pull the full set with one filter. This is useful when you're debugging, updating, or handing off to someone else.
* Add tags for the integrations a workflow relies on — for example, O365, Huntress, or Autotask. When an integration changes or has an outage, you can quickly find every workflow that touches it.
* If you're building out a larger initiative like a client portal, QBR automation, or billing reconciliation, tag every workflow involved. This keeps project-related builds grouped even as your overall list grows.
* Use color to add a visual layer on top of your tags. A useful approach: give internal MSP operations workflows one color and client-facing or service desk automations another, so you can orient yourself faster when scrolling a long list.
---
# 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:
```
GET https://docs.rewst.help/documentation/settings/tags-in-rewst.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.