Search the documentation

Find a page by title or section.

Data

Table columns and views

Choose which columns a list shows and in what order. The layout is saved per person, per table, and follows you between devices.

Updated

Most admin lists in Cooriroo carry more information than fits on a screen, so each one lets you decide what it shows. You pick the columns, put them in the order you read them in, and Cooriroo remembers — for you, on that table, everywhere you sign in.

Who can do this

Role
Administrators

No special permission is needed. A column layout is one of your own account preferences, so changing it never affects what a colleague sees, and an admin cannot set a layout on someone else’s behalf.

Change what a list shows

The Columns control sits in the toolbar above the table, next to the density control.

  1. 1

    Open the column manager

    Vehicles → Columns

    The button carries a count when you have anything hidden, so a list that looks like it is missing a field tells you why without being opened.

  2. 2

    Show or hide a column

    Toggling a column applies to the table straight away and saves in the background. If the save fails the table reverts and says so, rather than leaving you with a layout that disappears on the next page load.

  3. 3

    Drag columns into the order you want

    Order is part of the saved layout. Columns pinned to either edge stay where they are and are not draggable.

  4. 4

    Reset when you want the defaults back

    Reset clears your saved layout for that one table and the list falls back to its declared default columns. It does not touch any other table.

Where the layout is saved

Layouts are stored server-side against your user account, keyed by a stable table identifier such as vehicles or trips. That is what makes them follow you to another browser or machine. A copy is also kept locally so the table paints in your layout immediately rather than flashing the defaults first.

Saving is per table. Rearranging the trips list writes only the trips layout, so two tabs open on two different lists cannot overwrite each other.

Custom fields as columns

When a list supports custom fields, defining one adds two things to the table: a summary column showing a record’s values as badges, and one dedicated column per field. The dedicated columns start hidden and appear in the manager under their own heading, so adding a field never silently widens everyone’s table — it waits for the people who want it.

Because custom-field column identifiers are built from your own keys, a layout you saved keeps working when you add or archive fields: unknown entries are ignored, and newly declared columns are appended with their default visibility.

Row density

The density control next to the Columns button offers compact, default and relaxed, trading row height against how many rows fit on screen. It is set per table rather than globally, because a thirty-column log and a destination list with two-line address cells want opposite things.

Unlike the column layout, density is stored in the browser rather than against your account, so it does not travel to another device and a cleared browser returns the table to its default spacing.

Which lists are configurable

The column manager is available on, among others:

  • Operations: trips, trip exceptions, tasks, delivery pools, destinations, origins.
  • People: drivers, and the tasks, trips and shifts tabs on a driver.
  • Fleet: vehicles, work orders, inspections, inspection templates, service schedules, maintenance logs, fleet alerts.
  • Elsewhere: support tickets, the notification log, and import history.

Detail-page tabs count as their own tables. The visits tab on a destination and the cargo tab on a trip each keep their own layout, which is why customising one does not change the other.

Limits

  • Up to 50 tables with a saved layout per person.
  • Up to 300 column entries within one table.
  • Table and column identifiers are capped at 128 characters.

These are backstops rather than working limits — no list in Cooriroo comes close to 300 columns — and they exist so a stored layout cannot grow without bound.