> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/administration/settings/smart-tags.md).

# Automatically label jobs with Automatic Tags

> **Where to find it:** Settings → Data & Integrations → Automatic Tags

Automatic Tags help your team spot jobs with work waiting in specific task folders. A tag appears when a job has at least one open task in any of its selected folders. Once the last matching task is completed, moved, deleted, or unlinked, the tag disappears. Reopening or adding a matching task brings it back.

## Create or change a tag

1. Open **Automatic Tags** and select **Add tag**.
2. Enter a unique name and select one or more task folders.
3. Leave **Enabled** selected to show the tag on matching jobs, then select **Save**.

Use the edit action to change a tag's name, folders, or enabled state. Disable a tag to hide it while keeping its rule, or delete it to remove the rule. Folder selections follow the folder when it is renamed. If a folder is removed, edit the tag and choose an available folder.

## Find matching jobs and tasks

On the Jobs list, use the **Automatic Tags** filter to find jobs with any selected tag. Select a tag with the link icon on a job or in the list to see its matching open tasks and open a task for more detail. Tags reflect the tasks you have permission to see. A task linked only to a property does not tag every job at that property.

Related: [Customize your Jobs task folders](https://learn.withessential.com/administration/settings/customize-jobs-task-folders.md) and [The Tasks inbox](https://learn.withessential.com/field-operations/tasks/the-tasks-inbox-folders-status-filters-and-search.md).


---

# 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://learn.withessential.com/administration/settings/smart-tags.md?ask=<question>&goal=<user_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.
