> For the complete documentation index, see [llms.txt](https://help.aphex.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aphex.co/docs/planner/features/tags.md).

# Tags

{% hint style="info" %}
**Who can use this feature?**

Task Owners, Assignees and Admin users can add Tags to Tasks.

***

All Project Users can create and edit Tags by default. This can be changed to Admins only in the Project Settings.
{% endhint %}

Tags give you a way to label Tasks with anything that matters to your team, from safety and risk, to key priorities, review flags, or anything else. They’re multi-select, fully custom, and can be used to filter views to suit different meetings, roles, or priorities.

## Creating Tags

***

Creating tags lets you build a reusable library of Tags to assign to Tasks.

<figure><img src="/files/bbaMKpfv25L5IZR1o3bi" alt=""><figcaption></figcaption></figure>

**To create a new Tag:**

* Click your Project Title in the top left, then select  `Project Assets`&#x20;
* Select `Tags` from the menu
* Click  <img src="/files/dh1ksUu4JSY3XEMHXWxj" alt="" data-size="line">&#x20;
* Create your custom Tag by entering the name and assign a colour
* The Tag is added to the library of Tag the team can assign to their Tasks

## Assigning Tags to Tasks&#x20;

***

Tags can be added to Tasks to help group and organise work across your plan, they’re a flexible way to highlight key information without changing the structure.

<figure><img src="/files/hbL1WdmHz6XjuYwD5bFZ" alt=""><figcaption></figcaption></figure>

**To assign Tags to Tasks:**

* On the Gantt, open the column picker <img src="/files/lFM5ARreMBKf1sKH8Hvm" alt="" data-size="line"> and toggle <img src="/files/jTh9ws3AqCMfZ3SCPSwI" alt="" data-size="line"> `Tags`
* Click a cell in the column to add a Tag to the Task from the dropdown

See also: <a href="/pages/TnJXd2NNXypVW06spOJM#editing-tasks" class="button secondary">Bulk Edits</a>&#x20;

<details>

<summary>How Tags Work</summary>

* Tags are a multi-select property
* Archived Tags will no longer be available to add to tasks but will still exist on tasks it was assigned to before the resource was archived

</details>

## Filter by Tag

***

Filtering by Tags lets you focus on specific Tasks based on what’s been added to them. It’s a quick way to review and manage work related to a particular Tag across your plan.

<figure><img src="/files/gbeAnVxaIYpkU46FOMBW" alt=""><figcaption></figcaption></figure>

#### To Filter by Tag:

* Click <img src="/files/UnfOWQgX85R7uTuJEjsL" alt="" data-size="line"> then <img src="/files/4EyobaqwpvxEz1FuOXGS" alt="" data-size="line">
* Select `Tag` in the first dropdown
* Select from `Is`, `Is Not`, `Is Empty` or `Is Not Empty` in the second dropdown
* Select your desired Tag in the third dropdown

See also: create & share <a href="/pages/eOvGM0H6kVDgz4BlBkPB" class="button secondary">Views</a>&#x20;

<details>

<summary>Filter Breakdown </summary>

| Filter | Operator                                           | Value                          |
| ------ | -------------------------------------------------- | ------------------------------ |
| Tag    | <p>Is <br>Is Not <br>Is Empty <br>Is Not Empty</p> | <p>Multi-Select</p><p><br></p> |

</details>


---

# 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://help.aphex.co/docs/planner/features/tags.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.
