A pipeline shows the same entries two ways, and the toggle in the header switches between them. The choice sticks with the pipeline rather than with you, so switching changes what your colleagues see too.
One column per stage. Each column header carries the stage's colour, its name and how many entries are in it — that count is the whole stage, not just the cards currently loaded, so it stays right on a long board.
Drag a card to another column to move it. That's the main gesture, and everything else on the board is built around it.
If the pipeline has fields, cards show them and you can type straight into a card to set a value — no need to open anything.
Columns load more as you scroll, so a stage with hundreds of entries doesn't have to render at once.
The same entries as rows: Record, Stage, and a column for each field. Sort by any column, page through the results, and edit values in place — the same fields, edited from a different shape.
Use the board when you're moving work along and the table when you want to read across everything: who's stuck, what's in each stage, which entries are missing a value.
A field can carry a calculation — a sum, an average, a count. Where it does, the number appears at the bottom of each board column and under the table, so a stage tells you not just how many entries sit in it but what they're worth.
Click a card or a row and a panel opens on the right. It has its own URL, so you can send someone a link to exactly this entry.
At the top: the record's name, and whether it's a company or a contact. Open takes you to the full record. The overflow menu holds Remove from pipeline, which takes the entry off the board and leaves the company or contact untouched.
Below that, a stage strip: a progress bar across the stages, a dropdown to jump to any of them, and a shortcut to move to the next one. This is the alternative to dragging, and the only way to move an entry from the table view.
Then the detail, in order:
Details — this pipeline's fields, editable in place.
Company or Contact — what Gleap already knows about the record, plus any custom data it carries.
Tickets — conversations linked to this entry, with a New button to raise one. Done tickets are struck through, so a glance tells you what's still outstanding.
Activity — added, moved, fields changed, automations run. Anything an automation did is labelled as such, so you can tell your team's work from the system's.
Two shapes are worth watching for. A stage that keeps filling up is a bottleneck — usually a step that depends on someone outside the team. A stage that's always empty is a step that isn't real, and merging it into its neighbour makes the board honest again.
