Multi‑company administrator (MCA)
Multi‑company administrators exist for portfolio situations: Skilladder engagements where one steward must monitor or deploy artefacts across multiple customer organisations simultaneously.
Expect them to recognise:
Navigation highlights
| Menu | Reason they care |
|---|---|
Companies (/companies) | Canonical list across the portfolio slice they may access plus company detail drills. Adding companies may surface when entitlement allows provisioning. |
| Templates + Assessments | Deploy or duplicate artefacts from one organisation to others whenever product permissions expose those actions — especially template deployment modals surfaced on list pages or row actions for portfolio operators (verify per environment). |
| Dashboard (“Multi company”) | Different layout than isolated company dashboards: emphasises KPI rollups merging recent candidate activity stitched together from multiple organisational scopes; treat numbers as illustrative when demoing seeded data sets. |
Speaking points for internal demos
Highlight speed for managed service partners: fewer logins switching tenant accounts purely to monitor activity.
Operational caveats MCA teammates should reinforce:
- MCA permissions still respect explicit portfolio assignment gates — Skilladder admins wire who may see which subsidiaries.
- Row-level export rights follow the same granular rules applied to standalone company admins (do not infer export availability without validating test users).
See also
- Capabilities matrix — how MCA compares to company admins on each major sidebar entry.