> ## Documentation Index
> Fetch the complete documentation index at: https://docs.arcuserp.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Tags Settings
> Use Tags settings to manage system and custom labels that help operators identify important records, route work, and block unsafe actions when a tag is actionable.
Tags can be informational or actionable. Informational tags help users notice
something. Actionable tags can affect workflow behavior, such as blocking
fulfillment or blocking new orders.
## Open Tags Settings
1. Open **Settings**.
2. Choose **Entity Settings**.
3. Open the **System** group.
4. Choose **Tags**.
## System Tags
System tags are seeded by Arcus. They can be used by workflows that need a standard signal.
System tags:
* Cannot be deleted.
* Can have editable display details such as color, description, or sort order when allowed.
* Can have locked action behavior.
* Should be reviewed before the team creates duplicate custom tags.
Use system tags when the meaning matches the workflow. Create a custom tag only when the business needs a local label.
## Custom Tags
Custom tags are created by the entity. Use them for local routing, internal review, customer handling notes, package handling, or operational exceptions.
When creating a custom tag:
1. Use a specific name.
2. Choose a clear color.
3. Write a description that tells operators when to use it.
4. Choose where it applies.
5. Decide whether it is informational or actionable.
6. Save and test the tag on a safe record before using it in production.
## Applies To Scope
The scope decides where users can attach the tag.
| Scope | Typical use |
| ------- | ------------------------------------------------------------------ |
| Order | Payment holds, address review, call before ship, special handling. |
| Account | Credit hold, tax review, VIP, do not sell, billing review. |
| Product | Discontinued, special order, hazardous handling, serial required. |
| Return | Needs inspection, manager review, vendor claim, damaged. |
| Package | Fragile, freight review, signature needed, do not ship yet. |
Keep scopes narrow. A package-only tag should not appear on accounts unless users need it there.
## Actionable Tags
Actionable tags are read by supported workflows. Current tag behavior can include enforced actions such as blocking fulfillment or blocking new orders. Some action options may be scaffolded for future use and should not be treated as enforced until the workflow confirms it.
**Test actionable tags before relying on them**
If a tag is meant to block work, test it on a safe sandbox record and confirm the
actual order, account, package, or return workflow blocks the action as expected.
Use actionable tags for decisions, not decoration. Good examples:
* `Hold for billing`
* `Do not ship until address confirmed`
* `Block new orders`
* `Manager review required`
* `Call before shipping`
Avoid vague names such as `Important`, `Needs review`, or `Special` unless the team has a written process for what they mean.
## Editing And Deactivation
Use edit when the tag meaning stays the same but the label, description, color, scope, or sort order needs cleanup.
Use deactivation when the tag should stop being used for new records but should remain on historical records.
Avoid deleting custom tags that have been used heavily. If deletion is available, confirm whether removing the tag from attached records is acceptable.
## Recommended Setup
1. Review system tags first.
2. List the decisions operators actually need to make.
3. Create only the tags needed for those decisions.
4. Scope each tag to the record types where it is useful.
5. Use actionable behavior only when the workflow should truly block or route work.
6. Test each actionable tag.
7. Review tags quarterly and deactivate stale ones.
## Common Blocks
* **Tag does not appear on a record**: confirm the tag scope includes that record type and the tag is active.
* **Tag blocks work unexpectedly**: remove the tag from the record or edit the action behavior if the catalog is wrong.
* **System tag cannot be deleted**: system tags are protected because workflows may depend on them.
* **Users created duplicate tags**: deactivate the weaker duplicate and standardize on one label.
* **Action does not fire**: confirm the action is enforced by the workflow, not just listed as a scaffolded option.
* **Tag meaning is unclear**: update the description or rename the tag before it spreads.
## Related Articles
Understand safe order changes, holds, cancellation, and workflow state.
Manage account status, billing defaults, customer handling, and account-level blocks.
See how package and order signals affect packing and shipping work.
Review printing, modules, and tags together.