> For the complete documentation index, see [llms.txt](https://help.agencydesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.agencydesk.io/company-settings/general/global-tags.md).

# Global Tags

Create reusable colour-coded tags to organise and label Tasks across all Jobs. Global Tags help teams quickly identify status, type, or priority at a glance.

Global Tags are a simple, colourful way to help your team quickly understand the status or type of work at a glance. They can be used on any Task inside a Job and will also appear in Job Costing and on the Task Slider, helping everyone stay aligned.

### How to create a Global Tag

{% stepper %}
{% step %}
**Go to Settings**

Navigate to Settings > General > Global Tags
{% endstep %}

{% step %}
**Add a New Tag**

Click the **+ New Tag** button on the right-hand side.
{% endstep %}

{% step %}
**Name Your Tag**

Type in a clear label—something your team will easily recognise (e.g., 1st Draft, Bug, Internal).
{% endstep %}

{% step %}
**Choose a Colour**

Select a colour that stands out or fits into your tagging system.
{% endstep %}

{% step %}
**Save Your Tag**

Click **Save**, and your new Global Tag is ready to use!
{% endstep %}
{% endstepper %}

### Where Global Tags appear

Once created, Global Tags can be applied at a Task level in any Job. When used, they will show up:

* On the Task list inside a Job
* In Job Costing, helping with recon and reporting
* On the Task Slider in the Resource Planner, so team members instantly see context while planning or working

### Suggested Default Global Tag Sets for Agencies

If you’re just getting started with Global Tags, here are some tried-and-tested tag sets many agencies use to keep work organised and easy to follow.

You can use these as-is or as inspiration to build your own tagging system that fits your team’s workflow.

**1. Production & Review Workflow Tags**

*Perfect for creative teams, designers, developers, writers, and editors.*

* 1st Draft
* 2nd Draft
* Final Draft
* In Review
* Approved
* Complete

**2. Issue & QA Tags**

*Ideal for digital teams, development teams, and ongoing retainer work.*

* Bug
* Fix Required
* Blocked
* Ready for QA
* QA Passed

**3. Internal Workflow Tags**

*Helpful for tagging internal tasks that shouldn’t appear in client-facing reports.*

* Internal
* Admin
* Training
* Non-Billable

**4. Priority Tags**

*Great for quickly communicating urgency.*

* High Priority
* Medium Priority
* Low Priority
* Urgent

**5. Client Behaviour / Workflow Indicators**

*Useful for Account Managers working with long-term or retainer clients.*

* Client Delay
* Waiting on Client
* Feedback Received

**6. Department or Discipline Tags**

*Helpful for categorising Tasks by type of work.*

* Design
* Development
* Copywriting
* SEO
* Finance
* Production


---

# 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.agencydesk.io/company-settings/general/global-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.