Priority

Fork to edit…

priority ◎ Common list Read-only for you front_sl_01jf8k2m3n4p5q6r7s8t9v0w1x

A common list, shared by every organization

FuzeFront provides this list to every organization. You can view it and pick its values in any form, but you can't change it here — a change would affect every organization at once.

To change it for Globex Freight, fork it: your organization gets its own copy with the same key (priority). If you share the fork with everyone in Globex Freight (the default), every form in your organization that uses priority switches to it; a private draft is used only by people you give a role, and everyone else keeps the common list. Values already saved in records keep showing correctly.

Owned by: FuzeFront platform — not your organization
Who can see it: Everyone in every organization. A common list never becomes private again.
Values: 4 active · 1 archived · authored in en, translated into 9 languages
Your access: View and pick. You have no role on this list.

Values Translations

Label (en)	Code	Status	Item id
Low	LOW	active	front_sli_01jf8k2m3n4p5q6r7s8t9v0wa1
Normal	NORMAL	active	front_sli_01jf8k2m3n4p5q6r7s8t9v0wa2
High	HIGH	active	front_sli_01jf8k2m3n4p5q6r7s8t9v0wa3
Urgent	URGENT	active	front_sli_01jf8k2m3n4p5q6r7s8t9v0wa4
Critical (legacy)	CRITICAL	archived	front_sli_01jf8k2m3n4p5q6r7s8t9v0wa5

5 values · read-only Changes happen in your organization's fork

Why the Fork CTA is shown before anyone tries to edit

The UI cannot know in advance whether you may create lists — there is no capability probe for SelectionListCatalog:create, and a viewer does not hold it. So the CTA renders whenever visibility = platform, editable = false and the effective list for this key is this list. The service decides: a viewer who presses it gets the 403 explanation in the dialog (fork results), and the CTA is then replaced by that explanation for the rest of the session. The CTA is not rendered when editable is absent (a 4.0.0 service), when the list is not platform, or when your organization already has its own version of the key (see states).

Test hooks: [data-frame='02-common-detail'] · [data-visibility='platform'] · [data-badge='common'] · [data-editable='false'] · [data-readonly-notice='platform'] · [data-owner-org='platform'] · [data-panel='value-table'][data-readonly='true'] · [data-action='fork-to-edit'] · [data-tab='translations'] · [data-item='front_sli_01jf8k2m3n4p5q6r7s8t9v0wa1'] · [data-archived='true']
Contract: GET /v1/selection-lists/{listId} (shared read: visibility, editable, organization_id = platform org) · GET /v1/selection-lists/{listId}/items?status=all · GET /v1/selection-lists?key=priority&include_shared=true&limit=1 (is this list the effective one for the key?). GET …/access is never called for editable: false.
Tokens only — no raw hex, spacing or type outside tokens.css / frame.css.