Every client, their own platform.
Give each client an isolated, branded learning platform on their own domain, and run all of them from one console.
A live demo: agents find the team's skill gaps in a policy document and build a course that closes them, every module cited to its clause. A reviewer approves it, then each learner gets it in their own format.
- Custom domainTheir address and their certificate, under their name.
- Theme tokensColors, logo, and typography set per tenant.
- Branded certificatesTheir seal on every credential issued.
- Scoped teamsClient admins never see each other.
From signed client to live platform.
The same three steps for every client: stand up their tenant, build the program from their own material, and hand it over.
What changed in the policyNoor · cutting chapters
Escalate a suspicious transferZaid · building the simulation
Reporting duties checkDana · writing questionsSwitch clients, and the whole platform rebrands.
Pick a client to see its admin view.
Every client runs the same release. Each tenant sets its own colors, domain, and access.
Branded per client
Each tenant has its own colors, logo, fonts, and domain, so clients see their own platform.
Set once per tenant. Nothing downstream (modules, emails, certificates) needs to know your agency exists.
Blueprinted from the client’s own discovery notes
Approve blueprint✓VerifiedTheir seal on every certificate
Each completion issues a certificate under the client’s brand that anyone can verify with its ID.
Discovery playbook · labs passed
Every client in one console, none able to see another.
Roles and scopes follow the client you pick. Each tenant's data and audit trail stay inside that tenant.
One console, every client
Switch tenants without switching tools: roles, scopes, and content per client from a single seat.
org: acme-academyfollowing the tenant you picked abovecontent.writeusers.manageprogress.readIsolated by architecture
Each client’s data, roles, and audit trail live in their own tenant, with no rows shared between tenants. Stream the audit log to the client’s SIEM.
One working week to a client platform.
The first client takes a week because you are learning their material. Pick a day.
Theme tokens, logo, and domain go in once and reach every screen the client’s staff see.
PUT /api/v1/admin/organization/branding/0199a3c4-…Automate the rollout.
Provision organizations, seats, and content through the API, and onboard the next client in an afternoon.
{ "name": "Globex Learning", "slug": "globex-learning", "description": "Client academy" }
{ "statusCode": 201, "data": { "id": "0199a3c4-…", "slug": "globex-learning" } }
The rest of the platform
Every workspace gets all of it.
Stages, prerequisites, and outcomes, sequenced by difficulty
An authoring wizard, timed runs, server-side grading
Points, badges, streaks, and verifiable certificates
Practice groups, events, polls, and module discussions
Achievements and certificates land the moment they are earned
Living reference pages attached to paths and modules
Chapters, cues, bookmarks, and notes on every video
A storefront for everything your organization teaches
What agencies ask first.
Does each client get a separate platform?
Yes. Each client is a tenant with its own domain, brand, content, roles and audit trail. You run all of them from one console on one deployment.
Can I reuse my catalog across clients?
Yes. The paths and modules you build are yours, so you can bring the same program to another client. It takes that client's brand, and anything specific to one client stays in that client's tenant.
Can one client's admins see another client's data?
No. Each tenant keeps its data, roles and audit trail apart, with no rows shared between tenants. A client's admins see only their own tenant, and the audit log can stream to the client's SIEM.
Whose name is on the certificates?
The client's. Each certificate carries the client's seal and a public ID anyone can check. Your agency's name appears nowhere the client's learners look.
How long does a new client take?
The first client takes about a working week, because you are learning their material. After that, creating the tenant is an API call, and the next client takes an afternoon.
Does it work in Arabic, on the client's own domain?
Yes to both. Arabic gets a full right-to-left layout, 30+ languages are supported, and every tenant serves from the client's own domain.
Show your next client their own platform.
Book a demo. We walk through a client tenant, its brand, its certificates and the rollout week, using your sector as the example.
One deployment · isolated tenants · Arabic and English