Creating Object Types

An object type is the blueprint for a category of records — it defines the fields, layout, and identity of every record created under it. You build the object type first, then create records.

Go to Settings → Custom Objects → New Object Type.

Name and Identity

Every object type needs:

• Singular name — used when referencing one record (e.g. "Contract")
• Plural name — used in lists and navigation (e.g. "Contracts")
• Display ID prefix — a short code prepended to every record's auto-incremented ID. CON produces CON-1, CON-2, CON-3. Choose something short and recognizable — it can't be changed after records are created.
• Description — optional, shown in the object type directory

Scope

Scope determines where the object type and its records are available. Set it with the workspace dropdown — the same picker you use in workflows. You can tag an object type to the organization (global), to one or more workspaces, or both.

When you tag an object type to more than one workspace:

• The schema and records are shared across all the tagged workspaces — there's one set of records, not a copy per workspace.
• The object type shows up as an entity in each tagged workspace.
• Workflows for that entity are fully editable in its home context and read-only in the other workspaces it's tagged to.

Scope isn't fixed at creation. You can extend a workspace-scoped type to more workspaces, or promote it to organization scope, as long as you have the admin rights described in Who can manage object types.

Scope also limits relationships. A workspace-scoped object type can only reference global object types or object types that share at least one of its workspaces. See Relationship to custom object.

Who Can Manage Object Types

Who manages an object type depends on its scope:

• Global (organization) object types are visible to and managed by account admins.
• Workspace-scoped object types are managed by the workspace admin of each workspace they're tagged to.

Account admins get organization scope by default when they create an object type. They can assign it to any workspace where they're also a workspace admin, and they can promote a workspace-scoped type to organization scope if they're a workspace admin in that workspace.

Workspace admins can create object types too. A new type defaults to the workspace they administer, and they can extend it to other workspaces where they also hold workspace admin rights.

Scoping object types this way gives you a lightweight way to manage who sees and edits which data, ahead of full role-based access controls.

Draft and Published States

A newly created object type starts in draft state. It's visible in Settings but its directory isn't active and records can't be created.

Use draft state to build out your field schema and sections before making the type live. Once you're ready, publish it — the directory becomes active and your team can start creating records.

A published type can still have its fields edited. Adding new fields to a published type doesn't affect existing records — existing records show the new field as empty until filled in.

Sections

Sections group fields into labeled blocks on the record form. Every object type starts with a Basics section. You can:

• Rename existing sections
• Add new sections
• Drag fields between sections
• Reorder sections

Use sections when a record type has many fields and natural groupings exist. A Contract type might have a Contract Details section and a Parties section. A Vendor type might have a Vendor Info section and a Internal Management section.

Sections are purely organizational — they affect form layout but not field behavior or API access.

After Creation

Once published, the object type gets its own directory page where records can be created, searched, and filtered. You can then:

• Build saved views — filtered and sorted lists that your team can pin
• Configure automations — workflows triggered by record events or on a schedule
• Set permissions — control who can create, view, and edit records of this type
• Bulk-load records from a spreadsheet — see Importing records via CSV

On the records page, click the gear icon next to the object name to open the object type's configuration. The configuration page shows how many records the type has, with a View Records link that takes you back to them.