Skip to main content
Object Views are the Views you set up once on an object and then see on every record that belongs to it. You define the layout (which components show, how data is filtered) at the object level, and Custral renders that same layout, scoped to the individual record, whenever someone opens one.

​
Define once, use everywhere

This is the heart of record routing: structure lives on the object, and each record is a personalized instance of it.
  • On the Contacts object you build a View with a contact list and a stat card.
  • When a teammate opens the record for Avery Durrant, that same View appears. Filtered to show only Avery’s data.
You never lay out each record by hand. Configure the object’s Views, and every record under it shares a consistent, contextual experience.

​
Configuring an Object’s Views

1

Open the object

Go to the object whose record layout you want to shape (for example, Contacts).
2

Build the Views

Add the views and components you want every record to show. Lists of related records, summary cards, activity feeds, and so on.
3

Open any record

Each record now renders those Views automatically, scoped to its own data.

​
Contextual components

Components on an object’s Views adapt to the record being viewed. A “Related Deals” component on the Contacts object shows the deals tied to whichever contact you opened. No per-record setup required.

​
Permissions

Like every Custral surface, Object Views respect permissions. What a person sees on a record depends on their access to the underlying entities: the object, the record, and the Views themselves.

​
See also

Record Routing Overview

Views Overview

Components Overview

Records