PYLO Settings: Workspace
Pipelines
Make pipelines and their stages, rename and reorder them, flag stages won or lost, choose each card's value, and map Close or GoHighLevel stages.
Pipelines are the stages your leads move through on the Pipeline board.
Who can open it
Owners and admins.
The two default pipelines
Lead status and Opportunity are every lead's own status and opportunity stage. You can rename their stages and change their order, which changes how they read on the board. You cannot add or remove their stages or change which ones count as won or lost, because the rest of PYLO (the dashboard, commission, workflows) reads those values.
Your own pipelines
New pipeline takes a name, whether it tracks leads (cards belong to the setter) or deals (cards belong to the closer), and its stages, one per line. A stage called Won or Lost is flagged so, and you can change any flag afterwards.
On each pipeline you can:
- rename it, and choose whose card each lead is: the setter, the closer or the SDR;
- choose a money field as each card's value, which gives every column its total (add one under Custom fields);
- rename stages, move them up and down, flag each open, won or lost, and add new ones;
- archive a stage nobody is in, or bring it back. A stage still holding leads cannot be archived until they are moved; a stage is never deleted, so its history keeps its meaning;
- archive a whole pipeline once it is empty.
Nothing saves until you press Save. If PYLO refuses a change, the reasons are listed on the card.
Close and GoHighLevel
For a workspace that stays on its own CRM, map what it holds onto PYLO:
- Close: a lead status, written exactly as Close shows it, onto a stage of one of your pipelines; a Close custom field, by its name, onto a PYLO field.
- GoHighLevel: an opportunity stage, by its id, onto a stage; a custom field, by its id, onto a PYLO field.
From then on a Close import places each new lead at the stage its status maps to, and GoHighLevel's sync and import do the same as leads arrive. A mapped field is filled only when PYLO holds nothing for it, so a value someone typed in PYLO is never replaced. With nothing mapped, imports and syncs work exactly as before.
What reps can change
Reps can move their own leads between stages and edit custom fields on their own leads is off until an owner or admin turns it on. A lead is a rep's own when they are its setter, closer or SDR. With it off, only owners, admins and ops change a lead's stage or its custom fields. Either way, leads someone else owns, and reassigning leads, stay with owners, admins and ops.