Summary and recommendation
BetterUp 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.
BetterUp is an enterprise coaching and workforce development platform.
Admin and user-management workflows are not publicly documented;
onboarding, seat provisioning, and deactivation procedures appear to be handled through a dedicated customer success or implementation team rather than a self-serve admin console.
Teams evaluating BetterUp should expect a high-touch, vendor-assisted setup process rather than independent configuration.
Quick facts
| Admin console path | Settings / Administration > Users and Roles (exact labels vary by tenant) |
| 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 | Can manage tenant settings, integrations, and user access. | Cannot grant functionality outside the modules licensed for the tenant. | Detailed built-in role names are not fully documented publicly. | ||
| Standard User | Can use the core product features exposed to their role. | May not be able to manage tenant settings or other users. | Exact privileges can vary by tenant configuration. |
Permission model
- Model type: role-based
- Description: BetterUp appears to use role-based access for tenant administration and general product use, but the detailed permission matrix is not publicly documented in full.
- Custom roles: Unknown
- Custom roles plan: Not documented
- Granularity: Expect administrative access to be separated from standard user access, with exact scopes configured per tenant.
How to add users
- Log in as an administrator.
- Open settings or administration and navigate to users.
- Choose the add or invite user action.
- Enter the user's work email and assign the appropriate role.
- Save the user and complete any activation or SSO steps required by the tenant.
Required fields: Work email address, Role
Watch out for:
- Public documentation for user administration is limited, so exact labels may vary by tenant.
- If SSO is enabled, upstream IdP assignment may still be required.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | Unknown | Not documented |
| Domain whitelisting | Unknown | Automatic domain-based user add |
| IdP provisioning | Unknown | Not documented |
How to remove or deactivate users
- Can delete users: Unknown
- Delete/deactivate behavior: Public docs do not clearly document whether users are disabled, deleted, or both. Treat lifecycle behavior as tenant-specific unless confirmed in-product.
- Open the users area as an administrator.
- Locate the user to offboard.
- Disable, revoke, or remove the account using the controls available in that tenant.
- Review any integrations or service credentials associated with the departing user.
| Data impact | Behavior |
|---|---|
| Owned records | Tenant data remains in the workspace; public docs do not describe user-owned content semantics in detail. |
| Shared content | Shared dashboards, configurations, and records remain available unless separately removed. |
| Integrations | Review service credentials and integration ownership separately during admin offboarding. |
| License freed | Seat reuse behavior is contract-dependent and not publicly documented in detail. |
Watch out for:
- Offboarding should include token and integration review, not just interactive login removal.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Named user | Administrative or standard access to the tenant. |
- Where to check usage: Settings / Administration > Users and Roles
- How to identify unused seats: Review the tenant user list and any visible login or activity metadata. No public unused-seat report was verified.
- Billing notes: Public seat-level licensing details are not fully documented.
The cost of manual management
Because no self-serve admin documentation is publicly available, every app lifecycle event - adding a new hire, deactivating a departing employee, or auditing unused seats - requires coordination with BetterUp's customer success team. This creates a compounding operational burden: offboarding delays mean active coaching sessions may continue for employees who have already left.
Without a documented deactivation path, license reclamation depends entirely on how responsive your vendor contact is at any given moment.
The decision
BetterUp is best suited for organizations that already have a dedicated HR or L&D program manager who can own the vendor relationship and coordinate provisioning manually. If your team expects self-serve user management or automated lifecycle controls across every app in your stack, BetterUp's current admin model will introduce friction.
Confirm with your account team exactly which lifecycle operations are supported, at what cadence, and whether any admin portal access is included in your contract tier.
Bottom line
BetterUp's enterprise admin experience is opaque by design: no public documentation, no self-serve provisioning, and no disclosed seat management tooling.
Every user lifecycle action - from onboarding to offboarding - runs through the vendor's customer success layer, which makes BetterUp an outlier compared to SaaS tools that expose admin controls directly.
Organizations with strict access governance or frequent headcount changes should pressure-test the vendor's operational SLAs before committing to a contract.
Automate BetterUp 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.
