Stage Settings

Pipeline Stages define the steps a deal moves through from initial contact to closure. Each stage has a name, color, icon, and behavioral flags that determine whether it is a starting default, a closed/won/lost terminal, or an on-hold state. Stages can be reordered by dragging and the order controls how they appear on the Pipeline board and the Deal Detail stage selector.

Accessing the Page

• Route: /settings/stages
• Menu Path: CRM → Settings → Stage Settings
• Primary audience: Users with stage management permissions.

What you can do here

• View all pipeline stages sorted by their display order.
• Create new stages with a name, color, icon, and behavioral flags.
• Edit existing stage properties (name, color, icon, flags, SLA).
• Delete stages that no longer have deals assigned.
• Drag and drop to reorder stages — the new order is saved automatically.
• Initialize a default set of suggested stages using the Initialize Stages wizard.

Stage list

Each stage row shows:

Element	Description
Drag handle	Grab to reorder (requires reorder permission)
Color dot	The stage’s hex color
Icon	The stage icon
Code	Short uppercase code (e.g., QLF) — set at creation, never editable
Name	Display name
Type badges	Default, Won, Lost, On Hold, SLA: N days
Edit button	Open the edit dialog
Delete button	Open the delete confirmation

Creating a Stage

Click Add Stage to open the Create Stage dialog.

Fields

Field	Required	Type	Description	Default	Validation
Code	Yes	Text	Unique short code — uppercase letters, numbers, and underscores	—	Max 20 chars; must be unique; auto-uppercased
Name	Yes	Text	Display name shown on the board and deal selector	—	Max 100 chars
Description	No	Textarea	Optional description of the stage	—	—
Color	Yes	Color picker	Hex color for the stage dot and card accent	—	Must be a valid #RRGGBB color
Icon	No	Icon picker	Lucide icon displayed alongside the stage name	—	—
Default stage	No	Checkbox	New deals are placed in this stage automatically	Off	Only one stage should be marked default
Closed stage	No	Checkbox	Terminal state — deals in this stage are considered closed	Off	—
Mark as Won	No	Checkbox	Shown only when Closed is checked — classifies the closed stage as Won	Off	Can only be set on closed stages
On Hold	No	Checkbox	Paused state — deals here are not counted as active (mutually exclusive with Closed)	Off	—
Enable SLA tracking	No	Checkbox	Turns on SLA monitoring for this stage	Off	—
SLA Days	Yes (if SLA enabled)	Number	Number of days before a deal triggers an SLA notification	—	Must be greater than 0

Code is set at creation and cannot be changed later.

Editing a Stage

Click the Edit button on any stage row to open the Edit Stage dialog.

Same fields as Creating a Stage, except:

• Code is read-only after creation.

Deleting a Stage

Click Delete on a stage row and confirm in the dialog.

1. Click Delete on the stage row.
2. The confirmation dialog shows the stage name and a warning that deals in the stage must be moved first.
3. Click Delete Stage to confirm.

Note: Stages with deals assigned cannot be deleted until those deals are moved to a different stage. The default stage shows an additional warning: set another stage as default before deleting.

Reordering Stages

Drag a stage row by its handle to a new position. The order is saved automatically when you release. The new order controls the left-to-right column sequence on the Pipeline board and the left-to-right order of stage buttons on the Deal Detail page.

Requires reorder permission.

Initialize Stages (wizard)

When no stages exist, the page shows an empty state with an Initialize Stages button. This opens a wizard that lets you choose from a set of pre-built stage templates:

Template Stage	Code	Type	SLA
New	NEW	Default	1 day
Contacted	CNT	Active	2 days
Qualified	QLF	Active	3 days
Discovery	DSC	Active	5 days
Proposal	PRP	Active	5 days
Negotiation	NEG	Active	7 days
Commit	COM	Active	3 days
Won	WON	Closed — Won	—
Lost	LST	Closed — Lost	—
On Hold	ONH	On Hold	—

Select or deselect individual stages, then click Create Selected Stages. Stages are created in the order shown.

Notes

• Each tenant should have exactly one Won stage (Closed + Is Won). Analytics and the pipeline closure column rely on this flag to identify won deals.
• Each tenant should have at least one Lost stage (Closed, no Is Won flag).
• Having multiple default stages is allowed but only the first in sort order is used when creating deals without an explicit stage.
• SLA notifications are triggered when a deal remains in a stage past the configured number of days without advancing.

Related Pages

• CRM Configuration — Global deal creation rules and code format
• Pipeline — See stages in action on the kanban board
• Deal Detail — Stage selector uses the configured stages