Objects and records

Objects define the types of data your workspace tracks. Records are the individual entries inside those objects.

When to create an object

Create an object when the workspace needs a durable source of truth for a type of item. Common examples include companies, contacts, deals, accounts, vendors, candidates, or projects.

Do not create an object for a temporary list of work. Use a list or board for workflow-specific grouping.

Object structure

An object can have:

• A singular and plural name.
• A URL slug.
• An icon.
• Attributes.
• Views.
• Record page configuration.
• System or custom object behavior.

Attributes

Attributes are fields on records. They can hold structured values such as text, options, relation-backed fields, enriched values, or other supported field types.

Use clear labels and avoid duplicating the same concept in multiple fields. If two objects need to be connected, use a relation instead of manually copying values.

Views

Views are saved ways to work with records. A default list view is useful for everyday scanning. Kanban-style views can be used for pipeline workflows when enabled.

Good object design

1. Name the object clearly

   Use a name people already understand, such as Companies or Deals.

2. Define required fields

   Add only the fields needed for the first workflow.

3. Create a default view

   Make the default view useful for day-to-day work.

4. Connect related work

   Link records to conversations, notes, files, tasks, or other records when context matters.

Common mistakes

• Creating separate objects for every team instead of sharing one source of truth.
• Using text fields for relationships that should be modeled as relations.
• Importing data before object fields are reviewed.
• Creating too many views before the team has used the default view.

Related guides