Objects

Objects controls how supported record pages are arranged. It uses the same Properties catalog as forms, filters, and automation, but focuses on presentation: which cards and tabs are visible, their order, and which properties appear inside editable cards.

Open Settings → Objects, select an object, and open its Default view.

Supported objects

The record-layout editor currently supports:

• Contacts
• Accounts
• Deals
• Tickets
• Orders
• Price Offers
• Products
• Invoices
• Forms
• Activities
• Campaigns

Not every module with Properties is available in Objects. For example, Projects have properties and pipelines but do not currently have an organization-wide record layout in Objects.

Default view

Each supported object has one Default view assigned to all workspace users. If the organization has not saved a layout, Workstation uses the current system layout.

Saving the Default view changes every record page for that object in the organization. Use Reset to system layout to replace a saved layout with the current system default.

The three layout regions

Left sidebar

The left sidebar contains identity, status, key information, tags, and other compact cards. You can:

• Drag cards to reorder them
• Hide a card and restore it from the card library
• Edit registered property cards
• Create custom property-list cards

An object can have up to 20 custom left-sidebar property cards. A property card can show up to 50 properties.

Middle column

The middle column contains the primary record workspace. Tabs may include About, Activities, Emails, Comments, Timeline, Invoices, and other object-specific areas.

You can reorder or hide registered tabs, but at least one middle-column tab must stay visible. Tabs with a registered card catalog also allow their cards to be reordered or hidden. Editable property cards can use one or two columns.

Some tabs and cards contain application behavior rather than a simple property list. These remain available as whole cards and do not expose a property editor.

Right sidebar

The right sidebar contains associations, files, totals, context, and other supporting cards. You can reorder, hide, or restore available cards.

Registered association cards can also be configured with:

• A custom title
• Up to six properties from the associated object
• Primary-association filtering
• Quick filters
• Default sorting

Filters and sorting are applied before the compact card limit, so they determine which associated records appear first.

Editing a property card

Select the pencil action on an editable property card to:

1. Change the card title.
2. Add properties from the selected object’s live Properties catalog.
3. Drag properties into the preferred order.
4. Remove properties from the card without deleting their data.
5. Choose one or two columns where the card supports it.
6. Preview values using a real record.

Adding a property to a card does not change its group in Properties. The group and the card placement are independent.

Creating a property-list card

From the left-sidebar card library:

1. Select Add card.
2. Open Create card.
3. Choose Property list.
4. Enter a title and add at least one property.
5. Select Create card.
6. Save the full record layout.

Creating the card only changes the unsaved editor state. Use Save or Save and exit to publish it to the workspace.

Save, undo, and exit

Layout changes are not automatic. The editor provides:

• Undo and Redo for changes made during the current edit session
• Save to publish and continue editing
• Save and exit to publish and return to Objects
• An unsaved-change warning when exiting without saving

User customization

The editor’s Settings tab controls whether users may personally reorder left-sidebar cards, right-sidebar cards, both, or neither.

A user’s order is only a personal overlay. It cannot change which cards the organization makes visible, card contents, property selection, or the shared middle-column layout. New organization cards are still added for users who previously customized their order.

Properties, Objects, and views

• Use Properties to define and validate data.
• Use Objects to place that data and arrange the record experience.
• Use Table Views to configure list and Kanban pages.
• Use Pipelines to control stages and movement rules.

These settings are independent. Hiding a field from one record card does not delete the property, remove it from reports, or hide its list-table column.