CRM > Configuration links the administration screens permitted by your role and subscription. Pipeline administration and general CRM configuration have separate permissions. Creating or changing configuration still checks current purchased features and capacity.
Pipelines and stages
Create pipelines and their stages when the pipeline feature permits it. A stage has an order, open/won/lost category, probability, required fields and optional approval requirement. Approval-required stages also need the approvals feature. Review how the stage affects existing deals before changing it. Required fields is a searchable multiple selection of supported deal attributes and permitted active deal custom fields in the current company. Choose up to 20 requirements. A false boolean or a numeric zero is a supplied value; missing required information prevents entry into the stage.
Map populated stage previews the deals moving from a retiring stage to its replacement. The preview checks the replacement stage's required information before offering confirmation. Review the displayed versions and confirm the mapping. Changed deals, stage configuration or pipeline configuration need a fresh preview; returning to a different company also requires a new preview. Both stages must belong to the same pipeline, and a review contains at most 500 deals. For a larger stage, use normal reviewed deal edits to reduce the remaining population before mapping the stage. Normal deal transitions still require their applicable loss or reopening information. Historical stage information is retained. When the effective pipeline allowance is one, Select retained pipeline chooses the usable retained pipeline rather than deleting the others. Existing retained data does not authorize creation of additional pipelines.
Custom fields and modules
Custom fields defines typed values for contacts, organizations, deals and custom records. Choose a stable field key, type and choice options or relationship target as applicable. An existing definition's entity, key and type cannot be changed; retire it and create a new definition when its meaning changes. Turn on Required value when new records must supply this field. Required text, number, date, boolean and choice values still use their type validation: false and zero are valid supplied values, while blank or missing required values are rejected. Adding a requirement does not invent values for historical records or block an unrelated edit to an untouched historical gap. Changing that field must satisfy the current requirement. An untouched historical missing answer stays missing, including an unknown boolean; explicitly supplying false records a false answer. A deal must still satisfy its destination stage's requirements when moving stages.
Field retirement preserves existing values; retired fields cannot receive new values or changes. Downgrading preserves permitted read/export access and ordinary retained-record edits, while unavailable custom-field enrichment pauses. Active field allowances are per entity and shared across the tenant's company workspaces. Reusing a field key in another company does not create extra capacity. Field-security features can add read and write permission restrictions; they do not grant permission to related records.
Custom modules defines a named module's fields, required values, choices, relationships and one-, two- or three-column layout. Custom records selects that module and presents its supported fields. Keep keys stable and review relationship targets. Module definitions and custom records use distinct finite allowances; creating a module does not include unlimited records or authorize cross-company relationships.
Territories
Territories defines rules matching currency, owner or organization. All configured rules must match. Lower priority values take precedence, with record ID resolving ties; each deal is counted once. Rule recommendations do not apply owner changes automatically. Use Sales Analytics to review and apply current assignments with the required permissions.
Replacement scorecards
Replacement Scorecards records the customer's actual replacement requirements. For each workflow, mark supported, accepted workaround or blocking gap and provide evidence. A required blocking item or missing evidence prevents a ready result. Record an outcome review where appropriate.
A scorecard records reviewed evidence; it does not enable a feature or certify that imports, providers, operational automation, mobile workflows or every replacement requirement have passed. Verify the customer's required workflows and acceptance evidence before treating the workspace as ready.
Core MVP versus advanced configuration
A configured capability, a staff role and an enabled release surface are three separate requirements. The core MVP deliberately masks advanced administration and automation where configured. Do not promise quotes, territory assignment, custom modules or provider-backed email/calendar merely because this guide describes their implemented screens. Verify the tenant's actual release scope and acceptance evidence through CRM operations.
Staged advanced releases
Your workspace may enable advanced CRM in stages: Growth and intelligence; Sales-to-service; then Connected productivity. These product release stages are separate from subscription plan names. Growth and intelligence includes configured pipelines, custom fields, reports, forecasts, follow-up automation and AI where your subscription and role permit them. Later stages introduce quotes, approvals, sales sequences, onboarding and additional connected-productivity features.
An operator can pause sequences or onboarding separately from basic reminders. A paused report cannot be run or freshly exported through an already open page. Workers and prepared automation email check their initiating feature again before proceeding. Existing records remain stored; retained review and stop operations continue to follow their current permissions.
The accepted Zoho integration can remain explicitly enabled while a later stage is restricted. This does not expand the fields synchronized by that connector. Custom modules and territory planning remain separate, deferred scopes. Feature availability still depends on current release settings, subscription capacity, staff permission and record access; a stage name never grants those permissions.
Workspace layout
Configuration lists and forms share the compact CRM workspace styling. Current actions, permitted fields, stage-mapping review and effective plan limits remain unchanged. A clearer layout does not grant additional configuration access.
Continue with the configured workflow
After configuring stage requirements, follow Quotes and approvals for controlled sales decisions. Follow Sales automation for sequences and onboarding, and Reports and forecasts for saved report definitions. Review the migration matrix before mapping external definitions into the workspace.