CRM Setup

Workstation separates the definition of CRM data from the way that data is displayed. This makes it possible to add a field once, reuse it across forms and automation, and then choose where it appears on a record page.

The CRM configuration model

Area	What it controls	Where to configure it
Properties	Native fields, custom fields, computed values, validation, conditional logic, and groups	Settings → Properties
Objects	The cards, tabs, associations, and property placement on record pages	Settings → Objects
Pipelines	Ordered stages, stage colors, probabilities or open/closed categories, transitions, and stage requirements	Settings → Pipelines
Table Views	List columns, filters, sorting, saved tabs, and Kanban grouping	A module’s list page and Manage views

These areas work together but do not replace one another. For example, creating a Deal property makes the field available to the CRM. Adding it to a Deal property card in Objects decides where users see it. Adding it as a stage requirement decides when it must be filled.

Recommended setup order

1. Review the standard fields for Contacts, Accounts, Deals, and Price Offers in Properties.
2. Create the custom properties and groups your process needs.
3. Add validation and conditional logic while the data model is still simple.
4. Configure contact and deal pipelines, including stage order and rules.
5. Arrange the record experience in Objects.
6. Create shared and personal Table Views for daily work.
7. Import existing data after property internal names, types, and pipeline stages are stable.

Core CRM records

Contacts

Contacts are people and also carry the prospect lifecycle. Use contact status, owner, source, pipeline, stage, rating, and score to qualify a person before or alongside creating a deal. The legacy lead-conversion workflow is no longer the normal CRM workflow.

Accounts

Accounts represent companies or organizations. A contact can have a primary account and can also be associated with additional accounts. Accounts can be related to contacts, deals, tickets, appointments, projects, invoices, campaigns, price offers, and other records.

Deals

Deals represent active revenue opportunities. Every deal has a deal pipeline and stage. Deal stages can carry a probability and may be marked as the pipeline’s Won or Lost stage.

Price Offers

Price Offers are quotes with line items, pricing, approvals, PDF output, sharing, and signing. They can be associated with contacts, accounts, and deals. A price offer is useful before or during a deal, but it is not required to create a contact or deal.

Organization-wide and personal settings

Some CRM configuration affects everyone, while other settings are personal:

Configuration	Scope
Properties, groups, rules, and conditional logic	Organization-wide
Pipelines, stages, and pipeline rules	Organization-wide
Default record layout in Objects	Organization-wide
Personal left/right record-card order, when allowed	Per user
Saved private table views and standard-tab overrides	Per user
Shared table views	Organization-wide visibility

Before saving a default object layout or changing a pipeline, review the change with the people who use that record type. Existing records use the updated configuration immediately.

Related administration

• Use Team and Departments for permissions and data visibility.
• Use Data Validation to decide between property rules, conditional logic, and stage requirements.
• Use Settings for imports, feature modules, integrations, currencies, products, and other workspace configuration.