Manage Pipeline Stages
Manage Pipeline Stages
Review and manage the shared pipeline stages used by your current PloverCRM workspace.
Open stage settings #
- Open PloverCRM.
- Tap Settings.
- Under App preferences, tap Lead Details.
- Tap Manage Stages.
Image placeholder: Replace this image path with the final Manage Stages screenshot when it is available.
Review stages #
Each stage can show its name, color, and the number of deals assigned to it. Use the up and down controls to review the current order.
If your role can view stages but cannot manage them, the screen is read-only.
Add a stage #
- Tap Add Stage.
- Enter a Stage Name.
- Choose a Stage Color or enter a valid six-digit hexadecimal color.
- Tap Add.
- Tap Save Changes.
At least one stage is required. Stage names must be unique.
Edit a stage #
- Tap the edit control for the stage.
- Update the Stage Name or Stage Color.
- Tap Update.
- Tap Save Changes.
Renaming a stage can update the stage name associated with existing deals.
Reorder stages #
- Tap the up arrow to move a stage earlier in the list.
- Tap the down arrow to move it later in the list.
- Continue until the stages are in the order you want.
- Tap Save Changes.
Delete a stage #
- Tap the delete control for the stage.
- Review the confirmation dialog.
- Tap Delete only when you are certain.
- Tap Save Changes.
Warning: Deleting a stage changes shared pipeline settings. A stage assigned to deals cannot be deleted. Move those deals to another stage first.
PloverCRM can show Stage In Use and identify the deals that must be moved before deletion.
Troubleshooting #
Manage Stages is unavailable
Your role may not have access to shared stage settings. Ask your workspace administrator to review your permissions.
A stage cannot be saved
Make sure at least one stage remains, every stage has a name, and no two stages use the same name.
A stage cannot be deleted
Move the assigned deals to another stage first, then return to Manage Stages and try again.
Changes are not visible elsewhere
Tap Save Changes, wait for the success message, and refresh workspace data before checking another screen.
