Tags Settings

Use the Tags page to keep the catalog of labels your team attaches to orders, accounts, products, returns, packages, and bills of materials. Come here to add a custom tag, clean up a tag’s name, color, or description, hide a tag you no longer use, or make a custom tag actionable so it blocks fulfillment or new orders.

​

Before You Start

• You need the settings.view permission to open the page.
• You need settings.edit to create, edit, or delete a tag. The page shows Add custom tag and the edit and delete buttons to everyone who can open it, but without settings.edit the save or delete is refused when you submit it.
• Attaching a tag to a record happens on that record, not here, and needs the record’s own edit permission: orders.edit for an order, accounts.edit for an account, products.edit for a product, returns.edit for a return, fulfillment.ship for a package, and manufacturing.edit for a bill of materials.

​

Open Tags Settings

1. In the deck, open Settings.
2. Under System, choose Tags.

The breadcrumb reads Settings > System > Tags. You can also search for Tags in the command palette, and an older bookmark to the Tags page still lands here.

​

The Tag List

The page has two groups:

• System tags: “Seeded per-entity. Cannot be deleted. Actions are locked.”
• Custom tags: “Entity-defined. Fully editable.” When you have none, the group reads “No custom tags yet. Click “Add custom tag” to create one.”

Each row shows the tag’s color dot, its name, the action it performs as an amber badge when the tag is actionable, an Inactive badge when the tag is hidden, the Slug, the record types it Applies to, and the description. Custom tags have an edit button and a delete button; system tags have only the edit button. The list refreshes on its own when someone else creates, edits, or deletes a tag.

​

System Tags

System tags are seeded by Arcus. They can be used by workflows that need a standard signal. System tags:

• Cannot be deleted. Clear Active to hide one instead.
• Can have their name, color, and description edited, and can be marked inactive.
• Have a locked scope and locked action behavior. In the edit dialog, Applies to reads “(locked for system tags)” and the Actionable checkbox is disabled.
• 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. To create a custom tag:

1. Click Add custom tag. The Create custom tag dialog opens.
2. Enter a specific Name.
3. Optionally enter a Slug. Leave it empty and Arcus generates one from the name. The slug keeps only lowercase letters, numbers, and underscores.
4. Choose a Color from the swatches, or pick any color with the color picker.
5. Write a Description that tells operators when to use the tag.
6. Choose at least one record type under Applies to.
7. Decide whether the tag is informational or actionable. To make it actionable, check Actionable, triggers system behavior and choose an action.
8. Leave Active (toggle off to hide without deleting) checked.
9. Click Create tag. The button stays disabled until the tag has a name, at least one scope, and, when Actionable is checked, an action.

Test the tag on a safe record before your team relies on it.

​

Applies To Scope

The scope decides where users can attach the tag. 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. The action list marks which actions are enforced today: When you choose an enforced action, the dialog warns “Enforced end-to-end: applying this tag will block the corresponding operation.” When you choose a scaffold action, it reads “This action is not enforced in every workflow. Test it before relying on it.” Only active tags block work. Marking an actionable tag inactive lifts its block everywhere it is attached. 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

Click the edit button on a row to open the edit dialog, named for the tag. Change what you need and click Save. The slug cannot be changed after the tag is created. Use edit when the tag meaning stays the same but the label, description, color, or scope needs cleanup. Use deactivation when the tag should stop being used but should remain on historical records: clear Active (toggle off to hide without deleting) and save. The row then shows an Inactive badge.

​

Deleting A Custom Tag

1. Click the delete button on a custom tag.
2. The Delete tag? dialog warns that the tag “will be removed from every resource it’s attached to. This cannot be undone.”
3. Click Delete.

Avoid deleting custom tags that have been used heavily. Deactivate them instead when the history matters.

​

Messages You May See

​

What Changes Elsewhere

• Records: an active tag in a record type’s scope can be attached to records of that type. Deleting a tag removes it from every record; deactivating it keeps it on existing records.
• Fulfillment: while an order carries an active Block fulfillment tag, no package on it can be marked fulfilled (shipped), it cannot be packed through Walk-in Pack, and auto-pack skips it. Packing a box and buying a label are not blocked. The block message names the tag and says to remove it to allow fulfillment.
• Orders: an account carrying an active Block new orders tag cannot receive new orders.
• Audit trail: every create, edit, and delete is recorded in the Audit Log with the tag’s name.

​

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 mark the tag inactive if the catalog is wrong.
• System tag cannot be deleted: system tags are protected because workflows may depend on them.
• Save or delete is refused: you need the settings.edit permission.
• Users created duplicate tags: deactivate the weaker duplicate and standardize on one label.
• Action does not fire: confirm the action is marked enforced, not scaffold.
• Tag meaning is unclear: update the description or rename the tag before it spreads.

​

Related Articles