Many brands, one account, zero cross-contamination
Run training for every brand or business unit from a single account — each one fully isolated, with its own documents, knowledge, courses, and members.
Sound familiar?
- Each brand's content must never appear in another brand's training — and you need to prove it.
- Standing up a separate tool per brand means separate bills, separate logins, separate headaches.
- Downgrades and reshuffles risk destroying content someone still needs.
- Some units need a dedicated, walled knowledge base; others can share — and your tool forces one model.
Why this is worth fixing
Training Magazine projects $102.8 billion in 2025 U.S. training expenditures among organizations with 100 or more employees — and every brand that rebuilds the same onboarding, compliance, and product training from scratch pays for it again. Each tenant drafts from its own source, walled off from the others, without re-spending on the same work.
How Scormy One solves it
One billing account can run many isolated tenants — one per brand or business unit. A tenant's documents, knowledge bases, courses, members, and API keys live entirely inside it. No tenant can ever retrieve, search, or train over another tenant's data. Isolation comes from who you are, never from a URL someone could tamper with.
Each unit gets the model that fits: a shared knowledge base filtered by access, or a dedicated one walled off on its own. Abilities are set per tenant, so one brand can have capabilities another doesn't, even under the same account.
When plans change, nothing gets destroyed. Downgrades park resources rather than delete them — content stays safe and comes back when you upgrade. You decide what stays active; everything else waits.
Published training output
Multi-Brand Workspace Administration
An administrator course for keeping brand workspaces isolated and reducing seasonal capacity without deleting valuable training content.
Keep Brand Workspaces Separate
Choose the correct tenant before managing documents, courses, members, or access.
Choose the Correct Tenant
Administrators must confirm the brand and active tenant context before changing documents, courses, members, or access.
On screen: “Brand confirmed? Tenant confirmed? Then act.”
What should an administrator verify before adding a document or member?
- AOnly the billing account name.
- The administrator should verify the brand name and active tenant context.
- CWhether another brand already has a similar document.
- DThe date of the most recent account invoice.
Fictional example · Helio Group Workspace Governance Handbook
training-export.json
Pretty-printed export.v1 payload
{ "schemaVersion": "export.v1", "trainingId": "4c3d8b17-6e52-4dc7-8dc3-89c55926a701", "version": 1, "title": "Multi-Brand Workspace Administration", "language": "en", "status": "published", "publishedAt": "2026-07-21T13:15:00.000Z", "kind": "training", "hasQuiz": true, "synopsis": "An administrator course for keeping brand workspaces isolated and reducing seasonal capacity without deleting valuable training content.", "chapters": [ { "id": "aaf496df-0835-4713-9b0f-7d3b13bc7a11", "title": "Keep Brand Workspaces Separate", "summary": "Choose the correct tenant before managing documents, courses, members, or access.", "position": 0, "scenes": [ { "id": "8924ed2a-7e80-49db-8828-df338c58d121", "kind": "narrative", "title": "Choose the Correct Tenant", "position": 0, "summary": "Administrators must confirm the brand and active tenant context before changing documents, courses, members, or access.", "durationSeconds": 105, "narrative": "A multi-brand account gives each brand its own tenant. Before making an administrative change, confirm both the brand name and the active tenant context shown in the workspace. Do this before adding a document, inviting a member, publishing a course, or changing access.\n\nWork only with resources that belong to the selected tenant. A document for one brand should not be uploaded to another brand's workspace, even when the same administrator supports both teams. The same rule applies to courses, members, and access credentials.\n\nIf an expected resource is not visible, stop and re-check the tenant context. Do not search another brand's workspace to work around the problem. Confirm the request and switch only through the approved account controls.\n\nA reliable administration habit is simple: identify the brand, verify the tenant, then act. That short check keeps each team working inside its own boundary.", "onScreenText": "Brand confirmed? Tenant confirmed? Then act.", "plan": "roll-a", "mediaKind": "image", "generationPrompt": "Enterprise administration scene with a shared-services employee reviewing two clearly separated brand workspaces on a neutral dashboard, confirming the active tenant before adding a document; crisp professional office, fictional names, no real logos.", "sourceImages": [], "sourceChunks": [] } ] }, { "id": "37267844-f419-4139-98a5-ebcb4a9f4a32", "title": "Manage Seasonal Capacity Safely", "summary": "Park inactive resources during a seasonal reduction and restore them when capacity returns.", "position": 1, "scenes": [ { "id": "516cb571-5eed-4c2f-bbc9-a4eab4eabf22", "kind": "narrative", "title": "Park Resources Without Deleting Content", "position": 0, "summary": "During temporary capacity reductions, administrators should keep essential resources active and park lower-priority content so it can be restored later.", "durationSeconds": 110, "narrative": "Seasonal changes can reduce how much a tenant needs for a period, but temporary capacity decisions should not destroy long-term training work. Begin by reviewing which courses, knowledge resources, and team access must remain active during the reduced period.\n\nChoose the highest-priority resources first. Park lower-priority resources rather than deleting them. Parked content is intentionally inactive, but its structure and history remain intact for later use. Record the decision so the brand team knows what is active and what is waiting.\n\nWhen capacity increases again, restore the required resources through the approved controls. Confirm that each restored course opens correctly and that the intended team members can access it.\n\nThe safe pattern is review, prioritize, park, and verify. This keeps seasonal cost decisions reversible and avoids forcing a brand to rebuild content when demand returns.", "onScreenText": "Review · Prioritize · Park · Restore", "plan": "roll-b", "mediaKind": "broll", "generationPrompt": "Professional sequence showing an enterprise administrator reviewing a seasonal resource list, marking lower-priority training as parked rather than deleted, then restoring it later; clear separated workspace visuals, no company marks.", "sourceImages": [], "sourceChunks": [] } ] } ], "quizzes": [ { "id": "6756c928-c3e9-4b85-aa0c-7bb77f1b7441", "prompt": "What should an administrator verify before adding a document or member?", "type": "single-choice", "interactionType": "choice", "difficulty": "medium", "options": [ { "id": "ent-q1-opt-0", "text": "Only the billing account name." }, { "id": "ent-q1-opt-1", "text": "The administrator should verify the brand name and active tenant context." }, { "id": "ent-q1-opt-2", "text": "Whether another brand already has a similar document." }, { "id": "ent-q1-opt-3", "text": "The date of the most recent account invoice." } ], "position": 1, "correctAnswer": "The administrator should verify the brand name and active tenant context.", "correctOptionIds": [ "ent-q1-opt-1" ] }, { "id": "11a409f5-5ee4-467b-aeae-f89c2be1c442", "prompt": "How should lower-priority resources be handled during a temporary seasonal reduction?", "type": "single-choice", "interactionType": "choice", "difficulty": "medium", "options": [ { "id": "ent-q2-opt-0", "text": "Delete them permanently before reducing capacity." }, { "id": "ent-q2-opt-1", "text": "Move them into another brand's tenant for storage." }, { "id": "ent-q2-opt-2", "text": "Leave every resource active without reviewing priorities." }, { "id": "ent-q2-opt-3", "text": "Park the resources so they remain intact and can be restored later." } ], "position": 2, "correctAnswer": "Park the resources so they remain intact and can be restored later.", "correctOptionIds": [ "ent-q2-opt-3" ] } ]}Fictional example · Helio Group Workspace Governance Handbook
Before and after
| Before Scormy One | With Scormy One |
|---|---|
| One tool per brand — many bills, many logins | One account, many isolated tenants, one bill |
| Cross-brand content bleed is a real risk | Hard tenant isolation — data never crosses |
| Downgrades threaten content you still need | Park-don't-delete — content is paused, never destroyed |
| One sharing model forced on every unit | Shared or dedicated knowledge bases, per unit |
| Same abilities everywhere | Per-tenant abilities — each brand configured its own way |
Which capability solves which problem
| The problem | The capability that solves it |
|---|---|
| Brands must stay separate | Tenant isolation — fully walled-off tenant per brand or unit |
| Many bills, many logins | One account, many tenants — single billing relationship |
| Different needs per unit | Shared or dedicated knowledge bases, plus per-tenant abilities |
| Downgrades destroy data | Park-don't-delete — resources paused and restored, never lost |
| Service-to-service automation | Master key per tenant — rotate on Enterprise |
| Access must fail safe | Auth-derived context, fail-closed — deny when uncertain |
| Security & vendor review | SOC 2 Type II compliance on Enterprise |
What this looks like in practice
In practice
A holding company runs three retail brands. In Scormy One, each brand is its own tenant under one account: separate documents, separate knowledge bases, separate teams. The shared services group authors brand-specific training inside each tenant, and no brand's content is ever visible to another. When the company trims one brand's plan for a quiet season, that tenant's courses and knowledge are parked — fully intact — and snap back the moment the plan is restored. One invoice covers all three.
One account. Every brand, walled off.
Enterprise plans add dedicated knowledge bases, master-key rotation, and SOC 2 Type II compliance. Let's map your brands to tenants.
15-day Growth-tier trial · $10 in AI credit · no card to start.