Labels
Labels are reusable global tags for classifying participants and resolve requests.
Unlike metadata, labels are short controlled values intended for filtering, matching, and reporting. They are not namespaced by project or owner.
What Labels Do
Section titled “What Labels Do”Labels are used to:
- Group participants by business capability, function, region, risk area, or approval type
- Help the resolver select candidate participants from a controlled vocabulary
- Filter participants and resolve requests in the platform
- Power Dashboard top category reporting
- Expose stable categories through REST and MCP read scopes
Label Shape
Section titled “Label Shape”A label has:
- ID
- Name
- Color
- Created-by identity
- Created and updated timestamps
Names are unique case-insensitively. Color is stored as a hex color and is used for badges in the platform.
Label Access
Section titled “Label Access”Active authenticated users can read the global label catalog.
Admins and effective project owners can create and update labels. Non-admin project owners can delete only labels they created, and only when every usage is in projects they own.
Platform Screen
Section titled “Platform Screen”The Labels screen at /labels shows:
- Label badge
- Participant count
- Resolve request count
- Updated timestamp
Participant and resolve request counts link to filtered views. Admins and project owners can create, edit, and delete labels from the screen.
Relationship to Participants and Resolve
Section titled “Relationship to Participants and Resolve”Attach labels to participants when the label helps describe the work that participant can handle. The resolver uses available labels as a controlled list; it should match exact labels rather than invent new categories.
Resolve requests inherit labels from selected participants so operational views can show category volume and resolution rate.
REST label endpoints are documented in Labels API.