Summary and recommendation
Clari 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.
Clari is a revenue intelligence platform built around forecasting, pipeline inspection, and CRM write-back - with optional add-on modules for conversation intelligence (Copilot) and sales engagement (Groove).
User management lives at Settings → Users inside the Admin console (https://app.clari.com/settings), and access is role-based: Admin, Manager, and Rep tiers map directly to visibility layers in the forecasting hierarchy.
Because that hierarchy is driven by CRM sync (typically Salesforce), the org structure in your CRM is effectively the source of truth for who sees what in every app layer Clari exposes.
Quick facts
| Admin console path | Settings → Admin (accessible to users with Admin role) |
| Admin console URL | Official docs |
| SCIM available | No |
| SCIM tier required | Enterprise |
| SSO prerequisite | Yes |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Admin | Full access to system settings, user management, CRM integration configuration, role assignments, and forecasting hierarchy setup. | Admin role assignment and exact permission boundaries are not publicly documented in detail; configuration may require Clari implementation support. | |||
| Manager | Access to team forecasting views, pipeline inspection for direct reports, and rollup submissions. | Cannot manage system-level settings or add/remove users. | Manager visibility is tied to CRM hierarchy sync; mismatches in CRM org structure can break rollup access. | ||
| Rep (Individual Contributor) | Access to own pipeline, opportunity updates, and forecast submissions for their own book of business. | Cannot view peer data or admin settings. | Rep access to Copilot (conversation intelligence) or Groove (sales engagement) requires separate module licensing. |
Permission model
- Model type: role-based
- Description: Clari uses a role-based access model aligned to CRM hierarchy (typically Salesforce). Roles such as Admin, Manager, and Rep map to visibility tiers in forecasting and pipeline. Access to specific modules (Copilot, Groove) is controlled by license entitlement in addition to role.
- Custom roles: Unknown
- Custom roles plan: Not documented
- Granularity: Role and module-level; granular object-level permissions not publicly documented.
How to add users
- Log in to Clari as an Admin.
- Navigate to Settings → Users (or Admin → User Management).
- Click 'Add User' or 'Invite User'.
- Enter the user's email address, name, and assign a role.
- Assign the user to the appropriate team or hierarchy node (typically synced from CRM).
- Save or send invitation.
Required fields: Email address, First and last name, Role assignment, CRM user mapping (if applicable)
Watch out for:
- User hierarchy and team structure are typically driven by CRM (Salesforce) sync; manually added users may not appear correctly in forecasting rollups until CRM mapping is confirmed.
- Module access (Copilot, Groove) must be separately provisioned and may require Clari support or CSM involvement.
- SSO-enforced orgs may require the user to exist in the IdP before they can log in, even if manually added in Clari.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | Unknown | Not documented |
| Domain whitelisting | No | Automatic domain-based user add |
| IdP provisioning | Yes | Enterprise |
How to remove or deactivate users
- Can delete users: No
- Delete/deactivate behavior: Based on available information, Clari deactivates users rather than permanently deleting them, preserving historical data integrity for forecasting and audit purposes. Permanent deletion capability is not publicly documented.
- Log in to Clari as an Admin.
- Navigate to Settings → Users.
- Locate the user to be deactivated.
- Select the option to deactivate or disable the user account.
- Confirm the action.
| Data impact | Behavior |
|---|---|
| Owned records | Historical forecast submissions and pipeline data associated with the deactivated user are retained for reporting continuity. |
| Shared content | Shared views or collaborative content tied to the user may remain accessible to admins; exact behavior not publicly documented. |
| Integrations | CRM integration data (e.g., Salesforce opportunity ownership) is unaffected by Clari deactivation; CRM records remain as-is. |
| License freed | Deactivating a user should free the seat license, but billing reconciliation timing depends on contract terms; confirm with Clari account team. |
Watch out for:
- If the user is synced from CRM, deactivating in Clari alone may not prevent re-provisioning on the next CRM sync if the CRM record remains active.
- For SSO/SCIM-enabled orgs, deprovisioning should be performed in the IdP to ensure access is fully revoked.
- License release timing and credit policies are contract-dependent and not publicly documented.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Core Platform (Forecasting/Revenue Intelligence) | Pipeline inspection, forecasting, deal management, CRM write-back. | ~$100/user/month (estimated; quote-based) |
| Copilot (Conversation Intelligence) | Call recording, transcription, AI-generated summaries, coaching. | +~$100/user/month add-on (estimated; quote-based) |
| Groove (Sales Engagement) | Email sequencing, dialer, activity tracking, Salesforce integration. | Bundled with Copilot or separately quoted; pricing not publicly listed |
- Where to check usage: Settings → Users (Admin view shows active user count; detailed license utilization reporting not publicly documented as a self-serve feature).
- How to identify unused seats: No publicly documented self-serve license utilization report; admins may need to cross-reference last login dates in the Users list or request a usage report from their Clari CSM.
- Billing notes: Clari uses quote-based, contract-driven pricing. Seat counts and module entitlements are set at contract time. Mid-term seat reductions may not result in immediate billing changes; consult contract terms. Clari merged with Salesloft in 2025, which may affect future packaging and billing structures.
The cost of manual management
Clari does not offer SCIM provisioning outside of Enterprise contracts, and even then SSO is a hard prerequisite. That means manual admin UI work is required for every user lifecycle event in non-Enterprise or non-SSO deployments.
Adding a user requires confirming CRM mapping before the account appears correctly in forecasting rollups; removing one is a two-step process - revoke SSO access in the IdP, then manually deactivate in Clari Admin - because there is no automated sync between the two.
Module access (Copilot, Groove) must be provisioned separately and often requires CSM or support involvement, adding coordination overhead to every onboarding and offboarding event.
What IT admins are saying
Recurring friction reported by Clari admins centers on three areas. First, the CRM-hierarchy dependency: org changes in Salesforce can silently break forecasting rollups until a re-sync is triggered, and there is no self-serve way to audit the mismatch.
Second, SSO configuration is not fully self-serve - enabling it requires contacting Clari support or a CSM. Third, self-serve admin documentation is sparse; much of the help center requires a logged-in Clari account, which limits pre-implementation research and troubleshooting for new admins.
Common complaints:
- Feature availability and admin capabilities vary significantly by plan and contract; many features require CSM or support involvement to enable.
- Requires contacting Clari support or CSM to configure SSO; not fully self-serve.
- Expensive when combined with Copilot and other add-on modules; total cost can reach $200–$500/user/month.
- User hierarchy in Clari is tightly coupled to CRM structure; org changes in Salesforce can cause forecasting rollup issues until re-synced.
- Limited self-serve admin documentation publicly available; much of the help center content requires a logged-in Clari account to access.
- SCIM provisioning requires Enterprise tier and SSO prerequisite, limiting automated user lifecycle management for smaller customers.
- Post-merger with Salesloft (2025), customers report uncertainty about product roadmap and packaging changes.
The decision
Manual management is the only path for teams below Enterprise tier or without SSO configured. Every app that depends on accurate forecasting rollups - dashboards, pipeline reviews, board-level forecasts - is exposed to CRM hierarchy mismatches until they are manually corrected, making this a real operational risk during rapid headcount changes or Salesforce org restructures.
Admins should treat IdP deprovisioning plus Clari Admin deactivation as a mandatory two-step checklist, not an either/or. License seat counts and mid-term reduction policies are contract-dependent; consult your agreement before offboarding in bulk.
Bottom line
Clari's manual user management is functional but tightly coupled to your Salesforce org structure and contract tier, which means administrative errors in CRM ripple directly into forecasting visibility.
Every app that relies on accurate rollup data is exposed to those mismatches until they are manually corrected, and teams with frequent headcount changes will feel the overhead most acutely.
The two-step offboarding requirement and CSM dependency for module provisioning should be factored into IT operations planning from day one.
Automate Clari 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.
