Summary and recommendation
WorkRamp user management can be run manually, but complexity usually increases with role models, licensing gates, and offboarding dependencies. This guide gives the exact mechanics and where automation has the biggest impact.
WorkRamp user management lives under Admin → People (https://app.workramp.com/admin/users).
The platform uses a fixed role-based model - Admin, Manager, Learner, and Content Creator - with no publicly documented self-serve custom roles.
Permissions are scoped first by role, then narrowed by group and team hierarchy.
Quick facts
| Admin console path | Admin → People (or Users) section within the WorkRamp admin dashboard |
| Admin console URL | Official docs |
| SCIM available | Yes |
| SCIM tier required | Enterprise |
| SSO prerequisite | No |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Admin | Full platform access: manage users, content, groups, integrations, billing, and reporting. Can create and assign all content types. | Admin seats typically count against licensed seat totals; confirm with WorkRamp account team. | |||
| Manager | Can view reports and progress for direct reports; may assign training to their team depending on configuration. | Cannot manage platform-wide settings, billing, or other teams' users. | Manager visibility scope is tied to group/team hierarchy configuration. | ||
| Learner | Can access and complete assigned training content, guides, and academies. Can view own progress. | Cannot create or publish content; cannot manage other users. | Learner is the default role assigned to new users. External learners (customers/partners) may be licensed separately depending on contract. | ||
| Content Creator / Author | Can create, edit, and publish training content (guides, paths, academies) within assigned scope. | Cannot manage users or billing. | Content creation permissions may be granted as an add-on to Learner or Manager roles rather than a standalone role; verify with WorkRamp documentation for current role naming. |
Permission model
- Model type: role-based
- Description: WorkRamp uses a role-based permission model with predefined roles (Admin, Manager, Learner, and content-authoring roles). Permissions are scoped by role assignment and group/team membership. Granular custom roles are not publicly documented as a self-serve feature.
- Custom roles: No
- Custom roles plan: Not documented
- Granularity: Role-level; scoped further by group/team assignment. Individual permission toggles are not publicly documented.
How to add users
- Log in to WorkRamp as an Admin.
- Navigate to Admin → People (or Users).
- Click 'Invite User' or 'Add User'.
- Enter the user's email address and first/last name.
- Assign a role (e.g., Learner, Admin).
- Optionally assign the user to one or more groups.
- Send the invitation; the user receives an email to set their password and activate their account.
Required fields: Email address, First name, Last name, Role
Watch out for:
- Invited users consume a licensed seat upon activation; confirm seat availability before bulk invitations.
- If SSO is enforced, users must authenticate via the configured IdP and may not use password-based login.
- Group assignment at invite time determines initial content visibility and reporting hierarchy.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | Yes | Admin → People → Import Users (CSV upload option) |
| Domain whitelisting | No | Automatic domain-based user add |
| IdP provisioning | Yes | Enterprise |
How to remove or deactivate users
- Can delete users: Unknown
- Delete/deactivate behavior: WorkRamp's official help documentation describes deactivating users to remove platform access. Whether a hard delete of user records is available is not explicitly confirmed in publicly available official documentation. Deactivation is the documented method for removing access.
- Log in to WorkRamp as an Admin.
- Navigate to Admin → People (or Users).
- Locate the user by name or email.
- Select the user and choose the 'Deactivate' option.
- Confirm the deactivation.
| Data impact | Behavior |
|---|---|
| Owned records | Completion records and progress data associated with the deactivated user are retained in the platform for reporting purposes. |
| Shared content | Content created or assigned by the deactivated user remains in the platform; reassignment behavior is not explicitly documented in public help articles. |
| Integrations | SCIM-provisioned users deprovisioned via the IdP are automatically deactivated in WorkRamp; integration tokens or API keys tied to the user may need separate review. |
| License freed | Deactivating a user is expected to free the associated licensed seat, but the exact timing (immediate vs. next billing cycle) should be confirmed with WorkRamp support. |
Watch out for:
- Deactivated users cannot log in but their historical data (completions, scores) is preserved for reporting.
- If SCIM is in use, deprovisioning should be performed in the IdP to ensure consistent deactivation; manual deactivation in WorkRamp may conflict with SCIM sync.
- Reactivating a previously deactivated user may require a new seat allocation depending on current license count.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Internal Learner Seat | Access to assigned training content, guides, academies, and personal progress tracking for employees. | Included in platform contract; per-seat pricing not publicly listed - quote-based. |
| External Learner Seat (Customer / Partner) | Access to customer-facing or partner academies. May be licensed separately from internal seats depending on contract. | Quote-based; separate SKU from internal seats in many contracts. |
| Admin Seat | Full administrative access. Typically counts against total licensed seats. | Included within total seat count; no separate published price. |
- Where to check usage: Admin → People (Users list shows active vs. inactive users and total count); reporting dashboards may show seat utilization.
- How to identify unused seats: Filter the Users list by 'Last Login' date or 'Active' status to identify users who have not logged in recently. WorkRamp does not publicly document an automated unused-seat report.
- Billing notes: WorkRamp pricing is contract-based and not publicly listed per seat. Plans are quoted annually. Internal and external (customer/partner) learner seats are typically separate line items. Pricing seed data indicates Professional tier at approximately $17k–$30k/year for 200 users and Enterprise at $54k–$102k+/year for 1,000+ users, but these figures are estimates and should be verified with WorkRamp sales.
The cost of manual management
WorkRamp is contract-priced with no public per-seat rate. Seed data suggests the Professional tier runs roughly $17k–$30k/year for 200 users; Enterprise runs roughly $54k–$102k+/year for 1,000+ users - but both figures are estimates and must be confirmed with WorkRamp sales.
Internal and external (customer/partner) learner seats are typically separate line items, which adds complexity when tracking spend across every app in your stack. Admin seats count against total licensed seats, so provisioning admins carelessly inflates your billable count.
What IT admins are saying
Community evidence is not specific enough to quote or summarize yet for this app.
The decision
Manual provisioning is viable for small, stable teams where invite volume is low and group assignments are straightforward. For organizations managing frequent onboarding, offboarding, or role changes across every app in their portfolio, the absence of automated seat-utilization reporting and the complexity of internal-vs-external seat tracking make manual workflows a meaningful operational burden.
If SCIM is available on your contract tier, it is the lower-risk path for lifecycle management.
Bottom line
WorkRamp's manual user management is functional but friction-heavy at scale.
The fixed role model, group-driven content assignment, and split seat licensing mean that small provisioning errors - a missed group assignment or an over-provisioned admin seat - have downstream effects on both content access and contract costs.
Teams running frequent headcount changes should weigh that operational overhead carefully before committing to a manual-only workflow.
Automate WorkRamp workflows without one-off scripts
Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.
