Custom Objects
Model something the platform doesn't ship with (a real table with audit, search and ownership behind it) as configuration, not a development project.
Illustrative UI only. Data and individuals shown are fictitious; any resemblance to real persons or data is coincidental.
A real table, standard equipment included
A new object arrives with identity, timestamps, soft-delete and audit columns already in place, plus indexes tuned for the active-record lists people actually browse.
Capabilities are toggles
Ownership, approvals, tags and field history are each a flag on the object that provisions the columns and machinery behind it. What you switch on is what you get.
Numbering built in
Records can auto-number on a template you define, such as CLM-2026-0001, with the sequence managed for you, so reference numbers are born unique instead of policed by convention.
Your domains, properly separated
Objects group into namespaces that are real database boundaries. A new line of business gets a clean space of its own, not a prefix naming convention.
Why we like this one
The proof point is that the platform is built on it. The claims, the approvals, the conversations, the finance records: roughly a hundred shipped objects are provisioned by exactly the machinery you'd use for your own. Custom objects aren't a side door bolted on for customers; they're the front door the product itself walks through, which is the strongest guarantee that they'll keep working.
Book a demo ➝