How to manage the lifecycle of partners, customers, channel reps, franchise operators, and employees in Continu — so the right people have the right access, the wrong people don't, and you can prove both.
Why User Management Matters
A user record looks like a row in a database. It isn't. Each user record is a person with access — to your content, your customer data, your partner directory, your compliance records. The decisions about who exists in Continu and what they can do shape the security posture, the audit posture, and the quality of every program that runs through the platform.
The cost of bad user management is rarely obvious in the moment. Inactive partners still receive certification notifications and the partner program looks artificially engaged. Terminated employees still appear in compliance cohorts and the completion rate looks artificially low. Customer admins who left their company still hold their access and the customer's auditors are about to ask why. Each one is small. Together, they erode the trust in the data your program produces.
User management is the operational discipline that prevents that erosion. It's not glamorous, it doesn't ship features, and it shows up in the program owner's day as a steady stream of small decisions — provision this person, deprovision that one, change this role, audit this access.
This guide is about treating that work with the seriousness it deserves.
What User Management Actually Is
User management in Continu is the lifecycle of every user record — from creation through role changes to deprovisioning — plus the audit and access reviews that confirm the state is correct.
Strip away the mechanics and user management does three jobs.
Provision the right people. Create user records for the people who should have access. Sometimes manually, often automatically through integrations with HRIS, PRM, or other source systems. The job is to make sure everyone who needs access has it, and to do it without manual list-keeping that breaks at scale.
Assign the right access. Roles, permissions, group memberships, segment associations. The job is to give each user the access they need to do their job and nothing more. The principle of least privilege is real; settings creep is the failure mode.
Deprovision when access ends. When a partner leaves the channel, when a customer admin changes companies, when an employee terminates, when a contract ends. The user record's access needs to be revoked promptly and cleanly. Stale access is a security incident waiting to happen.
These are different jobs with different stakeholders. Provisioning often lives with IT or HR (for employees) or partner operations (for partners). Role assignment lives with the program owner. Deprovisioning lives with security and IT but the L&D consequence falls on the program owner.
The strategic question: for each user in your tenant, do you know how they got there, what they should be able to do, and who confirms that status quarterly?
Who Lives in Continu
The user population in Continu is usually broader than a single category.
Employees. Internal staff. Usually sourced from HRIS. Lifecycle tied to hire, role changes, leave, termination. Highest volume of automated provisioning typically.
Partners and channel reps. External staff at partner organizations. Sourced from PRM, manual provisioning, or self-serve enrollment. Lifecycle tied to partner-program enrollment and offboarding.
Customer admins. Customer-side users who interact with your Continu tenant — often customer success-led training, certification, or admin enablement. Lifecycle tied to customer relationships.
Franchisees and franchise operators. Independent operators in a franchise system. Sourced from franchise management systems or manual onboarding. Lifecycle tied to franchise agreements.
Contractors and vendors. Third-party staff with time-bounded access. Often shorter tenure than other user types; deprovisioning rhythm tighter.
Members. Association or community members. Lifecycle tied to membership renewals.
Each population has its own provisioning source, its own lifecycle, its own access scope. Treating them as one user pool produces sloppy access decisions. Treating them as distinct populations with explicit lifecycle policies produces a clean tenant.
The Roles Question
Every user in Continu has a role (or set of roles) that defines what they can do.
Admin. Full configuration access. Settings, permissions, integrations, content lifecycle. The role with the most power; the role that needs the most discipline. A clean tenant has few admins, all of them deliberately chosen, all of them reviewed quarterly.
Creator. Can author content, assemble tracks and journeys, configure assessments and surveys, build automations. The program-design role. Usually the largest non-admin role in a healthy tenant.
Manager. Can see direct reports' progress, assign content within their span of control, run reports on their team. Tied to the manager hierarchy from the HRIS or similar source.
Learner. Consumes content, completes programs, takes assessments. The default role for most users.
The strategic discipline is choosing roles based on what each user actually needs to do, not what's easier to grant. "Make them all admins, it's easier" is the most common bad decision in user management. Three years later, fourteen people have admin access and nobody can remember why.
Provisioning Sources
How users get into Continu shapes everything downstream. Different sources have different implications.
HRIS integration. Workday, BambooHR, ADP, or equivalent. Source of truth for employees. Drives provisioning, deprovisioning, segmentation, manager hierarchy, role changes. When HRIS is configured correctly, employee lifecycle is automatic.
SCIM. Identity provider-driven provisioning. Common for organizations using Okta, Azure AD, or similar IdP as the authoritative user store. SCIM provisioning handles employees and often partners.
PRM (Partner Relationship Management). Source of truth for partner-program enrollment. Drives partner user provisioning and lifecycle.
Manual provisioning. Admin-created user records. Used for small populations, special cases, contractors, vendors. Doesn't scale; should be the exception, not the rule.
Self-serve enrollment. Users sign up themselves, often through a partner portal or member registration. Useful for high-volume external populations where you can't realistically provision each user manually.
API or scripted provisioning. Custom integrations using Continu's API. Used for non-standard source systems or for migrating users in bulk.
Each source has lifecycle implications. HRIS-driven users follow HRIS lifecycle. Manually-created users have no automatic lifecycle — someone has to remember to deprovision them. Mixed-source tenants need explicit rules about which source owns which user record.
Best Practices
Define the provisioning model before scaling user count. Decide upfront — for each user population — which system is authoritative and how lifecycle events propagate. Adding 5,000 partners with no defined provisioning model produces a tenant full of orphans within a year.
Match the role to the job. Don't grant admin access because it's easier. Map out which roles need which permissions and assign the narrowest fit. The cleanup cost of broad permissions is much higher than the friction cost of narrow ones.
Plan deprovisioning from day one. When you add a new partner population, define how they will be deprovisioned — by what trigger, on what timeline, with what audit log. Without a deprovisioning plan, populations accumulate.
Run quarterly access reviews. Once a quarter, the admin team (or a delegate) reviews admin-level access, content creator access, and any non-default permissions. Confirm each one is still needed. Revoke what isn't. Document the review.
Tie role assignment to attributes, not to individuals. A partner-manager role isn't assigned to "Bob"; it's assigned to "anyone in the partner-manager segment." When Bob changes jobs, the segment changes, and Bob's role changes with it. Attribute-driven role assignment scales; individual-level assignment doesn't.
Use Smart Segmentation to drive role context. Segments based on attributes (role, location, region, tier, employment status) can drive role assignment, content visibility, and program enrollment. The segments do the work; user management becomes attribute management.
Document the lifecycle policy per population. Employees follow HRIS. Partners follow PRM. Customer admins follow CRM. Contractors are manually deprovisioned at end-of-contract date. Each population has a documented lifecycle; the team knows where each user category lives in its lifecycle.
Pair every external integration with an attribute-ownership map. Which system owns first name, which owns email, which owns manager, which owns role? Without this map, conflicting source systems overwrite each other on every sync.
Build a soft-delete or archive path for offboarded users. Deletion removes the audit trail. Archiving preserves it. For compliance and historical reporting, archived/deactivated is usually the right state, not deleted.
Test deprovisioning end-to-end. When a user is offboarded, can they still log in? Do they still receive notifications? Do they still appear in cohort segments? Test these scenarios with real users before they bite a real situation.
Anti-Patterns
Admin access as a convenience. Granting full admin to anyone who asks because it's easier than configuring the right scoped permission. Six months later, twelve people have admin access; you don't remember why eight of them needed it.
No deprovisioning policy. Adding users is easy; nobody owns removing them. Three years in, the tenant has 2,000 active users and 4,000 ghost users. Reports are wrong; license counts are wrong; audits are uncomfortable.
Manual provisioning at scale. Every new partner is a manual user creation. Every change is a manual edit. The work scales with the partner count; the errors scale faster. Automate provisioning before the population grows past a manageable manual threshold.
Static cohort assignment. Manually adding users to specific cohorts and then never updating membership. As people change roles, locations, or tier, the cohort drifts. Use segmentation that auto-maintains cohort membership.
Mixed source-of-truth chaos. HRIS thinks Bob is in marketing. CRM thinks Bob is at a partner. Continu has both records. The user has duplicate access, mismatched attributes, and broken segmentation. Decide which system owns each user record; merge or reconcile duplicates.
No quarterly access review. Admin access is granted and never revisited. Three years later, eleven admins exist; six of them haven't logged in this year. The access review catches this; without one, the sprawl compounds.
Deprovisioning as a manual to-do. When someone leaves the channel, a human needs to remember to deprovision them in Continu. Sometimes the human forgets. Automate deprovisioning from source system events when possible; for manual deprovisioning, build a queue and a SLA.
Role explosion. Creating fifteen custom roles for fifteen edge cases. The role inventory is its own complexity problem; consolidate to a small set of well-defined roles plus segment-based variations.
Hard-deleting users. Deleting removes the audit trail. The completion record is gone. The historical report can't account for the user. Use deactivation/archiving instead; preserve the trail.
Treating contractors like employees. Provisioning contractor user accounts with the same role and lifecycle as employees. When the contract ends, the deprovisioning doesn't happen because the contractor isn't in HRIS. Treat contractor populations as their own lifecycle.
Self-serve enrollment without rate-limiting or moderation. Open registration for partners turns into spam or fraud accounts. Self-serve enrollment needs at least basic verification — domain check, manual approval, captcha, or invite-code.
In the Continu Architecture
User management touches everything.
- Content. Visibility rules depend on user attributes. The user record is the audience filter for all content.
- Tracks and Journeys. Assignment is to users; users must exist with the right attributes to receive the right programs.
- Smart Segmentation. Segments are populations of users defined by attributes. Garbage attributes produce garbage segments.
- Assignments. Direct assignments target users; automated assignments target segments built from user attributes.
- Assessments. Records are tied to users. Stale users produce stale records.
- Badges. Issued to users; visible on user profiles. The badge inventory is only as clean as the user inventory.
- Reporting. Every report rolls up by user. User-management hygiene shows up in report quality.
- Notifications. Sent to users. Inactive or stale users either receive irrelevant notifications or — if filtered — surface gaps in the lifecycle.
The principle: every other Continu object operates on the user population. Fix user management and the rest of the platform produces cleaner data.
External Audience Patterns
Partner onboarding and offboarding. New partner rep enrolled via PRM or self-serve. Default role and segment assigned. Welcome flow triggers. When the rep leaves the partner, deprovisioning fires — ideally automated, manually with SLA otherwise.
Partner rep moves between partners. A rep at Partner A leaves and joins Partner B. The user record needs to be moved (re-attributed) rather than duplicated. Without a "move" policy, the rep has two records, mismatched segments, and double access.
Customer admin lifecycle. Customer relationships start, customer admin gets provisioned. Customer admins change at the customer side. The customer success team needs visibility into who's active and a path to deprovision when the customer relationship ends.
Channel tier changes. A partner moves from Bronze to Silver tier. Attributes update; access changes accordingly. Attribute-driven role and content access make this automatic. Manual permission edits make it brittle.
Franchise operator turnover. Franchise operators come and go. Corporate needs a clean view of who's active per franchise location. Franchise management integration handles the lifecycle.
Contractor and short-term access. Contractors with 90-day access. Time-bounded provisioning where access auto-expires at the contract end date.
Self-serve member registration. Association or community members register themselves. Manual approval, domain verification, or invite-code keeps the registration credible.
Internal Audience Patterns
HRIS-driven employee lifecycle. Hire date triggers provisioning. Role change in HRIS updates attributes in Continu. Termination in HRIS triggers deprovisioning. The HRIS is the source of truth; Continu reflects it.
Manager hierarchy maintenance. Manager relationships flow from HRIS. When someone gets a new manager, the manager-of-direct-reports relationship updates. Manager reporting reflects current org structure.
Leave handling. Employees on extended leave (parental, medical) — should they receive compliance assignments? Should reports include them? Define the policy and reflect it in attribute design so the system handles leave gracefully.
M&A integration. New employees from an acquired company need to be added quickly and integrated into the standard provisioning model. Decide on the integration approach before the M&A closes.
Role-based access for sensitive roles. Some internal roles (security, compliance, HR) need broader Continu access. Define those roles explicitly with documented justification rather than informal admin grants.
Internal transfers. Employee moves from sales to product. Attributes update; segment memberships change; assignments shift. The system handles it via segmentation; the program owner doesn't have to manually re-enroll the user.
Long-tenure stale access. Employees who have been at the company a long time may have accumulated permissions over the years. Periodic re-baselining of long-tenured users catches the creep.
Known Behaviors and Limits
HRIS-driven attributes are authoritative. When the source system owns an attribute, you cannot manually override it in Continu — the next sync will restore the source value. Plan attribute ownership upfront.
Provisioning sync has lag. When a new hire is added in HRIS, the Continu user record appears on the next sync cycle, not instantly. Plan onboarding workflows around the sync cadence.
Deprovisioning may not be immediate. Same lag applies in reverse. A terminated employee may persist briefly in Continu until the sync runs. For high-security situations, supplement automated deprovisioning with manual session termination.
Duplicate user detection is imperfect. When the same person exists in multiple source systems (employee who became a partner, customer admin who's also a contractor), duplicates can occur. Continu has duplicate detection, but it requires reasonable email-and-attribute consistency to work.
Role permissions are per-instance, not per-domain. A role defined in your tenant applies in your tenant. Multi-tenant or multi-instance deployments need their own role definitions.
Archived users still exist in records. Deactivating a user preserves their historical records but removes their access. For most compliance scenarios, this is the right state — not deletion.
Self-service password reset is gated by login method. SSO users don't manage passwords in Continu. Direct-login users do. Reset flows depend on the configured login method.
License counts depend on active users. Most license models count active (not archived) users. A clean deprovisioning practice keeps license counts honest.
Audit logs capture user changes, but require retention configuration. User-management actions (create, modify, deactivate) are logged. The retention window for those logs is configured in Settings; for compliance scenarios, confirm the retention matches your audit requirement.
Role changes propagate to existing data only on next operation. Granting a creator role doesn't retroactively give the user authorship of past content. It allows them to author new content going forward.
Where to Go Next
- Provisioning and Sync: How User Data Flows Into Continu — for the upstream integrations that feed user records.
- Settings: What Lives Here and What It Affects — for the tenant-wide configuration that frames user management.
- Smart Segmentation: Designing Populations That Maintain Themselves — for the attribute-driven segmentation that drives role assignment and access.
- Compliance Programs: The Audit-Ready Stack — for the audit-readiness that depends on clean user management.
- Reporting: Which Report Should I Use? — for the reports that surface user-management state.
Design first. Click second. Know who's in your tenant, why, and what they can do.