How Continu Works
Follow

May 10, 2026 02:24

A foundational guide for anyone designing learning programs across their business ecosystem — customers, partners, channel, franchisees, contractors, members, and employees.

Why This Guide Exists

Most help articles teach you what to click.

This one teaches you how the system thinks — so you can think with it.

A learning platform is not a content library. It is the infrastructure for building capability across everyone whose performance shapes your business — your customers learning your product, your partners selling on your behalf, your channel certifying on your standards, your franchisees operating in your name, your employees executing your strategy.

To use Continu well, you need a model of what is happening underneath the interface. This guide gives you that model.

This guide is for you if:

You are designing a partner enablement program and need to onboard hundreds — or thousands — of external reps you don't directly employ.
You are running customer education, certification, or extended-enterprise learning at scale.
You are administering Continu and want to graduate from clicking through tasks to designing programs.
You are a learning leader making decisions about onboarding, capability, compliance, and culture across audiences inside and outside your organization.

Once you understand the model, every article in this help center stops feeling like a manual and starts feeling like a toolbox.

What Continu Is Actually For

Strip away the modules and the dashboards and Continu does three things:

It turns change in your ecosystem — a new partner activated, a customer onboarded, a product launched, a regulation updated, a hire made — into learning intent.
It moves that intent into the right learner's hands at the right moment, regardless of whether they sit inside your organization or outside it.
It tells you whether the learning landed.

The platform's real value is portability. Build a program once, deploy it across audiences — partner, customer, channel, employee — and measure it consistently.

If a feature is not helping you do one of those three things, you are probably overbuilding.

The Continu Model: Six Core Objects

At the architectural level, Continu organizes itself around six objects:

Users — every learner in your ecosystem.
Smart Segmentation — dynamic, attribute-driven population logic.
Content — the things being learned.
Assignments — the connection between a user and content, with intent and a due date.
Workshops — live, scheduled, attendance-tracked learning events.
Automations — the rules that turn ecosystem events into learning intent.

Reporting, notifications, integrations, dashboards — these are layers on top of these six objects.

If you can describe a learning program in terms of these six things, you can build it in Continu.

If you can't, you are not ready to build it yet.

Users — Every Learner in Your Ecosystem

Continu starts and ends with a user.

A user is more than a record. They are a person at a moment in their journey with your business — a partner rep new to your portfolio, a customer admin three weeks into onboarding, a franchisee operator preparing for an audit, a channel certification candidate, a vendor needing security training, an employee promoted into a new role.

Every attribute on a user record — tier, region, role, certification status, contract type, tenure, custom fields — is a potential lever for personalization.

Users come in through several doors:

Partner relationship management (PRM) systems, partner portals, or ecosystem platforms.
Customer systems and CRMs, for customer education programs.
HRIS provisioning, for internal audiences.
SSO-driven creation at first login.
Manual creation for edge cases.

The source of truth matters. If your PRM owns the partner, your PRM owns their attributes. If your CRM owns the customer, your CRM does. If your HRIS owns the employee, your HRIS does. Continu inherits whatever you feed it. Garbage in, garbage out. Clean data in, programs that adapt to change.

The strategic question: what does this learner need to know, do, or believe — given who they are, where they sit in your ecosystem, and what stage of their journey they are in?

Every other object in Continu exists to answer that question.

Smart Segmentation — The Lever

If users are who you are designing for, Smart Segmentation is how you scale that design across every audience you train.

Smart Segmentation is dynamic, attribute-driven population logic. You describe a population once — "Tier 1 channel partners certified in the last quarter," "Customers on the Enterprise plan who completed onboarding," "Franchisees in the Southeast region with a new managing operator," "Resellers eligible for advanced certification renewal" — and the segment maintains itself.

When a partner is activated, a customer signs, a franchisee changes ownership, a certification expires, a contract renews, a role changes — Smart Segmentation sees it and updates.

This is the most underrated capability in the platform.

Why Smart Segmentation is the lever:

One architecture, every audience. The same Smart Segmentation logic that powers your partner enablement program powers your customer education program powers your channel certification program powers your internal onboarding. Learn the model once. Apply it everywhere.
Programs become living things. New partners fall into the right enablement segment the day they're activated. Customers fall into the right education segment the day they sign. People who change tier, status, or role fall into the right segment the day the change happens.
You stop maintaining lists. Static lists rot — especially across external audiences where data changes constantly. Smart Segmentation does not rot.
Personalization scales. One segmentation rule can drive five automations, ten dashboards, and a notification cadence — and you only describe the population once.
Governance becomes possible. When Smart Segmentation is the source of truth, audits, certification verification, and partner-tier compliance reviews become straightforward.
Strategy survives change. Partner programs evolve. Customer cohorts shift. Reorgs happen. Smart Segmentation keeps your learning architecture intact through all of it.

Most program problems in Continu are segmentation problems in disguise. Get Smart Segmentation right and almost everything downstream gets easier. Get it wrong and no amount of automation will save you.

The strategic question: what populations — across your customers, partners, channel, and employees — do you keep returning to in your learning strategy? Define those with Smart Segmentation. Let the platform keep them current.

Content — The Raw Material

Content is what you build for people to learn from. Videos, articles, files, SCORM packages, external links, Tracks (sequenced collections), Journeys, and more.

Two things to internalize:

Content lives independently of who is assigned to it.
A single piece of content can be assigned to many audiences through many different programs.

This separation is the secret to scale. The same product training video can serve customer onboarding, partner enablement, and channel certification — with different surrounding context for each audience. You build something well, once, and reuse it across the ecosystem. The marginal cost of every additional learner approaches zero.

The strategic question: is this a reusable program asset, or a one-off communication? Build the first into Continu. Send the second through email.

Assignments — Where Intent Lives

An assignment is the connection point. It says: this learner should learn this content, by this date, for this reason.

Without an assignment, content sits in the library and never reaches the learner. Assignments are how learning intent becomes learning action — across every audience, internal or external.

Every assignment moves through a defined set of states:

Not Started — the assignment exists but the learner has not engaged.
In Progress — the learner has started but not finished.
Completed — the learner met the completion criteria.
Expired — the due date passed without completion.
Removed — the assignment was rescinded.

State is everything. Reporting is a read on state. Notifications are triggered by state. Stakeholder and program-owner dashboards roll up state. If you understand the states, you understand most of what the platform tells you.

The strategic question: is this a one-time push or a sustained program? The answer determines whether you assign directly or build an automation.

Workshops — Where Learning Becomes Live

A workshop is a live learning event with a date, a capacity, and an attendance record.

Workshops exist because some learning cannot happen alone. When discussion is the point, when facilitation is the value, when attendance has to be verified for certification or compliance — a workshop is the right object.

Workshops shine for partner certification sessions, customer office hours, channel kickoffs, franchisee training cohorts, and any program where seeing the learner show up is part of the value.

Use a workshop when:

The interaction is the value.
You need to know who actually showed up.
Capacity matters — room, instructor bandwidth, license seats.
Certification, accreditation, or compliance hinges on verified attendance.

Don't use a workshop when:

The content is static and self-paced.
A Track or assignment delivers the same outcome without scheduling overhead.

Workshops have their own state machine: Registered, Waitlisted, Attended, No-Show, Cancelled. Reporting interprets these. Get fluent in the states before scaling workshops across audiences.

The strategic question: does the value of this learning come from the people in the room, or from the content itself? Live learning is expensive. Spend it where it earns its keep.

Automations — Turning Ecosystem Change Into Learning

Automations are how the platform listens to your business.

An automation watches for a trigger — a partner is activated, a customer signs, a certification expires, a contract renews, an attribute changes, a date threshold is reached — and creates an assignment (or another action) in response.

This is the difference between manual administration and a designed system. Direct assignment is fine for one-off pushes. Automation is what makes partner enablement, customer education, recurring certification, and role-based capability sustainable.

The mental model:

A trigger is an event in the world.
A condition is a filter on who or what the trigger applies to — almost always a Smart Segmentation rule.
An action is what Continu does in response.

Automation is leverage. With Smart Segmentation underneath, one automation can serve a population that grows and changes for years without you ever opening the rule again.

Automation is also where unintended consequences live. Test every automation against a controlled segment of two or three users — a few test partners, test customers, or test learners — before activating it ecosystem-wide. The platform will happily fire ten thousand wrong assignments if you let it.

The strategic question: what events in my ecosystem should automatically generate learning intent? Every recurring program is an answer to that question.

How the Objects Relate

Here is the system in one sentence:

Users have attributes. Attributes drive Smart Segmentation. Smart Segmentation and triggers drive Automations. Automations create Assignments. Assignments deliver Content. Content drives Completion. Completion — and Workshop attendance — drive Reporting.

Read that sentence twice. Most admin confusion comes from skipping a link in that chain.

Example: a new channel partner is activated.

Your partner system marks a new reseller as active.
→ Continu syncs the partner contact and their attributes.
→ The contact matches a Smart Segmentation population ("Tier 2 Resellers — North America — newly activated").
→ A "User Added" Automation fires.
→ It creates an Assignment to the Reseller Onboarding Track.
→ The assignment moves through states as the partner engages.
→ A live certification Workshop in week 4 captures attendance.
→ Reporting reflects completion at every step.
→ The channel manager's dashboard rolls up partner readiness across the territory.

The same chain works for a new customer admin starting onboarding, a franchisee taking over a location, a contractor starting a project, an employee changing roles. The audience changes. The architecture does not.

If any link in the chain breaks, the program does not deliver. Understanding the chain is how you debug.

How Triggers Work

Continu is event-driven, not poll-driven.

This matters because:

Automations fire when an event happens, not on a schedule. A new partner activated on a Tuesday gets enabled on Tuesday — not at the next nightly batch.
The two most important trigger types are User Added and User Updated. They sound similar. They are not.
- User Added fires once, when a user first matches a segment.
- User Updated fires whenever an attribute change moves a user into a segment they did not previously match — for example, a partner advancing from Silver to Gold tier.
Misconfigured triggers are the single most common cause of "why did everyone get this assignment again?" tickets. Always think about idempotency: if this trigger fires twice for the same user, what should happen?

How Reporting Flows

Reporting is a read on the state of the system you have built. It is not a separate product — it is a window into the same objects.

Three things to know:

Every metric is a function of state. Completion rate is the percentage of assignments in a Completed state, scoped to a population. If your population is wrong, the metric is wrong. (This is exactly why Smart Segmentation matters for reporting, not just for delivery.)
Time filters apply to events, not to assignments. A "completed in last 30 days" filter looks at the timestamp on the state change, not on when the assignment was created.
Reports answer questions. Choose the report that matches the question you are asking, not the report with the most filters.

The most useful reporting habit: define the business question first, then pick the report. "How many of our Tier 1 partners are certified?" is a different question from "Which customers stalled in onboarding?" is a different question from "Where is the program stuck?" Different questions, different reports.

Five Habits of Mature Continu Admins

A few principles worth internalizing early — they hold whether your audience is partners, customers, channel, or employees:

Design before you click. Sketch the learner, the segmentation, and the trigger before you open the platform. The platform is fast at execution and slow to undo bad design.

Test before you scale. Activate every automation against two or three test users first. Continu will happily fire ten thousand unintended assignments if you let it.

Name like you will come back in six months. Because you will. Naming conventions that include audience, program, and version are an act of kindness to your future self — and your future stakeholders, partners, and auditors.

Build segmentation before automations. Most program problems are segmentation problems in disguise.

Don't mistake activity for learning. Completion is a proxy. Engagement, application, capability, and outcomes are the real signal. Build programs to teach, not to tick boxes — and your partners, customers, and employees will all feel the difference.

Common Mistakes

These are the patterns we see most often:

Building automations before defining Smart Segmentation.
Confusing direct assignment with automation. Direct is for one-time pushes. Automation is for sustained programs.
Treating workshops as content. A workshop is an event with attendance — design it that way.
Reading reports without understanding the underlying state.
Notifying too often. Every notification is a small withdrawal from the learner's attention budget — and partners and customers have less patience for it than employees do.
Letting attribute hygiene slip. When user data goes stale, segmentation lies, automations misfire, and reports mislead. This is especially dangerous for external audiences where you don't control the source system.

Where to Go Next

Once this model is in your head, the rest of the help center stops feeling like a list of disconnected features and starts feeling like a toolkit.

How Continu Works Follow