Skip to main content
A view is a saved way to look at an object’s records. It combines a layout with details such as visible attributes, filters, sorting, and grouping. Your team can focus on the information it needs without making another copy of the data.

​
Pick a layout

The object view creation menu currently offers Table and Kanban. Start with a table for detailed scanning. Use a kanban board when groups or stages are the main thing you need to see. Gallery and Calendar object views are not currently enabled in this menu.

​
Build around a question

For a Projects object, a view called Active projects could show only records with an active status, display their target dates, and sort by the next deadline. A second view could group the same projects by status.
  1. Choose the object and the view you want to configure.
  2. Select the attributes that help answer your question.
  3. Filter out records that are not relevant to that view.
  4. Apply sorting or grouping to make the next action clear.
  5. Give the view a name that describes its purpose.

​
Walkthrough: an Active projects table

Start with a Projects object containing a few records and an attribute for the project’s current stage. Add a target date if the team uses deadlines.
  1. Open Projects and its view selector. Choose Create new view.
  2. Choose Table, enter Active projects as the name, and select Confirm.
  3. Use the view’s attribute controls to show the project name, status, target date, and Client relationship. Hide details you do not need for this review.
  4. Add a filter for the status that means active work in your workspace.
  5. Sort by target date so the next commitments are easy to find.
  6. Compare the result with two known records: one active project should appear; one completed project should be excluded by the filter.
The final check matters. A view that looks tidy but omits the wrong records can mislead your team about the work it needs to do.

​
Walkthrough: a delivery board

Create another view, choose Kanban, and select the attribute used to group the records. A grouping attribute is required before you can confirm a new kanban view. Use an appropriate choice attribute such as your delivery status. Name it Delivery board, then check that records appear in the expected columns. A record without a grouping value needs attention if you expected all projects to have a stage. Inspect its value rather than assuming it disappeared.

​
Make filters easy to reason about

With multiple filters, check whether the view requires all conditions or any condition. “Active and due this month” is a narrower set than “Active or due this month.” Name the view according to what it actually selects. Before sharing a process around a view, explain what is intentionally excluded. Keep a broader view available for looking up records outside that process.

​
Understand what changes

Hiding a column does not remove its attribute. Filtering a record out of a view does not delete the record. Editing a record’s values, however, changes the underlying record wherever it appears.
If a record seems to be missing, check your filters and selected view before creating it again.

​
Keep exploring

Bring your data into Kato

Prepare your first records or plan an import.

Organize tasks

Turn the context in your workspace into clear next steps.