The lead board
What this page is — the kanban view of leads, one column per status, where dragging a card moves the lead through the pipeline.
What it is for — seeing progress at a glance and updating it by dragging, rather than opening records one at a time.
The problem it solves — "how is the pipeline doing?" answered visually. It also answers the question this screen generates more than any other: why is a lead missing from the board when the list can see it? There are three distinct causes and a decision tree for telling them apart.
Route: /org/marketing/leads?tab=kanban · Permission: View Marketing Suites lead management
1. What the board is
| Board | List | |
|---|---|---|
| Groups by | Status within one pipeline | Nothing — flat, newest first |
| Shows leads with no status | No | Yes |
| Shows leads from other pipelines | No | Yes |
| Changes data by dragging | Yes — writes the status | No |
2. What a card carries
| On the card | From |
|---|---|
| Name | full_name |
| Company | company_name |
| Contact handle | email or phone |
| Value | deal_value |
3. Step by step — moving a lead
- Choose the pipeline. The columns change to that pipeline's statuses.
- Drag a card to another column.
- The new status is saved immediately, and the change is recorded on the lead's activity timeline as a system entry.
Conversion rules can watch for a status change. Dragging a card into a converted status may create a contact or a deal — see convert to deal.
4. Why leads go missing from the board
This is the most common question about this screen, and there are three distinct causes.
If neither is supplied — by the API, the import or a webhook — the lead is given the project's default pipeline and its first status, so it appears on the board straight away.
Older leads created before that was true may still have neither. Those show in the list and not on the board; give them a status with bulk update.
Pipelines belong either to one project or to the whole organisation, and a lead can only be attached to one its own project can see. An attempt to save any other combination is refused.
Older data may still hold leads pointing elsewhere. If your board looks emptier than your list, that is the first thing to check.
A pipeline can be created and left without statuses. Selecting it produces a board with no columns at all and no explanation. See pipelines and statuses.
Diagnosing it
5. The admin contract
| Needs | Or |
|---|---|
| A pipeline visible to this project | No columns |
| That pipeline to have statuses | No columns |
| Leads that have a status | Empty columns |
| Edit Existing Leads | Dragging fails on save |
6. Downstream
A drag writes the status, which feeds the funnel report, can fire a conversion rule, and appears on the lead's timeline. It does not change the lifecycle stage — those are independent, see status, grade and score.
7. Don't confuse this with…
| This | Not this |
|---|---|
| The lead board — statuses | The deal board — stages, a different table |
| A status | A lifecycle stage |
| Column order | sort_order on the status, which is what sets it |
8. Troubleshooting
| Symptom | Cause |
|---|---|
| Board has no columns | The pipeline has no statuses, or none is selected |
| Board shows fewer leads than the list | Leads with no status, or a cross-project pipeline. Section 4 |
| A dragged card springs back | The save failed — usually missing Edit Existing Leads |
| A drag created a deal unexpectedly | A conversion rule watches that status |