Client-Branded Portals: Running Separate Environments for Enterprise Accounts
A client branded learning portal is the point at which a training provider stops looking like a supplier and starts looking like part of the client’s own infrastructure. It is also the point at which operational complexity multiplies, because four clients means four domains, four sets of branding, four reporting cadences, and four data boundaries you must be able to demonstrate. Getting the pattern right early, including how the AI Coach is scoped per portal, is much cheaper than untangling it at eight clients. Key Takeaways 🖥️ Sign In to Access Your Dashboard What Each Client Portal Needs Five layers, and they are configured separately per client. Domain: Either a subdomain of yours (acme.yourfirm.com) or a subdomain of theirs (learning.acme.com) pointed at your platform. The second reads better to their employees and requires DNS cooperation from their IT team, which is worth requesting during onboarding rather than after launch. Branding: Their logo, colours, and login screen. This is the easy layer and the one demos focus on. Sender identity: Enrolment and reminder emails should come from an address their learners recognise. This requires SPF, DKIM and DMARC alignment against whichever domain sends. Get it wrong and your reminders land in spam, which silently destroys completion rates. Content scope: Which courses this client can see. Usually a subset of your library plus anything built specifically for them. Reporting: Their cadence, their format, their metrics. Different clients want different things, and standardising this early saves considerable time later. Data Separation You Can Actually Demonstrate Enterprise procurement will ask how you guarantee their learner data is not visible to other clients. “It is configured correctly” is not an answer that survives a security review. What they want to see: Write these five answers once, keep them current, and attach them to every proposal. Providers who assemble this per deal lose weeks. Question Weak answer Answer that passes review How is data separated? Each client has their own portal Row-level tenant isolation enforced at the query layer Who can see across clients? Only admins Two named roles, all cross-tenant access logged What happens on exit? We delete it Full export within 14 days, deletion within 30, confirmed in writing SSO Is the Adoption Lever In enterprise accounts, whether learners must remember a separate password largely determines whether they log in at all. Single sign-on against the client’s identity provider removes that friction. It is also the most common reason a launch slips, because it requires coordination with an IT team that has other priorities. Raise it in week one of onboarding, not week five. Practical notes. Most enterprise clients in the GCC use Microsoft Entra ID or Okta, and SAML 2.0 covers the majority of cases. Ask early whether they require just-in-time provisioning, since that changes how enrolment works. And always keep a non-SSO fallback for contractors and external learners, who frequently sit outside the client’s directory. 📄 Generate a Free PDF Sample Course in Your Cloned Voice Build a Launch Template The first portal takes weeks. The fourth should take a day, and it only will if you templatise. Your template should cover: DNS records to request, branding assets to collect, the SSO information checklist, default course scope, the reporting schedule, and a test plan. Package it as a single onboarding document you send the client’s IT contact at kickoff. The test plan matters most. Before any client portal goes live, verify: login via SSO and via fallback, an enrolment email arriving in the inbox rather than spam, certificate generation with the correct branding, a report export containing only this client’s learners, and the mobile experience. Those five catch most launch failures. The wider implementation arc is set out in what happens in the first 30 days. The Support Load Across Portals To be clear about scope: Vocaliv is not your system of record. Learner accounts, enrolments, and completion evidence stay in your LMS, and tenancy separation is a property of that system. What changes is the per-portal support burden. Four portals normally means four support queues, and that is where the margin on a multi-client model disappears. Where content questions resolve without an instructor, the queue that scales with client count stops scaling. Course content is shared across portals from a single source, so an update propagates rather than being repeated four times. For a provider running four client portals, 300 learners Metric Before After Time to launch a new client portal 3 weeks 1 day Support tickets per week across portals 45 14 Course update effort across portals 4 times Once Data separation evidence for procurement Assembled per deal Standing document Launching a Client Portal in Six Steps Frequently Asked Questions If you are about to launch your second client portal, build the template now. Doing it at the fourth means redoing the first three. 👉 Book a Live Platform Demo with an EdTech Expert
White Label Training Platforms: What You Own, What You Rent, and What You Cannot Move
A white label training platform lets you deliver training under your own brand on infrastructure you did not build, and the commercial logic is obvious. Your client sees your name, your domain, your colours, and never learns who runs the system underneath. Whether you run that delivery through the AI Course Builder or another engine, the split that decides whether the arrangement holds up three years in is less obvious: what you own outright, what you rent month to month, and what quietly cannot leave with you at all. That last category is where training providers get caught. Key Takeaways What a White Label Training Platform Actually Covers Vendors use the term loosely, so it pays to itemise. In practice, a white label arrangement covers some or all of the following: The test for each is simple. Would a learner, or a procurement officer at your client, encounter the vendor’s name anywhere in normal use? Email headers and PDF metadata are the two places it usually leaks. What You Are Renting, Not Owning This is the part that gets skipped in demos. You are renting the runtime. The platform, the model layer, the hosting, and the update cycle belong to the vendor. Your access ends when the contract does. That is not a flaw, it is the deal, and it is why the price is what it is. The problem appears when a provider builds a client-facing promise on a capability they do not control. Here is a concrete version. You sell an enterprise client on Arabic voice delivery across their onboarding programme. Your vendor changes voice providers, the available Arabic voices change, and your client notices. You carry the relationship risk. The vendor carries none of it. Contracts rarely address this. Ask what notice you get on a material capability change, and get the answer in writing. What Cannot Move At All Three things typically do not survive a migration, regardless of what the export button suggests. Configuration: Learning paths, branching rules, assessment logic, and role permissions are expressed in the vendor’s data structures. An export gives you a file. It does not give you a system that behaves the same way elsewhere. Budget rebuild time, not import time. Analytics history: Raw event logs are sometimes exportable. The computed views on top of them almost never are. If you have shown a client a completion trend for two years, that trend does not follow you. Generated assets and voice models: Where content, audio, or a cloned instructor voice was produced inside the platform, the output file may be yours while the underlying model is not. Ask specifically whether you retain a licence to assets already generated after termination. That is a different question from whether you can download them, and it connects directly to the consent and licensing issues around cloned instructor voices. Layer Typically portable Typically not Learner records and enrolments Yes, via CSV or API Nothing Course content and media Yes, as files Interactive structure Assessment items Yes, as text Branching and scoring logic Branding and domain You own the domain Theme configuration Analytics Raw events, sometimes Dashboards and trend history Generated audio Output files, usually The voice model itself Integrations Credentials are yours Field mappings and sync rules The Three Commercial Models Reseller: You sell the vendor’s product with your branding applied. The vendor typically retains some visibility into end clients. Margin is thinnest, setup is fastest, and your technical obligation is lowest. OEM: The platform is embedded in your offering and the vendor is contractually invisible. You hold the client relationship entirely and carry first-line support. Margin is highest, and so is your support cost. This is the model providers most often underestimate, because you become a software support desk whether you planned to or not. Co-brand: Both names appear. This helps when the vendor’s name carries credibility your firm has not yet built, which is common in early enterprise deals across the GCC where procurement teams want to know whose technology is running. Positioning is weaker long term, but the first sale is easier. White Label Training Platform Cost Structure Compared The pricing question that matters is not the monthly fee. It is where the per-learner curve crosses your revenue per learner. Cost element Reseller OEM Co-brand Platform fee Low to mid Highest Mid Per-learner overage Standard Negotiable at volume Standard Setup and configuration Minimal Significant Moderate Support burden Vendor You Shared Typical gross margin 30 to 45% 55 to 70% 40 to 55% Time to first client Weeks Months Weeks Run the model at three scales: pilot, first full enterprise contract, and your actual target. Arrangements that look identical at 80 learners diverge sharply at 800. Per-learner overage is usually the term with the most negotiating room. If you are still sizing deals, our breakdown of corporate training cost per employee in the UAE and Saudi Arabia gives the revenue side of the same equation. What Changes on the Support Side To be clear about scope: Vocaliv is not a reseller programme and does not manage your client contracts, billing, or commercial terms with end customers. Those stay with you. What it affects is the support load that determines whether an OEM arrangement is actually profitable. In an OEM model you carry first-line support for both the platform and the training content, which is two queues rather than one. Where learner questions about course material are handled by the AI Coach, the content queue shrinks and only genuine platform issues escalate. For a provider running four client-branded portals, 300 learners total Illustrative of the pattern described above, not measured results. Replace with your own platform data before publication. Metric Before After Support tickets per week 45 14 Tickets that are content questions 33 4 Instructor hours on learner support 22 7 Time to launch a new client portal 3 weeks 4 days How to Evaluate a White Label Agreement Because your client relationship depends on capabilities you do not control, that final