Tables
Manage tables, fields, and views
The Manage table dialog brings field management and saved view configuration into one workspace. Use it when you need more control than the quick controls available directly in a table.
Opening Manage table Opening Manage table
From a supported table:
- Click Actions above the table.
- Select Manage table.
You may also find Manage table in the table settings menu. Opening Manage view from a view tab takes you directly to that view's configuration when the action is available.
Fields and views are different Fields and views are different
The dialog separates two kinds of configuration:
| Section | What it controls |
|---|---|
| Fields | The data fields available to the table, including custom fields. |
| Views | How fields, sorting, and filters are arranged for one saved view. |
A field is part of the table's data model and can be used by multiple views. A view is only a saved presentation and query setup for that data.
Deleting a custom field permanently removes the values stored in that field. Deleting a saved view removes only its table setup.
Managing fields Managing fields
Open the Fields tab to review the fields available to the table. The list identifies the field type and whether a field is built-in, system-provided, a responsibility, custom, inherited, or editable.
Select a field to review its details and capabilities, including whether it can be hidden, sorted, or filtered. An Editable label means the custom field belongs to this table context; you still need the required permission to update or delete it.
To create a custom field:
- Open Fields.
- Click New field.
- Enter a descriptive name.
- Select the field type and complete its configuration.
- Save the field.
Custom fields can store organization-specific information such as priorities, external IDs, inspection dates, classifications, and numerical values.
Creating, updating, or deleting fields requires organization owner access for organization-level tables such as Sites. For a board-level table, you need organization owner access or permission to manage that board's settings.
Who can change a field's values Who can change a field's values
Site and board item fields have Editors: user groups whose members may change the field's values without being able to change anything else.
- On a site field, editors can change the field on the sites they have access to without the Update Sites permission. See Site Custom Columns.
- On a board item field, editors can change the field on every item they can see on the board, even when their board access only lets them view items.
Turn on Only editors can change this field to make the editors the only ones who may set or change it. Update Sites, or permission to update items on the board, then no longer covers the field, also when a site or item is created. Organization owners can always change it.
Configuring a saved view Configuring a saved view
Open the Views tab and select a view. The editor shows whether the view is built-in or user configured and whether it is Global, Public, or Private.
For an editable view, you can configure:
- Fields: Show or hide fields and arrange them from left to right.
- Sorting: Add one or more sorting rules and arrange their priority from top to bottom.
- Filters: Add saved filters that should apply whenever the view opens.
The field editor lists every available field. Drag fields into the required order and use the eye control to show or hide them.
Scroll below the field list to add sorting rules and field filters.
Click Save changes when you finish. If you try to close the dialog, switch sections, or select another field or view with unsaved changes, 21RISK asks whether you want to discard them.
Field widths are stored by saved views, but widths are changed by resizing fields directly in the table rather than in the Manage table view editor.
Permissions Permissions
You can create and manage your own private views. Public and built-in views may be read-only unless you are an organization owner or have permission to manage the relevant board's settings.
The same principle applies to fields. A field can be available to a table without belonging to that table context, and belonging to the context does not override your field-management permissions.
For everyday view tabs, copying a setup, and sharing views, read Saved table views.