kintone's list views have no setting that changes a row's color only when it meets a condition, such as turning a row red once its due date has passed (as of October 2026). The list view settings only let you choose which fields to display, filter records, and sort them. Instead of color, the practical standard workaround is to create separate views for each condition so you can tell records apart without color.
List view settings cover displayed fields, filtering, and sorting — there's no color option
When you add or edit a list view, you can set the view's name, choose between table format and calendar format, and then configure table-specific settings (which fields to display and in what order) or calendar-specific settings (which date field to use as the basis and which field to use as the title). You can also set a filter for which records to display, and sorting (up to five levels). The official kintone help page for this screen does not include any item for changing a row's background color or text color based on a condition (as of October 2026).
The one place within list view settings where you can touch the appearance is the Customize view format, where you write your own HTML. However, this requires kintone System Administration privileges, so it isn't something an app administrator can casually color-code on their own list whenever they want.
Creating multiple views for each condition lets you tell records apart without changing color
The fact that list view settings include a filter for "which records to display" means you can create several views in the same app, each with a different filter. For example, if you set up separate views such as "Due Today" and "Overdue," you can just switch to the view you need to see that filtered set of records. Rather than making certain rows stand out with color, you separate the view itself.
Because this approach stays entirely within filtering and sorting, there is no need to ask anyone with higher-level permissions to set it up. If the app administrator already has permission to add and edit views, they can try this right away.
List the situations where you want color-coding, then check whether filtering or sorting can achieve the same result
Start by listing, as bullet points, the specific situations where you wanted to use color. Make clear what you're actually trying to distinguish — for example, "I want overdue orders to stand out" or "I want to see records grouped by assignee."
Next, for each situation, try creating a view with a different filter condition. For overdue records, use a date filter; for grouping by assignee, filter by the assignee field. Check whether the view then shows only the records you want to see.
If switching between views isn't a burden, your workflow can run fine without color. If there are still situations where switching feels like too much friction, treat only those specific cases as candidates for a customization.
