Entities are the business objects that make up a model — customers, orders, assets, and anything else you want to represent — and fields are the pieces of structured data that describe them. Together they define the shape of the data your ontology works with, from how it's stored to how each record is displayed.
Overview
Every model is built from one or more entities. Each entity lives on its own Entities tab, and within it a Fields tab holds the individual attributes that make up a record. You can add fields one at a time, import them in bulk, and fine-tune how each one behaves — whether it's searchable, required, or treated as the record's primary key. A separate Identity screen controls how records are labeled and displayed once the entity is set up.
Creating an Entity
To add a new entity, open the model's Entities tab and select New Entity. This option is available whenever you have edit access to the model — you'll see it both on the tab itself and in the empty state before any entities exist. Give the entity a Name (required, with an optional avatar icon), along with Tags and a Description to help others find and understand it.
Next, choose where the entity's data will live under Store data in. This choice is permanent and can't be changed after the entity is created:
JSON Store — document-style storage. You can also turn on Enable Reporting to include the entity in reports and analytics.
Analytics Store — storage optimized for analytical workloads. You can also turn on Time-based Composite Key so that time becomes part of each record's unique identifier.
Regardless of which store you choose, two more toggles are available: Enable SCD Type 2, which keeps a version history of each record so you can track how it changed over time, and Enable Auditable, which makes record-level activity and history visible directly on the golden record.
Field Types
Once an entity exists, add fields to it from the entity's Fields tab. Fields fall into three groups depending on what kind of data they hold:
| Group | Field types | Notes |
| Primitive | String, Integer, Date Time, Boolean, Number | Basic single-value data types. |
| Complex | Array, JSON, Single Select Lookup, Multi Select Lookup | Array fields have an element type; lookup fields join to another entity through an entity field, object field, and value field. |
| Derived | Formula | You supply the Formula Logic and choose a Formula Data Type for the result. |
Every field — regardless of type — needs a Key (must start with a letter, and can only contain letters, numbers, and underscores), a Display Label, a Description, and an optional Default value.
Field Settings
Open a field's Additional Settings panel to control how it behaves across the rest of the product:
| Setting | What it does |
| Filterable / Searchable / Sortable | Lets records be filtered, searched, or sorted by this field. |
| Primary Key | Uniquely identifies each record. Not available on Array or JSON fields. |
| Is Required | Records can't be saved without a value in this field. |
| Hashable | Securely hashes the field's data before storing it. |
| Secure Field | Stores the field's data in encrypted form. |
| Timestamp Field | Available only on Date Time fields. |
Hashable and Secure Field are mutually exclusive — turning one on automatically turns the other off.
Importing Fields
Instead of adding fields one at a time, you can import them in bulk. Both Add Field and Import Fields require edit access to the model, and are hidden entirely — not just grayed out — if you don't have it. Import Fields supports three methods:
Upload File — import a schema from a CSV or XLS file; a template is available to download and fill in.
From Sources — pick a connected source, choose the objects you want, and select which of their fields to bring in.
Suggest Fields — import a ready-made set of fields from the template library.
Whichever method you use, you'll see a consolidated preview before committing — existing fields alongside the new ones, with the new fields highlighted — followed by a success count once the import finishes.
Record Identity & Display
Each entity has a Settings › Identity screen where you can edit its name, avatar, description, and tags after creation. This is also where you set the Record Title Format — a template that determines how each record is displayed throughout the system. Type {{ to insert entity fields into the template; if you leave it unset, records are identified by their primary key by default. The entity's storage choice is also shown here for reference, but it's disabled — since it was fixed when the entity was created, it can't be edited from this screen.
Notes
The Store data in choice (JSON Store vs. Analytics Store) cannot be changed once an entity is created — pick carefully.
A field's Key must start with a letter and can only contain letters, numbers, and underscores — no spaces or other special characters.
Primary Key is unavailable on Array and JSON fields, since those types can't uniquely identify a record on their own.
Turning on Hashable disables Secure Field, and vice versa — you can't apply both to the same field.
Add Field and Import Fields both require edit access to the model; without it, these options don't appear at all.