Value Lists
A value list is a named, ordered set of choices: statuses, priorities, categories, referral sources. Any extension field of type List picks one by name, and every field that uses it offers exactly the options you define here.
The payoff is that there is one place to change them. Edit a list, and every field using it offers the new options immediately — no field-by-field editing, no two fields drifting apart.
Where to find it
| Screen | Where it lives | What you need |
|---|---|---|
Lists — /admin/lists | Settings → Data model → Lists | Permission to read extensions; creating and editing needs the manage permission |
The catalogue
The table has four columns: List (its name and key, with a system badge on a list the system ships), Items (every item's label, in order, coloured when the item has a colour), Origin and Status (Active or Disabled). The Edit, Disable or Enable, and Delete buttons sit at the end of each row.
Origin is either Global (shared by every space) or This space. A space list shadows the global one with the same key: define a space list called priority and this space uses yours while every other space keeps the shared one.
What an item holds
Press + New list, or Edit on a row. A list has a Name people read and a Key (technical name) — the name a field refers to. The key is filled in from the name as you type it; once the list exists it cannot be changed. Then the items, in display order:
| Field | What it is for |
|---|---|
| Label | what people read in the dropdown |
| value | what is actually stored on the record — filled in from the label until you type your own |
| Rank | a whole number; higher is more important. Used wherever the platform ranks the items |
| Colour | picked with the colour button and painted on the item wherever it is shown as a chip; No colour (✕ beside it) takes it away |
Rank and colour are both optional. + Add item adds a line, the ↑ and ↓ buttons move a line, and ✕ at the end removes it (a list always keeps at least one item).
Disabling a list
Disable is soft and reversible, and you are asked to confirm first. A disabled list offers no options to any field — nobody can pick from it. Because of that, the server refuses to disable a list that a live field still uses, with the same refusal as a delete (see below). Disabling a Global list turns it off for this space only; every other space keeps it. The editor shows a prominent banner while you are in a disabled list, and saving a disabled list keeps it disabled; you turn it back on with Enable in the list view.
Deleting a list, and the guard that stops you
Only a This space list has a Delete button; a global list is never deleted here, only disabled for this space. Deleting is also soft, and you are asked to confirm first: the list disappears from this space, and if a global list shares its key, that one resurfaces in its place. You can undo it by re-creating the key.
Before a delete or a disable, the server checks who is still using the list. If a live field refers to it, the change is refused, and the refusal, shown above the table, names every field that still uses it in plain language. Clear those fields first, or point them at another list, then try again; Dismiss closes the message.