Creating Object Types
Define the schema, display ID, and scope for a new custom object type.
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.
CONproducesCON-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:
| Scope | When to use |
|---|---|
| Global | Organization-wide data — vendors, clients, contracts, projects. Visible across all workspaces. |
| Workspace | Data relevant to one team or service desk only. Scoped to a specific workspace. |
Scope cannot be changed after the object type is created.
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