This guide walks through creating a flag in Settings > Flagging and managing it afterward by renaming or deleting it. Flags created here become the master list for your tenant and are available to apply to documents through Transformation Rules, Rejection Rules, and Instruction Builds.
Prerequisites
Flagging write permission (Admin or Manager role by default)
The
Flaggingfeature enabled for your tenant
Steps
Create a Flag
Navigate to Settings > Flagging. This page is the master list of all flags in your tenant.
Click + Add New.
Enter the flag name, following the naming rules: no spaces, a maximum of 24 characters, and case-sensitive (so "HighValue" and "highvalue" are different flags).
The flag is added to the master list and becomes available to Transformation Rules, Rejection Rules, and Instruction Builds.
Rename or Delete a Flag
On the Flagging page, locate the flag in the list. Each flag shows usage counters for the Transformation Rules, Rejection Rules, and Instructions that reference it.
To rename, open the flag's edit modal, update the name, and click Update.
To delete, use the delete action on the flag. Deletes are soft, so history is preserved.
If the flag is currently used by any rule or instruction, the edit modal opens with the Update button disabled and a red warning, and deletion is blocked. Remove the references first; click a usage counter to navigate to them.
Expected Outcome
The new flag appears in the master list on the Flagging settings page and is available to apply to documents through Transformation Rules, Rejection Rules, and Instruction Builds. Renamed or deleted flags update across the system, and because deletes are soft, flag history is preserved.
Common Issues
Issue | Resolution |
Flag name rejected | Remove any spaces and keep the name within 24 characters; remember that names are case-sensitive |
Cannot edit or delete a flag | The flag is in use by a rule or instruction, so the Update button is disabled and delete is blocked. Remove the references first; click a usage counter to find them |
Flagging page not visible, or no option to add | The |
Notes
Flag names are case-sensitive, so "HighValue" and "highvalue" are treated as separate flags. Pick a naming convention and apply it consistently to avoid accidental duplicates.
A flag must exist in this master list before it can be referenced anywhere; instruction-build saves are blocked if they reference a flag that does not exist here.
Deletes are soft, so flag history is preserved for auditability.
Create, rename, and delete actions are recorded in the Settings activity log.
