Settings → Roles & Access → Lead visibility lists every lead-owning member with a scope selector: Own leads only (the default), Selected reps (pick which other reps they can also see — a sales manager over a subset), or All leads. Admins are shown as a non-editable Sees all leads row because they never need a policy.
Also called: rep can only see their own leads · sales manager sees everything · hide leads from other reps
- 1Each row edits a draft; Save is explicit and per-row so narrowing someone's visibility is never silent.
- 2Policies are stored per (organisation, user) with scope and the list of visible users.
- 3Server enforcement lives behind /api/lead-visibility/me; this tab is the admin editor.
- 4The table is registered admin-only and org-scoped in the database proxy, and the organisation id is stamped server-side.
- 5Load failures are distinguished: a 403 means you are not an admin, a 429 means rate limiting with a Retry, anything else offers a retry hint rather than an empty board.
The library comment sets the semantics — own is the default and is stored explicitly so it is visible in the UI rather than implied by an absent row. Explicit per-row saves exist because 'a destructive scope narrowing is never silent': taking leads off a rep's screen without them realising is worse than the setting being one extra click.
- Lead visibility was all-or-nothing.
- There was no middle ground between own leads and every lead.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →