Summary and recommendation
Coassemble 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.
Coassemble is a role-based LMS with three fixed workspace roles: Admin, Author, and Learner.
All user management happens through Workspace Settings > Members - there is no public SCIM endpoint or IdP connector to automate provisioning.
Every app in your stack that lacks automated provisioning creates the same exposure: access that outlives employment.
Quick facts
| Admin console path | Workspace Settings > Members |
| Admin console URL | Official docs |
| SCIM available | No |
| SCIM tier required | Enterprise |
| SSO prerequisite | No |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Admin | Full workspace control: invite/remove members, manage billing, create and publish courses, assign content to groups, configure workspace settings. | Counts as a paid seat on plans that charge per active member. | Only Admins can access billing and workspace-level settings; there is no separate Owner role documented publicly. | ||
| Author | Create, edit, and publish courses; manage own content; view learner progress on assigned courses. | Cannot access billing, cannot manage workspace settings, cannot invite or remove other members. | Counts as a paid seat on plans that charge per active member. | Author seat count directly affects plan cost on seat-based tiers. | |
| Learner | Access and complete courses assigned to them; view own progress. | Cannot create or edit content, cannot access admin or author areas. | Learner seats are included or priced separately depending on plan tier; some plans offer unlimited learners. | On certain plans, learner seats are unlimited and do not consume the same seat quota as Authors/Admins. Verify current plan terms before assuming unlimited learner access. |
Permission model
- Model type: role-based
- Description: Coassemble uses three fixed workspace roles: Admin, Author, and Learner. Roles are assigned per workspace member and cannot be customized or combined into hybrid permission sets.
- Custom roles: No
- Custom roles plan: Not documented
- Granularity: Role-level only; no per-feature or per-course permission overrides documented in official help content.
How to add users
- Navigate to Workspace Settings > Members.
- Click 'Invite Members' or equivalent invite button.
- Enter the invitee's email address.
- Select the role to assign: Admin, Author, or Learner.
- Send the invitation; the invitee receives an email to accept and set up their account.
Required fields: Email address, Role selection (Admin, Author, or Learner)
Watch out for:
- Invitations expire if not accepted; resend may be required.
- Adding Authors or Admins may increase billable seat count immediately depending on plan.
- Users must accept the email invitation before they appear as active members.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | Yes | Workspace Settings > Members > Import / Bulk Import (CSV upload option) |
| Domain whitelisting | No | Automatic domain-based user add |
| IdP provisioning | No | Not documented |
How to remove or deactivate users
- Can delete users: Unknown
- Delete/deactivate behavior: Coassemble's official help documentation describes removing members from a workspace, but does not explicitly distinguish between a permanent delete and a deactivation/suspension state. The exact data-retention behavior upon removal is not clearly documented in publicly available official sources.
- Navigate to Workspace Settings > Members.
- Locate the member to remove.
- Select the option to remove or revoke access for that member.
- Confirm the action when prompted.
| Data impact | Behavior |
|---|---|
| Owned records | Not documented |
| Shared content | Not documented |
| Integrations | Not documented |
| License freed | Removing a member is expected to free their seat, reducing billable count on seat-based plans, but official documentation does not specify the exact billing cycle timing. |
Watch out for:
- Official documentation does not clearly state whether removed user data (course completions, progress records) is retained or deleted.
- Billing adjustment timing after member removal is not explicitly documented.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Author/Admin seat | Ability to create content and/or manage the workspace; counts toward the paid seat limit on most plans. | Varies by plan tier; approximately $10–$99/month per seat range based on published pricing tiers. |
| Learner seat | Access to assigned courses and progress tracking only. | Included as unlimited on some plans; counted separately on others. Verify current plan details at coassemble.com/pricing. |
- Where to check usage: Workspace Settings > Members (shows current member count and roles); billing summary accessible under Workspace Settings > Billing.
- How to identify unused seats: No documented automated inactive-user report. Admins must manually review the Members list and cross-reference last-login or course activity data if available.
- Billing notes: Coassemble pricing is seat-based for Authors/Admins on most plans. Some plans advertise unlimited learners. Pricing tiers (Solo, Pro, Business, Enterprise) differ in seat counts and feature access. Enterprise pricing is custom. Always verify current pricing at coassemble.com/pricing as rates change.
The cost of manual management
Author and Admin seats are billable on most plans, so every unreviewed member is a potential cost leak. Coassemble does not surface an inactive-user report; Admins must manually audit the Members list and cross-reference course activity to identify stale accounts.
Billing adjustment timing after removal is not explicitly documented, so seat reclamation may not be immediate.
What IT admins are saying
Community evidence is not specific enough to quote or summarize yet for this app.
The decision
Coassemble suits teams that can absorb manual provisioning overhead and do not require IdP-driven lifecycle management. The three-role model is straightforward for small author teams but becomes a governance liability at scale, where every app with fixed roles and no SCIM forces IT to own every joiner, mover, and leaver event by hand.
Teams on Enterprise should contact Coassemble sales directly to confirm whether any custom integration path exists before committing to a workflow.
Bottom line
Coassemble's user management is entirely UI-driven, with no public API, no SCIM, and no documented IdP connectors. Every app that relies solely on manual provisioning introduces the same risk: access persists until someone remembers to remove it.
For organizations where learner seat counts are large or Author/Admin turnover is frequent, the manual audit burden is real and the cost of inaction - both in license spend and access risk - compounds over time.
Automate Coassemble 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.
