Leads
The service lead — from intake through requirements to the point it becomes an engagement. See
Reading the tables for the conventions, and
/admin/settings/scope in the platform for the live per-tenant answer.
Capabilities
| Capability | Gate | Admin | CSM | SDM | Expert | Vendor | Customer |
|---|---|---|---|---|---|---|---|
| View leads and the lead overview | lead.view | ✔️ | ✔️ | ✔️ | ✔️ (own) | ✔️ | ✔️ (own) |
| Edit the lead overview | lead.editOverview | ✔️ | ✔️ | ✔️ | ❌ | ❌ | ❌ |
| Assign a CSM to the lead | lead.assignCsm | ✔️ | ✔️ | ✔️ | ❌ | ❌ | ❌ |
| Assign an SDM to the lead | lead.assignSdm | ✔️ | ✔️ | ✔️ | ❌ | ❌ | ❌ |
| Qualify the lead out (manager only) | lead.qualifyOut | ✔️ | ✔️ | ✔️ | ❌ | ❌ | ❌ |
| Flag delivery for rework (manager only) | lead.flagRework | ✔️ | ✔️ | ✔️ | ❌ | ❌ | ❌ |
| Export leads | lead.export | ✔️ | ✔️ | ✔️ | ❌ | ❌ | ❌ |
| Archive the lead | lead.archive | ✔️ | ❌ | ❌ | ❌ | ❌ | ❌ |
| View the BRD | brd.view | ✔️ | ✔️ | ✔️ | ✔️ (own) | ❌ | ✔️ (own) |
| Flag the BRD as unclear | brd.flag | ✔️ | ❌ | ❌ | ✔️ | ❌ | ❌ |
| Sign the BRD off | brd.signOff | ✔️ | ❌ | ❌ | ❌ | ❌ | ✔️ |
| Add an expert to the match set | match.add | ✔️ | ❌ | ✔️ | ❌ | ❌ | ❌ |
| Override the match ranking | match.override | ✔️ | ❌ | ✔️ | ❌ | ❌ | ❌ |
| Rate the expert on a delivered lead | expert.rate | ✔️ | ❌ | ❌ | ❌ | ✔️ | ❌ |
| View the lead activity timeline | activity.view | ✔️ | ✔️ | ✔️ | ✔️ (own) | ✔️ | ✔️ (own) |
Approving the requirements is the customer’s act (brd.signOff), not a manager’s. Managers
read the BRD and can send delivery back with lead.flagRework; the expert raises a concern with
brd.flag when a BRD is too thin to bid on. Archiving is admin-only — the manager equivalent is
lead.qualifyOut, which records why the lead stopped rather than removing it.
Surfaces
| Page | Gate | Admin | CSM | SDM | Expert | Vendor | Customer |
|---|---|---|---|---|---|---|---|
/service-leads | derived from lead.view | ✔️ | ✔️ | ✔️ | ✔️ (own) | ✔️ | ✔️ (own) |
/service-leads/create | explicit — vendor lead sourcing | ❌ | ❌ | ❌ | ❌ | ✔️ | ❌ |
/service-leads/import | explicit — mirrors the import action | ✔️ | ✔️ | ✔️ | ❌ | ✔️ | ❌ |
/projects/create | explicit — the customer’s request form | ❌ | ❌ | ❌ | ❌ | ❌ | ✔️ |
/workspace/[id] | derived from lead.view | ✔️ | ✔️ | ✔️ | ✔️ (own) | ✔️ | ✔️ (own) |
/admin/demo-data | derived from tenantConfig.manage | ✔️ | ❌ | ❌ | ❌ | ❌ | ❌ |
A lead reaches the platform two ways, and each has its own form: a vendor sources one at
/service-leads/create (or in bulk at /service-leads/import), and a customer raises their own
request at /projects/create. Neither form is open to both. The demo-data tools that seed leads
are admin-only and reachable from the demo data tab of /admin/settings as well as
/admin/demo-data.