Tags
Overview
Tags are labels for free categorisation. Unlike a custom field, which carries exactly one value per record, any number of tags can be attached to a record.
The rule of thumb for choosing: what every record has and what gets reported on is a field. What only some have, and what emerges in daily practice, is a tag.
Tags are global — they are maintained centrally here rather than invented in passing while capturing data. That prevents the sprawl of "Important", "important" and "IMPORTANT" that makes any evaluation worthless.
Core tasks
Create a tag. New tag requires a name and optionally a colour. The colour is not decoration: in daily use it is what makes a tag recognisable in a long list at all.
Set the scope. The scope limits where a tag is offered — General, Customer or Task. Left empty, the tag is usable everywhere. That is the default and usually the right one; setting a scope only pays off once the selection gets unwieldy.
Fields in detail
| Field | Required | Values / format | What it does |
|---|---|---|---|
Name name | yes | text, max. 100 characters | What the tag is called. It is also the key: a tag is assigned by its name, including from automation and import. |
Colour color | no | colour value, max. 20 characters | Colour of the marker in lists. |
Scope scope | no | text, max. 100 characters | Where the tag is offered — say only on customers or only on tickets. Empty means everywhere. |
A tag is more than a label. It can start a marketing journey and serve as a condition in automations. That is why assigning and removing raise an event each — but only on a genuine change, not on saving the same state again.
Renaming a tag carries all assignments with it; deleting it removes it everywhere. Both are interventions reaching well beyond this page.
Settings & permissions
- No route permission of its own. The page is reachable; creating and changing is checked by the
server.
- Tags apply across brands.
- Filters and search draw on this. Wherever lists filter by tag, this list is the source.
FAQ & troubleshooting
A tag does not appear while capturing data. Check the scope. A tag scoped to Customer is not offered on a task.
We have two nearly identical tags. That happens when tags are created in passing. Merge them by removing the superfluous one — assign the surviving tag to the affected records first.
Field or tag? One value per record plus a reporting need argues for a field; several free attributes for a tag. See Custom fields.
The colour has no effect. Not every list renders tags in colour; where it does, the colour comes from here.