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

# Record Routing

> Understand how Custral connects Object structure with Record-level navigation.

In Custral, **routing** is how you go from a structured data definition to a real, interactive workspace. [Objects](/data/objects/overview) define the structure, which [views](/surfaces/views/overview) and [components](/surfaces/components/overview) exist, while [records](/data/records/overview) bring that structure to life when you open one. Configure a layout once on the object, and every record under it renders that layout, scoped to its own data.

## The two halves

Routing bridges two things:

* **Objects**: where the structure of your data and its views are defined.
* **Records**: where those views are actually displayed and acted on.

When you open a record, Custral loads the record together with its parent object and renders the object's views. Each one scoped to that single record.

<img src="https://mintcdn.com/custral/NGCdls_pt-1YDx5S/images/object-routing.jpg?fit=max&auto=format&n=NGCdls_pt-1YDx5S&q=85&s=cb257435e410c5a0cf37160dc81f3294" alt="Object routing" width="2736" height="1461" data-path="images/object-routing.jpg" />

## How a record opens

<Steps>
  <Step title="Follow a record link">
    Click a row in a database view, a search result, a related-record link on another record, or a link in a workflow or notification. You land at `/records/<recordId>` (for example, `/records/rec_123`).
  </Step>

  <Step title="Custral loads the record and its object">
    The record arrives with its parent object attached, so Custral knows which views to draw and what the record's name and fields are.
  </Step>

  <Step title="The object's views render as tabs">
    Each view configured on the object becomes a tab on the record, scoped to that record's data. No per-record setup required.
  </Step>
</Steps>

## Views come from the object

You lay out a record's experience **once, on its object**, not on each record by hand. Add the views and components you want every record to show (a summary dashboard, lists of related records, an activity feed), and Custral renders that same layout for every record under the object.

| Layer                                | Role                                                | Example                                                   |
| ------------------------------------ | --------------------------------------------------- | --------------------------------------------------------- |
| **[Object](/data/objects/overview)** | Defines the available views and layout.             | *Contacts* object → *Overview*, *Related Deals*           |
| **[View](/surfaces/views/overview)** | Sets the filters, layout, and components to render. | *Overview* → summary card + activity feed                 |
| **[Record](/data/records/overview)** | Renders the object's views, scoped to itself.       | *Avery Durrant* → the same tabs, filled with Avery's data |

Components adapt to the open record automatically: a "Related Deals" component on the Contacts object shows the deals tied to whichever contact you opened. See [Object Views](/surfaces/records/views) for how this is configured.

## On a record page

A record opens as a full screen with its name and breadcrumb in the header, the object's views as tabs, and a set of actions:

| Action                               | What it does                                                           |
| ------------------------------------ | ---------------------------------------------------------------------- |
| **Share**                            | Grant another person or group access to this record.                   |
| **Duplicate**                        | Create a copy of the record.                                           |
| **Run AI Enrichment**                | Run the object's AI auto-fill agents to populate empty properties.     |
| **Create Shortcut**                  | Add a sidebar shortcut, in a section you pick, that opens this record. |
| **Add to Favorites**                 | Star the record for one-click access from Favorites.                   |
| **Edit Object / Properties / Views** | Jump to the object to change its structure or record layout.           |
| **Delete**                           | Archive the record.                                                    |

## Why this model works

* **Reusability**: define structure once on the object; every record shares a consistent experience.
* **Context**: each record automatically fills the object's views with its own data.
* **Dynamic routing**: every record URL (`/records/<recordId>`) renders the object's layout without a hand-built page.
* **Linkable**: point dashboards, workflows, and notifications straight at a record; Custral supplies the context.

## Related

<CardGroup cols={2}>
  <Card title="Object Views" icon="face-viewfinder" href="/surfaces/records/views">
    How the views you configure on an object appear on every record.
  </Card>

  <Card title="Views Overview" icon="eye" href="/surfaces/views/overview">
    The view types a record's tabs can be built from.
  </Card>

  <Card title="Objects" icon="cube" href="/data/objects/overview">
    Where a record's structure and views are defined.
  </Card>

  <Card title="Records" icon="table-list" href="/data/records/overview">
    The data model behind every record.
  </Card>
</CardGroup>


## Related topics

- [Object Views](/surfaces/records/views.md)
- [Navigation Overview](/surfaces/navigation/overview.md)
- [Surfaces](/surfaces/overview.md)
- [Chat Routing](/comms/chat/routing.md)