Set up a dropdown’s options and colours

A Select field is a fixed list of choices — a stage, a priority, a car model. This page covers writing the options, colouring them so a table can be read at a glance, and turning them into an ordered pipeline. About 15 minutes for a stage field.

Before you start

The field’s Type is already Select — see Choose a field type
You have the Table Settings permission
Have your list of options written down. Reordering is easy, but every option you add is one more thing your team has to choose between

Source does not work like this. Its choices are workspace lead sources, not field options — skip to Source is different.

Steps

Choose how people see the choices

Open Database Configuration, click the database’s chip along the top, then click the field’s row to open its editor. Display is the first setting under Type: Dropdown or Inline. Its tooltip is the whole decision: Dropdown — a compact menu; best when there are many options or space is tight. Inline — every option shown as chips at once; best for 2–5 options you want visible at a glance.

The data is identical either way. You are only changing what the person filling the field sees, and both variants wear the same Select pill in the field list.

The four settings above the option list. Each has an info icon with the reasoning behind it

Decide how people pick

Two checkboxes. On a field you have only just switched to Select, Allow multiple selection starts on — turn it off if a contact should hold exactly one value.

Allow multiple selection lets one contact hold several values, shown as several chips. Its tooltip: Let people pick more than one option for this field. Selected values show as multiple chips.
Allow adding new options turns the picker into a search-and-add box, so someone can type a value that is not in your list and add it on the spot. Useful when you cannot predict every answer. Its tooltip also notes that Long lists (10+ options) already become searchable on their own.

Allow multiple selection is greyed out on Status and Source, because those two are core attributes of a contact and hold exactly one value. Allow adding new options is not offered on Source at all.

Write the options

Under the heading Options — with the count in brackets — click the dashed Add option button, then type the label into the row’s box. Repeat for each choice. Drag a row’s grip to reorder.

One row is missing its trash button — that is the option a new contact starts on, and the server will not let it go

Give each option a colour

Click an option’s dot. A small popover opens with ten swatches: Slate, Red, Orange, Yellow, Green, Teal, Blue, Sky, Violet and Pink.

A new option starts on Slate, the neutral grey, and stays there until you pick something

A colour shows on the chip in the table, on the rows inside the dropdown when someone is choosing, and here in this list — so a stage picked on a record reads the same as a stage read off the table.

The one exception is a field with Allow adding new options on. Options added on the spot are stored without a colour, so a creatable list would drift into rows of identical greys; Raion Hub hides the dot on those dropdowns rather than show you a column of the same swatch.

Save

Click Save changes. A toast reads Database config saved, and the chips in the table take their new colours.

Turn the options into pipeline stages

Switch Pipeline on — hinted Track this field’s options as ordered journey stages — and the list stops being a set of labels and becomes an ordered journey.

Drop-off rows keep their colour but lose their stage number — the numbers close up around them

Each on-path option’s dot becomes a numbered stage badge, filled with that option’s own colour. It is still the colour picker; clicking it still opens the swatches.
Each row gains a pill reading In journey. Click it and it becomes an amber Drop-off. Its tooltip explains why that matters: Drop-offs (like Lost or Junk) sit outside the journey — reaching one doesn’t count as progress toward the funnel.
Drop-offs do not take up a stage number. Numbering is recalculated every time you reorder, skipping them.

With Pipeline off, the options are plain labels and their order means nothing.

Collect extra details when an option is chosen

Under each option sits a checkbox: Collect additional details when chosen. Tick it and a Details to collect list appears, where you choose which other fields should be asked for the moment somebody picks that option.

Each row in the list shows the referenced field’s name and type, a Required checkbox, and a remove button.

On a date detail there is a star. Starring it marks that date as the stage’s own date — This is the stage’s date (milestone + analytics). Starring one clears the star from the rest. Until you star anything, the first eligible date is treated as the stage date. A Time field is not eligible.
The picker can also create a brand-new field for you. It hands over to the full field editor, and when you finish, you come back to this option with the new field already listed. A field created this way lands in the Qualification section.
A detail whose field has since been deleted shows in italics as Missing field followed by its key, so you can clear it.

Name, Status, Priority, Date Added, the field you are editing, and any Group field cannot be asked for as details.

Source is different

Opening the Source field’s editor replaces the option list with a lead-source manager, because those choices are not this field’s options — they are the workspace’s lead sources, and every Source picker in Raion Hub reads the same list.

The screen says it in full: These are your workspace’s lead sources, not per-field options — every Source picker in the app reads this list. Add one from any Source picker; archiving hides it from those pickers without changing the leads that already carry it.

The count in the heading includes archived sources, so it can be higher than the rows you see

Per source you can Rename, Merge it into another one, Archive it (and later Restore it), or Delete it. Archived rows stay in this list with an Archived marker; they just stop appearing in the pickers. Choosing merge reveals Move everything to, a dropdown (Pick a lead source…), and Merge / Cancel.

On a long list a filter box appears, with the placeholder Filter lead sources…. Before any sources exist the list reads No lead sources yet. Add one from the Source picker in Add Lead, Import, or a lead row.

Lead source changes save immediately. Renaming, archiving, merging and deleting a lead source do not wait for Save changes, and Discard will not undo them. Each one confirms with its own toast — for example “Walk-in” archived — hidden from the pickers, existing leads keep it.

These controls need the Lead Bank permission. Without it the row buttons are gone and a footnote reads Renaming, archiving and merging lead sources needs the Lead Bank permission.

Raion Hub will not let you delete a source that anything still points at. You get Can’t delete this lead source, a count of what still references it, and the way out: Merge it into another source to move them across, or archive it to hide it from the pickers without touching that history. When nothing uses it you get Delete this lead source? instead.

If something goes wrong

What happens	Why	What to do
One option has no trash button, just a gap	It is the option a new contact is created on, and the server refuses to delete it	Rename it instead of removing it
You cannot find a way to choose which option is the default	There is no such control on this screen	Rename the existing default to whatever you want new contacts to start on
Allow multiple selection is greyed out	The field is Status or Source — a core attribute, which holds one value	Nothing to do
Allow adding new options is not offered	You are editing Source, whose choices are workspace lead sources	Add a source from any Source picker, or manage the list here
Every option in a dropdown shows the same colour dot, or none	On a field with Allow adding new options, options added on the spot are created without a colour, so the dropdown hides the dot rather than showing a column of identical greys	Open the field here and give the options colours
A stage number skipped a row	That row is a Drop-off, and drop-offs sit outside the numbered journey	Nothing to fix. Click its Drop-off pill to put it back In journey
A change to the options vanished after saving, and a toast explained why	The server refused that one piece — removing a default option is the usual cause — and the screen reloaded what is stored	Read the toast, then redo the rest
Discard did not undo a lead-source rename	Lead-source changes commit immediately	Rename it back by hand
The lead-source rows have no buttons at all	You do not have the Lead Bank permission	Ask a Workspace Owner in Settings → Roles
The Lead sources count is higher than the rows you can see	The count includes archived sources	Nothing to fix