Continu Extend is the way you give partners, customers, and vendors their own learning experience — running on Continu, but branded as yours or theirs. Each Extend portal has its own login page, content library, users, and analytics. This article covers what Extend is, when to use it, and how it fits with your internal Continu instance.
What Extend is
Extend creates white-labelled enablement portals for audiences that aren’t your employees. Each portal is configured independently — its own brand, its own users, its own content, its own reports — but everything runs on the same Continu instance you use internally.
The portal experience looks like the brand whose audience it serves: your brand, your partner’s brand, or a co-branded mix. Learners signing in don’t see Continu’s logo or interface. They see a learning environment built for them.
Behind the scenes, your admins manage every portal from one Continu admin console. You don’t need separate logins, separate billing, or separate platforms.
When to use Extend
Use Extend when you need to train an audience that isn’t on your payroll — and where mixing them with your internal employees would compromise content scope, branding, reporting, or compliance.
Common Extend scenarios:
- Customer education — onboarding customers to your product, ongoing enablement, certification programs
- Partner enablement — channel partners, resellers, system integrators who sell or implement your product
- Vendor training — contractors, third-party support teams, or service providers who need to learn your processes
- Franchise operations — operators of franchise locations who need consistent training under your brand
- Multi-brand parent companies — a single parent training employees across multiple sub-brands, each with its own portal
When Extend is not the right fit: a single small group of external contractors who only need access to a handful of internal courses. For that, use the External User role inside your main Continu instance — it’s lighter weight and doesn’t need its own portal.
The portal model
Each Extend portal is a logically independent learning environment with its own:
- Login page and URL — hosted on its own domain or subdomain (e.g., learn.yourpartner.com)
- Brand — logo, colors, fonts, cover images
- User population — separate from your internal user list; the same person can exist in multiple portals without cross-contamination
- Content library — each portal gets its own; content can be shared across portals or kept exclusive to one
- Reports and analytics — segmented per portal so the data for each audience stays clean
Critical isolation rule: external users in a portal never see internal content, internal users, or analytics. The audience scoping is enforced at the portal level, not just by Smart Segmentation rules.
What each portal includes
| Capability | What it does |
|---|---|
| Custom branding | Logo, colors, fonts, cover images per portal — each portal looks like the brand it serves |
| Custom domain | Host each portal on its own domain or subdomain for a fully branded experience |
| Independent user management | Separate user lists, roles, and permissions per portal — no overlap with internal |
| Content library per portal | Each portal has its own; share content across portals or keep it exclusive |
| Portal-level analytics | Engagement, completion, certification status tracked per portal and per learner |
| Multi-language support | Serve content in multiple languages per portal, manually or automatically translated |
| Smart Segmentation | Applied at the extend account level — users inside an extend account inherit the segmentation set on the account itself |
How users get into a portal
Admins add users to an Extend portal through manual invite or bulk upload. For individual or small populations, invite users directly from the portal admin. For larger populations, upload a CSV with the user list and the portal will provision accounts and send invitation emails.
Once a user is in the portal, the same user lifecycle rules apply as in your internal instance — suspending, reactivating, role changes, and audience attribute updates all work the same way.
Content flow
Content lives in the portal it was created or assigned to. There are three patterns:
Portal-exclusive content. Content created inside a portal stays inside that portal. Most customer-facing content (product training, certifications specific to one offering) sits here.
Shared content across portals. Some content makes sense across multiple portals — for example, foundational courses you want every partner and every customer to take. Share it once; updates propagate to every portal it’s published to.
Internal-only content. Internal training never crosses into Extend portals. The isolation rule is enforced at the platform level.
Audience scoping is set on the extend account itself, not on individual users inside it. Every user in an extend account inherits the same segmentation. If you need different audience scopes for different cohorts of external users, build a separate extend account for each cohort.
How segmentation works in Extend
Segmentation in Extend behaves differently from segmentation inside your internal instance, and getting this right at design time saves rework later.
Segmentation is applied to the extend account, not to users inside it. The audience rules you build sit on the extend account itself. Every user inside that account inherits the same segmentation — you can’t further split users within a single extend account into different scopes.
If you need different scopes, you need different extend accounts. A partner program with three tiers (Gold, Silver, Bronze) where each tier should see different content needs three extend accounts, not one extend account with three audience segments.
Build the segmentation rules inside the extend account. Audience rules are configured from within the extend account’s admin, the same way Smart Segmentation works inside your internal instance — just scoped to that one account.
This model keeps the data isolation guarantee clean: because every user in an extend account inherits the same scope, there’s no risk of one external user accidentally seeing content meant for a different external population.
Reporting on Extend
Each portal has its own reporting scope. Open the Reports area inside a portal and you’ll see:
- Active learners
- Completion rates by content
- Certification status
- Engagement trends
- Audience-level cuts (by partner tier, customer segment, region)
The same standard report types you use for internal training (completion, learner activity, content performance) are available per portal. Cross-portal roll-ups for executive views are also available — useful for “how many learners have we trained across the whole external ecosystem this quarter” questions.
Extend vs External User role — when each applies
These two concepts are easy to confuse:
| Question | Use the External User role | Use Extend |
|---|---|---|
| How many external users? | A handful to a few dozen | Hundreds, thousands, or more |
| How separate from internal? | They sit in the same Continu instance, scoped by audience rules | Fully isolated portal with its own login |
| Branding requirements | Your standard Continu branding is fine | You need a branded experience (yours or theirs) |
| Reporting needs | Mixed with internal reports, filterable | Separate reporting per portal |
| Typical use | A few partner reps embedded in internal training | A full partner enablement program with its own portal |
If you’re not sure, your CSM or implementation lead can help size the decision against your roadmap.
Setup overview
Setting up an Extend portal involves:
- Scoping — who’s the audience, how many learners, what content do they need, what brand do they sign in to
- Domain setup — purchase or repoint a domain/subdomain to the portal; IT-level work
- Branding — logo, colors, fonts, cover images uploaded to portal settings
- Content publishing — push existing content or build new content into the portal’s library
- User provisioning — load the initial user list (CSV upload or manual invite)
- Pilot — launch with a small subset before opening to the full audience
Most Extend launches are scoped and built with implementation support, not solo. If you’re considering an Extend portal, talk to your CSM early — there are decisions that are much cheaper to make right at scoping than to fix after launch (most notably: portal-by-portal user ID strategy and content sharing scope).
Common pitfalls
| Pitfall | Symptom | Fix |
|---|---|---|
| Treating Extend like the External User role | Audience grows past a few dozen and reporting/branding gets messy | Plan Extend portals from the start when external audience is sizeable or needs distinct branding |
| Sharing content across portals without thinking about updates | Updating one piece of content unexpectedly changes what learners see in multiple portals | Decide per piece: exclusive to one portal, shared across, or internal-only — and document it |
| Reporting at the wrong level | “How many partners completed Course X” is hard to answer because data is spread across the Continu admin and the portal | Use portal-level reports for portal-specific questions; use cross-portal roll-ups for executive views |
| Multi-language portal without a translation plan | Portal launches with English content only and bilingual learners disengage | Decide language scope at design time; plan whether translations are manual, AI-assisted, or contributor-driven |
See Also
- External Users — for the lighter-weight External User role used inside your main Continu instance
- User Management: Who Has Access to What, and Why — for how user roles work in Continu
- Smart Segmentation: Designing Populations That Maintain Themselves — for the audience rule engine that runs inside each portal
- Provisioning and Sync: How User Data Flows Into Continu — for the broader user lifecycle model
- How Continu Works — for the foundational platform overview