Summary and recommendation
Spring Health 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.
Spring Health is a B2B mental health benefits platform sold exclusively through employer contracts, and unlike every app that exposes a self-serve admin console, it has no publicly indexed admin portal documentation.
Provisioning and deprovisioning workflows appear to be managed through a dedicated customer success or implementation team assigned during onboarding.
No help center articles covering admin user management are publicly accessible.
Quick facts
| Admin console path | Settings / Administration > Users and Roles (exact labels vary by tenant) |
| SCIM available | No |
| SCIM tier required | N/A (B2B only) |
| 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: Spring Health 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
Without a documented deactivation path, IT and HR teams must coordinate directly with Spring Health's implementation team to remove departed employees from eligibility - a process that is slow by design and difficult to audit at scale. Seat reclamation and access reviews cannot be self-initiated, which increases the risk of lingering access for terminated members.
This makes offboarding a high-friction, high-latency exception in any joiner-mover-leaver workflow.
The decision
Every app in a standard SaaS stack requires a documented offboarding path, and Spring Health's absence of a self-serve portal makes it a high-touch exception that demands a pre-agreed escalation process with your assigned customer success contact.
IT and security teams should confirm offboarding SLAs directly with Spring Health before relying on any time-sensitive deprovisioning workflow. Organizations requiring auditable, real-time access removal should document the agreed process internally to maintain audit readiness.
Bottom line
Spring Health's employer-only model means provisioning and deprovisioning run through Spring Health's implementation or customer success team rather than an admin console.
Public documentation on admin workflows does not exist in any indexed form, so IT teams should establish a direct escalation path with their Spring Health contact and document the agreed offboarding process internally to maintain audit readiness.
Automate Spring Health 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.
