Color-code a Property

Color makes a long Session items table easy to read at a glance. A red Status / Rejected chip jumps out where a gray one would blend in. This page covers where to set the color and how the cascade works.

Where to set a color

Colors are set in the Property editor, on the circular color button next to each field.

1. Open the Property editor on any Session item — either click + Property on a row, or expand a row and click an existing Property chip to edit it.

2. Find the circular color button next to the Name or Value field you want to color. The button shows the current color, or a transparent/inherited indicator if it’s set to inherit.

3. Click the color button. The Select Color dialog opens with the available swatches.

4. Click a swatch to select it. The selected swatch shows a check mark.

5. (Optional) To go back to inheriting from the parent, click the Inherit option in the dialog.

6. Click Apply.

The color saves immediately and applies everywhere that Property is shown.

How color inheritance works

Each Name in your Property library can have a color, and each Value under it can have its own color or inherit from its Name.

If Value has a color	Chip uses
Yes	The Value’s color.
No (inherits)	The Name’s color.

In practice this means:

• Color the Name when every Value under it should share a hue. Example: paint Status blue, and every Status Value shows up in blue chips unless you override it.
• Color the Value when you want to highlight specific outcomes. Example: keep Status chips blue overall, but make Status / Rejected red and Status / Approved green to stand out.

Where colors show up

• Property chips on Session item rows — the most obvious place.
• Property dropdowns in the editor — colors render on each option to help you pick.
• CSV export does not include colors. Color is a UI affordance, not data.

Tips

• Use color sparingly. If every Name is colored, nothing stands out. Reserve color for the Names you actually look for.
• Pick a small palette. Three to five colors across your library is plenty. More than that and your team starts forgetting what each one means.
• Color signals state, not category. Audio engineers read red/yellow/green as severity at a glance. Use that wiring: red for problems, green for “done”, yellow for “needs attention” — and avoid using those colors for unrelated categories.

See also

• Build your Property library — where Names and Values are created.
• Property model — the data-model reference, including how color is stored.
• Glossary: Property, Property library