Skip to main content
The Lead Stages screen is an admin interface for creating and reordering lead pipeline stages. The primary route is /ce/settings/lead-stages; an alternate route /ce/lead-stages also resolves to this screen.

​
Overview

The Lead Stages screen displays all configured pipeline stages in a draggable list via LeadStageEditor. Users can drag and drop rows to reorder stages; the description states “Leads will progress through these stages in order.” An Add Stage button opens LeadStageFormDialog for creating a new stage. A back arrow navigates to /ce/settings. The page shows a loading skeleton while stages are fetched and an error state if the fetch fails.

​
Who it’s for

Required permission: ce.leads.admin (route-level gate at /ce/settings/lead-stages).

​
Before you start

  • You need the ce.leads.admin permission.
  • Stages are scoped to your organization.

​
Steps

1

Open Lead Stages

Navigate to /ce/settings/lead-stages from CE Settings, or directly via the alternate route /ce/lead-stages.
2

Review current stages

The Pipeline Stages card shows all configured stages in their current order.
3

Reorder stages

Drag and drop stage rows to change the pipeline order.
4

Add a stage

Click Add Stage to open the stage form dialog. Enter a stage name and any other required fields, then save.
5

Edit or delete a stage

Use the actions available in the LeadStageEditor to modify or remove a stage (SME: confirm available row actions).

​
Key concepts

  • Stage order — leads progress through stages in the order shown; reordering affects the pipeline progression path.
  • Stage color — displayed on lead records as a badge border color.

Community Engagement

Community Engagement core overview.

Governance & parity

Documentation coverage and governance.
This page documents shipped product behavior. It is not medical, legal, or billing advice. Verify against your organization’s policies and applicable regulations before using it for clinical, compliance, or billing decisions. Protected health information (PHI) shown in the product is governed by your tenant’s access controls and is never exposed in this documentation.
  • src/routes/ce.tsx
  • src/cores/ce/pages/LeadStagesPage.tsx