Nearly everything your team sees is configurable under Settings. The
highlights, by what they shape:
Fields & records
- Custom fields — per object (leads, deals, customers, accounts):
text, number, email, phone, date, textarea, dropdown, multi-select,
checkbox, radio, and rich text. Built-in fields can be hidden or made
required per object.
- Duplicate check — enable per object and pick the matching fields; the
create forms then block duplicates.
- Custom objects — Settings → Objects is the registry of everything
in your CRM: system objects (always on), optional pre-built objects you can
activate in one click, and fully custom objects you create with a wizard —
each getting its own pages, fields, statuses, and permissions.
Pipeline behavior
- Lead statuses and deal statuses — your own stages, each with a
color, ordering, and optional pre-condition fields required to enter the
stage.
- Deal priorities, deal weightage (the forecast percentage per
stage), and reasons of lost.
- Lead scoring — assign a weight to each field; a lead’s score is the sum
of weights for the fields it has filled. Set an optional max score and
recalculate all leads anytime.
- Lead & customer tags — rule-based: define conditions (equals, contains,
date windows, and more, combined with and/or groups) and matching records
tag themselves.
Catalog & operations
- Product Types and Products — the catalog deals draw from.
- Sources — where leads and deals come from.
- SLA Policies — response times and escalations.
- Task Types, Task Outcomes, and Activity Types — the vocabulary
your team logs work with.
Start light: rename entities and add the few custom fields your process
can’t live without, then grow the configuration as real usage shows what’s
missing. Every list here can be changed later without losing data.