Configure the CRM data model

Members with Manage CRM schema can open Workspace settings → CRM. Start with a template or build the model directly. A template preview shows every proposed Record Type, field, layout, and view before it writes anything.

All CRM settings appear in one scrollable list with category headings on desktop and mobile. Scroll to the template, terminology, Record Types, fields, layouts, views, or process settings you want to edit.

Recommended setup order

1. Set the terminology your team uses for People, Organizations, and Records.
2. Create Record Types and their ordered status pipelines.
3. Add only the custom fields needed for decisions or automation.
4. Arrange create, edit, detail, and quick-create field layouts.
5. Create shared saved views for the team's daily work.
6. Add lifecycle definitions, forms, segments, and automations after the core model is stable.

Field types use plain-language choices such as Whole number, Yes or no, One choice, and Multiple choices. Choose the option that matches what members should enter; Bnder keeps the underlying technical identifier stable. Number fields accept ordinary decimal values, including scientific notation, but reject blank or yes/no values. Date fields reject impossible calendar dates instead of silently moving them into another month. The same checks apply to forms, imports, automations, and manual edits.

When you save a Record Type, field, relationship, layout, or view, the editor stays open until Bnder confirms the change. The Save action shows progress while Cancel is temporarily disabled. If saving fails, your entered values remain available so you can retry.

Bnder warns before Cancel, Escape, or Back would discard edited values. On desktop, press Cmd+S on macOS or Ctrl+S on Windows and Linux to save the active CRM form.

After a CRM change, Bnder confirms success or shows a clear error without hiding the form's existing guidance. Archiving a recoverable entry shows Undo for a short time so you can restore it immediately.

Formula, lookup, and rollup fields are calculated by Bnder and remain read-only. Connected-source ownership can also prevent manual edits to provider-managed values.

Fields, layouts, and views

Record Types describe what you track for a customer, such as a Deal or Subscription. People and Organizations describe the customers themselves. Give each type singular and plural names, define its stages, then add custom fields.

Layouts decide which fields appear in create, quick-create, edit, and detail forms. Views decide how records are filtered, sorted, grouped, and displayed. A personal view stays private; a team view is limited to effective team members. A view can use a table, Kanban board, calendar, timeline, or owner layout.

When editing a view's name or layout, unchanged filters are preserved. Change a filter only when you intend to change which records match.

Access and plans

Permissions and plan entitlement are separate. View CRM, Manage CRM, Manage CRM schema, Manage connectors, Export CRM, and Merge CRM records control what a member may do. Paid seats add capacity or unlock paid actions but never grant permission automatically.

Free provides a small complete trial. Starter and Pro seats add shared records, schema, views, forms, segments, lifecycles, automations, and monthly automation runs.

Calculated fields and relationships

Formula fields calculate values with Bnder's supported expressions. Lookup fields read a field from a related record; rollups summarize related values, for example a count or sum. These fields are read-only in records, forms, and imports. If a calculation shows #ERROR, review its formula or related-field configuration and save the field again.

Relationship Types define the names in both directions, which entities can be linked, and whether a relationship is visible in the portal. Select a specific Record Type when a side refers to custom records.

Customer processes

Configure Relationship Health Models to explain customer health through rules, score bands, and suggested next actions. A suggested action can create a follow-up task; it does not change customer data automatically.

Configure Lifecycle Definitions to guide customers through stages. Stages can require information, documents, tasks, or approvals before moving on. Use Handoff Templates to define the information and acceptance needed when responsibility changes.

Configure Relationship Review Templates for repeatable customer check-ins. Choose the customer types, sections, source views, optional cadence, and any follow-up required before closure. See Customer workflows for using these processes.

Remove or archive configuration

Remove field archives a field from active use. Check dependent forms, views, and automations first; calculated values may be cleared. Dependency errors explain what must be resolved.

Deleting a View or Layout permanently removes that configuration, not the customer records. Remove references from defaults and templates first.

Record Types, Relationship Types, Health Models, Lifecycle Definitions, Handoff Templates, and Review Templates use Archive to preserve existing records and history. Review dependent workflows before archiving them.