Summary and recommendation
Clearwater Analytics 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.
Clearwater Analytics is an enterprise-only investment accounting and reporting platform sold exclusively on a custom, quote-based model.
No self-service admin console path, user types, or permission model details are publicly documented.
User provisioning and access management appear to be handled through Clearwater's client services team rather than an in-product admin UI.
Quick facts
| Admin console path | Settings / Administration > Users and Roles (exact labels vary by tenant) |
| SCIM available | No |
| SCIM tier required | N/A |
| 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: Clearwater Analytics 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: Clearwater Analytics is sold on a custom, quote-based enterprise model. No publicly documented seat pricing or tier structure was found.
The cost of manual management
Because onboarding and configuration are managed through Clearwater's client services team, every app lifecycle action - adding a user, removing a departing employee, or adjusting access - likely requires a support touchpoint rather than a direct admin action.
This creates compounding overhead at scale: offboarding delays mean former employees may retain access longer than intended, and there is no publicly documented way to audit or reclaim seats independently. Pricing is custom and quote-based, so seat cost per action cannot be estimated from public sources.
The decision
Manual user management in Clearwater Analytics is viable only if your team has an established relationship with Clearwater's client services team and can absorb the latency of support-mediated provisioning. For organizations where every app must have a consistent, auditable joiner-mover-leaver process, the absence of documented self-service controls is a meaningful operational gap.
Confirm SSO and provisioning options contractually before assuming any automated or semi-automated workflow is available.
Bottom line
Clearwater Analytics is a capable enterprise investment platform, but its user management posture is opaque by design: no public admin console path, no documented permission model, and provisioning routed through client services.
Every app in a mature IT environment benefits from predictable, self-service access controls - and Clearwater's current public documentation does not confirm that standard. Teams should treat user lifecycle management as a contractual negotiation item, not a product feature they can evaluate independently before signing.
Automate Clearwater Analytics 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.
