Core Concepts

Concept	Description
Space	The workspace of one organization. Members, forms, apps, resources, and permissions belong to a space, and a member can enter every space they belong to
Form	Defines the fields, layout, buttons, print templates, and record pages of one kind of business record
Record	One row of a form. It carries a data state and an approval state, and it can run the approval processes and automation tasks configured for the form
App	A built-in or custom app that collects related work items, for example approvals, file bag, reminder, or an AI assistant
Resource	The external capabilities a space calls, for example AI models and map services
Message	Inbox messages, notifications, and conversations, routed by topic into the app that owns them
Roles and permissions	Roles, feature permissions, resource permissions, data policies, field permissions, and conditional sharing decide what each member may see and do

How They Fit Together

A form defines one kind of record: its fields, its layout, its buttons, its print template, and its record pages. Field design, layout design, button design, and print design all work on the same form
Every record belongs to one form. It carries a data state (draft, active, archived, trashed) and an approval state, and the approval processes and automation tasks configured for that form can run on it
Apps and messages are the entry points for daily work. Messages are routed by topic into the app that owns the topic, so the inbox stays grouped by what the work is about
Resources, such as AI models and map services, are external capabilities that the space calls. They are configured per space and shared by the features that need them
Roles and permissions decide what a member may see and do: feature permissions for menus and pages, resource permissions for forms, buttons, and fields, data policies for records, field permissions per field, and conditional sharing for rules that depend on the current record