Platform · Data Model

The structured foundation under every process.

Design custom entities, give them fields across 23 data types, and connect them with real relationships. Every record you capture flows through your process — and powers your UI, dashboards, workflows and AI agents.

No schema migrations, no SQL, no infrastructure to manage.
app.processo.io / model / orders
Data Model Configuration for Orders
Define entities, fields & relationships
Fields Relationships Visibility Data Auth Matrix
+ Add Entity
Orders18 fields
Customers24 fields
Invoices15 fields
Line Items9 fields
Payments11 fields
Fields 18 + Add Field
Order TypeDropdown
Order Number *Text
CustomerText
Delivery AddressTextarea
Order DateDate
Created Date TimeDateTime
23 field types
Linked records
The building blocks

Entities, fields and relationships

Everything in Processo starts with the data model. An entity is a type of thing your business tracks — a customer, an order, a ticket. Fields describe each one. Relationships connect them so records flow together through your process.

Entities

Define a table for each thing you track. Each entity lives inside its process with its own records, workflows and permissions — fully isolated from the rest.

Fields

Add columns to an entity from 23 data types — text, number, currency, date, status, people, attachment and more — each with its own validation rules.

Relationships

Link entities with one-to-many, lookups and object references. A record in one entity points to records in another, so your data stays connected and never duplicated.

How it works

From blank canvas to working schema

Model your process the way you think about it — name the things you track, describe them, define relationships between them. No migrations, no DBA.

Define an entity

Create an entity for each business object — Customer, Order, Invoice. Start from a prebuilt process or a blank canvas; each entity is scoped to its process.

Add fields with the right type

Pick from 23 data types, set required / unique validation, and flag sensitive fields as PII or ePHI so governance follows the data automatically.

Link entities together

Add a lookup or object-reference field to connect one entity to another, choosing one-to-many or one-to-one. Related records now travel together.

Put the model to work

Records flow into UI, dashboards, workflows and AI agents instantly — the model you draw is the model everything else reads from.

app.processo.io / model / projects
Fields 9 Search… Add Field
Assignees * People
Description * Textarea
End Date * Date
Project Name * Dropdown
Start Date * Date
Status * Status
Tags * Tag
app.processo.io / model / relationships
Data Model Configuration for Accounts
Define entities, fields & relationships
Fields Relationships Visibility Data Auth Matrix
Deals
22
Contacts
26
Accounts
27
Relationships

Connect records, never copy them

A relationship is a field that points at another entity. Look up a customer from an order, reference an order from an invoice — the data stays in one place and every view pulls the live value.

One-to-many. One customer has many orders; one order has many line items. Open a parent record and see all its children inline.
Lookup fields. Pick a related record from a searchable picker on the form. The order's customer field stores the link, not a copied name.
Object references. Reference whole records across entities — an invoice that points to its order, carrying context through the process.
Linked & computed values. Surface fields from a related record and roll up aggregates so totals and statuses stay in sync automatically.
Field types

23 data types, validated and governed

Every field carries a type, optional validation rules, and a sensitivity flag. Capture money as Currency, choices as Dropdown or Status, people as a user picker, and files as Attachments — each rendered with the right input and stored correctly.

Per-field validation. Required, unique, format and range rules keep records clean at the point of entry.
PII & ePHI flags. Mark sensitive fields once and governance, masking and access controls follow the data everywhere.
See all 23 field types
Textbox Textarea Number Date DateTime Boolean Dropdown Multi-select Email Phone Website People Tag Status Currency Rating Time Location Checkbox Attachment Progress Priority Object reference
Visibility & access

Decide who sees what, right on the entity

Access is part of the model, not a layer bolted on afterwards. Every entity carries its own rules — who can open it, which records they can reach, and whether they can take the data out.

Entity access. Keep an entity public to the workspace or make it private and grant it explicitly. Nobody reaches an entity they were never given.
Record access, row by row. Scope rows to named users, to roles, to anyone whose attributes match, or inherit from the parent record so children follow whoever owns the parent.
Download access. Reading a record and exporting it are separate rights — let a team work on-screen while bulk download stays with a few roles, and masked fields stay masked in the file.

Set once on the entity, enforced everywhere the data travels — pages, dashboards, queries, exports, workflows and AI agents all resolve the same rules.

See the full authorization model
app.processo.io / model / visibility
Entity Record Download
Public Private
Who can access records?
Users Roles Attributes Parents
Select Users
Save Changes Cancel
Works with

The data model connects to everything

Your entities are the foundation. Explore the capabilities that build on top of them.

Start modeling

Design the data model for your process today.

Create entities, add fields and draw relationships in minutes — then build the pages, dashboards and automations on top. No code, no infrastructure.

Start building free Back to platform