Expert knowledge
The expert’s own matchable profile — what makes them findable for a lead. See Reading the tables for the conventions.
Capabilities
The self-profile is not modelled in the permission registry. It is gated by an explicit
persona check in the server action (resolvePersonaActionContext({ roles: ["expert"] })), because
an authentication-only gate would lose the guarantee that only the expert themselves writes these
fields. There is no permission to grant here, and editing a role template cannot open it up.
| Capability | Gate | Admin | CSM | SDM | Expert | Vendor | Customer |
|---|---|---|---|---|---|---|---|
| Read and edit one’s own knowledge profile | explicit persona gate — expert | ❌ | ❌ | ❌ | ✔️ | ❌ | ❌ |
| Progress the expert onboarding steps | explicit persona gate — expert | ❌ | ❌ | ❌ | ✔️ | ❌ | ❌ |
What the profile holds
Position and bio, seniority and years of experience, the industries served, skills with a
per-skill proficiency and years, products, and structured availability (weekly capacity hours,
earliest start date, work mode). These are the datapoints expert matching filters and ranks a lead
against — products and availability decide who is matched, and the profile’s certifications,
industries, location, languages, CSAT and day rate decide the order. Managers see the result
through match.override and add to it through match.add, which is covered on the
Experts page.
Surfaces
| Page | Gate | Admin | CSM | SDM | Expert | Vendor | Customer |
|---|---|---|---|---|---|---|---|
/expert/my-knowledge | explicit — persona surface | ❌ | ❌ | ❌ | ✔️ | ❌ | ❌ |
/expert/onboarding | explicit — persona surface | ❌ | ❌ | ❌ | ✔️ | ❌ | ❌ |
An admin does not reach this surface; to walk it, sign in as an expert seat on the demo host — see Roles → Seeing another persona’s view.