> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getkato.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Create focused views

> Use the same records to answer different questions.

export const DocImage = ({src, alt, caption, kind = "workspace", thumbnail = false, natural = false}) => {
  const paths = {
    objects: "m12 3 9 4.5v9L12 21l-9-4.5v-9L12 3Z M3 7.5l9 4.5 9-4.5 M12 12v9",
    attributes: "M4 5h16 M4 12h16 M4 19h16 M8 3v4 M16 10v4 M10 17v4",
    records: "M5 3h14v18H5z M8 7h8 M8 11h8 M8 15h5",
    relationships: "M8 8H4v8h4 M16 8h4v8h-4 M8 12h8 M10 10l-2 2 2 2 M14 10l2 2-2 2",
    views: "M3 4h18v16H3z M3 9h18 M9 9v11 M15 9v11",
    importing: "M12 3v12 M8 11l4 4 4-4 M4 16v5h16v-5",
    workspace: "M4 4h16v16H4z M4 9h16 M9 9v11",
    navigation: "m5 5 14 5-6 3-3 6-5-14Z",
    team: "M16 21v-2a4 4 0 0 0-4-4H6a4 4 0 0 0-4 4v2 M16 4a4 4 0 0 1 0 8 M22 21v-2a4 4 0 0 0-3-3.87 M13 7a4 4 0 1 1-8 0 4 4 0 0 1 8 0Z",
    tasks: "M9 6h11 M9 12h11 M9 18h11 M3 6l1 1 2-2 M3 12l1 1 2-2 M3 18l1 1 2-2",
    meetings: "M4 5h16v15H4z M4 10h16 M8 3v4 M16 3v4 M8 14h3 M8 17h6",
    ai: "m12 3 2.5 6.5L21 12l-6.5 2.5L12 21l-2.5-6.5L3 12l6.5-2.5L12 3Z",
    automation: "M9 3h6v6H9z M3 16h6v5H3z M15 16h6v5h-6z M12 9v4 M6 16v-3h12v3"
  };
  return <figure className={["kato-visual", thumbnail ? "kato-visual--thumbnail" : ""].filter(Boolean).join(" ")}>
    {src ? <div className={["kato-visual-frame", natural ? "kato-visual-frame--natural" : ""].filter(Boolean).join(" ")}>
        {thumbnail ? <img src={src} alt={alt || ""} loading="lazy" decoding="async" /> : <a className="kato-visual-fullsize" href={src} target="_blank" rel="noreferrer" aria-label={`Open full-size image: ${alt || caption || "Kato guide"}`}>
            <img src={src} alt={alt || ""} loading="lazy" decoding="async" />
          </a>}
      </div> : <div className="kato-visual-frame kato-placeholder" role={thumbnail ? undefined : "img"} aria-label={thumbnail ? undefined : `Image placeholder: ${alt || caption || "Kato workspace"}`} aria-hidden={thumbnail ? "true" : undefined}>
        <span className="kato-orbit kato-orbit--outer" />
        <span className="kato-orbit kato-orbit--inner" />
        <span className="kato-visual-icon"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" strokeWidth="1.4" strokeLinecap="round" strokeLinejoin="round" aria-hidden="true"><path d={paths[kind] || paths.workspace} /></svg></span>
        {!thumbnail && <span className="kato-placeholder-label">Image placeholder</span>}
      </div>}
    {caption && !thumbnail && <figcaption>{caption}{src && <span className="kato-visual-hint">Select the image to view it full size.</span>}</figcaption>}
  </figure>;
};

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.

<DocImage kind="views" alt="Different views of the same Kato object records" caption="A different perspective on the same underlying records." />

## 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.

<Tip>
  If a record seems to be missing, check your filters and selected view before
  creating it again.
</Tip>

## Keep exploring

<CardGroup cols={2}>
  <Card title="Bring your data into Kato" icon="arrow-right-to-bracket" href="/documentation/importing-data">Prepare your first records or plan an import.</Card>
  <Card title="Organize tasks" icon="list-check" href="/documentation/organize-tasks">Turn the context in your workspace into clear next steps.</Card>
</CardGroup>


## Related topics

- [Build a project pipeline](/recipes/project-pipeline.md)
- [Connect related records](/documentation/data/relationships.md)
- [How your data fits together](/documentation/data/how-data-connects.md)
- [Changelog](/changelog.md)
- [Choose what to track](/documentation/data/objects.md)