Source · CMS snapshot (seed) — this guide body is served fromcontent/generated/cms-snapshot.json, not the code catalog alone. Staff path: Content Studio (:3030/experience/sites) → publish guide →MCV_CONSOLE_URL=http://localhost:3030 pnpm --filter @mcv-tech/marketing-shell content:seed→ rebuild:3050. Offline:MCV_CMS_SNAPSHOT_FILE=… pnpm content:seed.
The outcome you are walking toward
A new brand placed correctly in the tenant hierarchy on the first pass: the right entities at the right levels, isolation boundaries where the contracts say they are, and no restructuring once locations and staff are live.
1. Start from the hierarchy, not the org chart
The platform models seven levels of organizational scope with one hard isolation boundary at the brand. Read multi-tenant architecture first — the walkthrough below assumes you know which level each of your entities belongs to.
2. Decide what is shared and what is isolated
Sign-on, the substrate, and the audit machinery are shared. Records are isolated per brand and the boundary fails closed at the database — you do not configure isolation per query, you declare it per entity. List every data class the new brand touches and mark it shared or isolated before onboarding anything.
3. Place regions and locations deliberately
Regions and locations nest under the brand. Put a location at the wrong level and reporting, grants, and royalty metering inherit the mistake. The cheapest time to fix the shape is before the first location exists.
4. Onboard through the governed path
Brand creation, role grants, and integration points are onboarding steps with their own gates — follow venture & brand onboarding rather than assembling the pieces ad hoc. Revenue splits come after the structure holds; billing & treasury splits is the reference when you get there.