Skip to Content

Experts

The expert as a person on the platform — the directory they appear in, the evidence they submit, and the scores they carry. Their own profile data has its own pages: Expert knowledge and Expert experience. See Reading the tables for the conventions.

Capabilities

CapabilityGateAdminCSMSDMExpertVendorCustomer
View the people on an engagementpeople.view✔️✔️✔️✔️ (own)
Add an expert to a lead’s match setmatch.add✔️✔️
Override the match rankingmatch.override✔️✔️
Rate an expert on a delivered leadexpert.rate✔️✔️
View CSAT scorescsat.view✔️✔️✔️✔️✔️ (own)
Submit a CSAT scorecsat.submit✔️✔️

Match curation is the SDM’s job, not the CSM’s — match.add and match.override are the only capabilities that split the two manager roles. Rating a delivered expert belongs to the vendor. Experts hold no csat.view of their own: their scores reach them through their engagement, not through the CSAT surface.

Surfaces

PageGateAdminCSMSDMExpertVendorCustomer
/users, /users/[id]explicit — full-tenant directory, staff only✔️✔️✔️
/expert-evidenceexplicit — the evidence review queue✔️✔️
/csatderived from csat.view✔️✔️✔️✔️✔️
/admin/usersexplicit — admin config surface✔️

There is no standalone experts table: experts appear in the tenant-wide user directory at /users alongside every other role. That directory renders full-tenant PII with no per-persona scoping, which is why it carries an explicit staff-only list rather than deriving from people.view. Submitted evidence is reviewed at /expert-evidence by admins and SDMs.

Creating and administering expert accounts — inviting them, changing their primary role, granting extra roles or per-user permissions — is an admin capability on the user detail page; see Roles → Admin.

Last updated on