By 
Notion conditional color highlights database pages when a property matches a rule. Open the view’s settings, choose Conditional color, and add a color setting. In Table view, you can color an entire row or only the property used by the rule. In the other supported views, the color applies to the page background.
I would start with one question: which records need attention in this view? A priority rule makes urgent work easier to pick out while keeping the other records visible. Leave the priority value visible too, so the reader can understand the cue without relying on color alone.
Check the view and property before building a rule
Notion’s current conditional color instructions list Table, Calendar, Timeline, List, Board, and Feed as supported views. Gallery, Chart, and Form are not included in that list. If you cannot find the control in one of those layouts, use a supported view rather than assuming every database layout offers the same setting.
The supported rule properties are Select, Multi-select, Status, Title, Text, Number, Date, Person, Checkbox, Formulas, Relations, and Rollups. The property supplies the condition; it does not determine that every color scope is available. A formula-based rule, for example, still follows the scope of the view where you create it.
Some launch tutorials still exclude Formula, Relation, and Rollup properties. That restriction does not match the current help page, which lists all three. Use the current support list when deciding whether to add a workaround property.
| View | Documented color scope | Useful choice |
|---|---|---|
| Table | Entire row or the property used by the rule | Use a property highlight for a quiet cue; use the whole row when the record needs attention. |
| Calendar, Timeline, List, Board, Feed | Page background | Highlight the record as a whole. Do not expect a single property within a card to be colored separately. |
The distinction matters on a board: choosing Priority as the condition does not give you a separate colored Priority field inside the card. Coloring only one property requires Table view.
Set one priority rule
Before changing the rule, confirm that you are in the intended Table view and can edit the database's color settings. You need Can edit content, Can edit, or Full access; view and comment access let you see the colors without changing the settings.
For this example, use a Table view named Review queue and a Priority Select property with P0 and P1 options. The aim is to highlight P0 records in red. These are example field names and values; use the ones your team already understands.
Check the actual Priority values before opening Conditional color. A field called Urgency or an option called Critical needs a rule for those names, not a second property added just to match this example. If Priority is hidden, open View settings → Property visibility and show it in this view. Notion documents property visibility as a per-view setting. Keep that column visible while checking the rule.
- Open Review queue and select the slider icon at the top of the database view.
- Under View settings, choose Conditional color.
- Select New color setting, then choose Priority.
- Open the dropdown beside the property name and set the condition to match P0.
- Choose red for Page background.
- In Apply to, choose the entire row for this review queue, or just Priority if a smaller highlight is enough.
This follows Notion’s documented setup sequence. For applicable properties, the page background matches the option’s color by default: Notion gives P0 in red and P1 in orange as its example. Choose the background deliberately if your review view needs a different cue.
| Example record | Priority | What to check |
|---|---|---|
| Brand refresh | P0 | It matches the P0 condition and receives the chosen highlight. |
| Website launch | P1 | It does not match this rule. |
| Discovery add-on | Empty | It is not a P0 record. Enter a priority if one is missing; a highlight cannot supply that value. |
Inspect one matching record, one nonmatching record, and one empty value in your view. If the result surprises you, compare the actual Priority value with the condition before editing the record. A broad “not empty” condition answers a different question from “P0.”
Keep color rules local to the view
Conditional color settings belong to the view. A rule in Review queue does not automatically appear in another view of the same database. Duplicating a view also duplicates its color settings, so inspect the inherited rules before giving the copy a new purpose.
A weekly review can highlight urgent work while a reference list stays neutral. That is a useful separation: the stored Priority remains the record’s meaning, and each view decides how to emphasize it. If you need help choosing the layout first, the database views guide explains which question each view answers.
Color also does a different job from a filter. Filters show only records meeting their criteria; a color rule adds emphasis. If you want only P0 work in the queue, configure a filter. If you want to compare P0 work with the rest, keep the records visible and use color.
When the control or highlight is missing
Diagnose the specific symptom before changing stored values. The documented support and view-local rules give you these checks:
| Symptom | Discriminating check | Action and expected change |
|---|---|---|
| Conditional color is missing | Is this a supported layout, and can your account edit color settings? | Use Table or another documented supported view. If your access is view/comment only, ask the database owner for the appropriate grant. |
| A visible P0 record is uncolored | Compare this view's selected rule property and condition with the record's actual Priority. | Correct a rule targeting a different property or value. The intended highlight should apply only to records matching this condition. |
| The entire row is colored when you wanted one field | In Table, inspect Apply to. | Choose just the rule's property. The cue should be confined to that property rather than the whole row. |
| The same record is neutral in another view | Does that other view have its own color setting? | Configure a rule there if needed. A neutral reference view can also be intentional. |
| A matching record is absent altogether | Check the view's Filter conditions. | Review the criteria hiding the record. Color cannot make a filtered-out page appear. |
To remove the cue without changing Priority, open View settings → Conditional color and select the trash icon beside that rule. The delete-setting command removes that color setting. Inspect the same record afterward: its stored value should still be P0, while the deleted rule no longer supplies its highlight. Other rules or views need their own check.
Use Add another when a second condition answers a separate scanning need. Start with one rule, though, so it is clear which records should match. Keep the text values visible and give each color a stable meaning.
