A table has eleven view types: Grid, Card, Kanban, Calendar, Timeline, Gantt, Map, Chart, Dashboard, Form and Document. Every view shows the same records in a different layout. Think of one set of index cards laid out eleven ways.

Here is the test: start from the question you want answered. Each section below gives the one-line test for a type, the field it needs and the link to its article.

Example: the Vendor Management solution has three tables, Vendors, Contracts and Findings, and four parties who read them. Security owns the vendor data, Procurement edits contracts, Finance reads values and an external auditor checks the evidence. Each party's question has a view that answers it.

The Create New View list open at the bottom of the View Panel, with the eleven view types, Folder and Explore View Types.

The View Panel is the column at the left of a table. It lists the public views, any folders and My Private Views. At its foot sits the Create New View button.

Explore View Types is a window with one card per type, in two columns, in the same order as the hover list. Each card carries the type's name, an illustration and a one-line description of what the type is for. Selecting a card opens the same Create dialog over the window; an x at the top right closes it.

The Explore View Types window with one card per view type.

Each type below has the test, the field it needs and one line of the example. The settings live in the type's own article.

The test: do you want rows and columns you can edit in place? Grid is the view every table starts with. It needs no special field. Security's "Vendor risk register" is a grid of Vendors with the seven fields the program reads. See Grid View.

The test: do people know a record by its picture or logo? Card shows each record as a card. It needs no special field; an image field gives the cards a cover. "Vendor cards" uses Vendor Logo as the cover. See Card View.

The test: does each record sit at one stage of a process? Kanban shows records as cards in columns, one column per stage. Its Column Grouping setting offers Assigned To, Single Select and Status fields, and a new view groups by the first of them. The "Findings board" has a column per Status. See Kanban View.

The test: does each record belong on a day? Calendar places records by a date or a date range. It needs a date field, and a new view takes the table's first one. The "Renewals calendar" puts every contract on its Renewal Date. See Calendar View.

The test: do records span a period you want to see side by side? Timeline draws each record as a bar across a custom period. It takes a start date field and an optional end date field; a Due Date field holds both. A new view takes the table's first date field. The "Fieldwork timeline" draws each Audit Fieldwork Window. See Timeline View.

The test: does one task wait for another? Gantt draws tasks as bars with their durations and the links between them. It is built on the table's Dependency field, whose settings hold the start and end dates. The "Remediation plan" shows which finding waits on which. See Gantt View.

The test: do records have a street address? Map places each record as a pin. It needs an Address field; a text field is not accepted. The "Vendor map" pins every vendor at its Headquarters. See Map View.

The test: do you want one picture of the table instead of its rows? Chart counts or sums the records as one of fifteen chart types in six groups: Bar, Bubble, Column, Heatmap, Line and Pie. It needs a field to count or sum and a field to group by. "Findings by severity" counts findings per Severity. See Chart View.

The test: do you want widgets from several tables on one page? A dashboard holds widgets that read any table in the workspace. It needs no field of its own. "Vendor risk overview" puts the chart, the register and a metric on one page. See Get started with dashboards.

The test: do people add records through a fixed set of questions? A Form view shows one of the solution's forms inside the table. The form is built in the Forms listing first, so the view needs an existing form. "Vendor intake request" is how a new vendor is proposed. See Form View.

The test: do the notes belong next to the records? Document is a page you write inside the table, not tied to one record. It needs no field. "Vendor assessment summary" explains the assessment approach beside the Vendors table. See Document View.

Open the view menu, the chevron next to the view name above the toolbar. Its items are Rename View, Add Description, Duplicate View, Change View Type, Public View, Delete View and the Autosave changes checkbox.

Change View Type offers eight types: Grid View, Card View, Kanban View, Calendar View, Timeline View, Gantt View, Map View and Chart View. A check mark sits on the current one. Dashboard, Form and Document are not on the list. They are created as new views, never switched to or from. The records are untouched by a switch.

Delete View asks "Are you sure?" with No, cancel and Yes, delete view. The last public view of a table cannot be deleted.

The view menu open with the Change View Type submenu listing the eight types.

A public view is edited and saved by members with full access and above. A private view is seen and edited by its creator only, under My Private Views. A Solution Manager or Administrator can lock a public view so its settings cannot change until it is unlocked. Folders carry their own permissions. The detail is in View Panel, Locked Views, Folder Permissions and Shared Views.

Last verified 1 Nov 2026.