Summary and recommendation
Smarsh 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.
Smarsh is a compliance archiving and communications surveillance platform built for regulated industries.
It covers electronic communications capture, supervision workflows, and audit-ready retention across channels.
Admin capabilities are tiered, with full provisioning controls gated to the Enterprise plan.
Every app in a compliance stack depends on accurate user states, and Smarsh is no exception.
Quick facts
| Admin console path | Administration / Users and Roles (exact labels vary by Smarsh product module) |
| SCIM available | Yes |
| SCIM tier required | Enterprise |
| SSO prerequisite | No |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Administrator | Can manage tenant configuration, compliance settings, integrations, and user access. | Cannot grant capabilities outside the Smarsh products and modules licensed for the tenant. | Detailed built-in role names are not fully documented publicly. | ||
| Reviewer / Standard User | Can work with supervised communications, reviews, or archived records exposed to their role. | May not be able to manage tenant settings or other users. | Access varies by Smarsh product area and tenant configuration. |
Permission model
- Model type: role-based
- Description: Smarsh uses role-based access control across its platform, but specific role names, permission boundaries, and tier requirements are not publicly documented outside authenticated help content.
- Custom roles: Unknown
- Custom roles plan: Not documented
- Granularity: Expect role-based separation between tenant administration and review workflows, with exact scopes depending on the Smarsh modules in use.
How to add users
- Log in to Smarsh as an administrator.
- Open administration and navigate to users or roles.
- Choose the add or invite user action.
- Enter the user's work email or login details and assign the appropriate role.
- Save the user and complete any SSO or activation flow required by the tenant.
Required fields: Email address or username, Role
Watch out for:
- Exact navigation labels vary across Smarsh product modules.
- If SSO or SCIM is configured, IdP-side assignment may still be required.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | Unknown | Not documented |
| Domain whitelisting | Unknown | Automatic domain-based user add |
| IdP provisioning | Yes | Enterprise |
How to remove or deactivate users
- Can delete users: Unknown
- Delete/deactivate behavior: Official documentation on delete vs. deactivate behavior is not publicly accessible; no explicit statement could be verified.
- Open the Smarsh 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 supervision queues, integrations, or service credentials tied to the departing user.
| Data impact | Behavior |
|---|---|
| Owned records | Archived records and compliance artifacts remain tenant assets; public docs do not describe user-owned object semantics in detail. |
| Shared content | Shared reviews, policies, and supervised content remain available to the tenant unless separately changed. |
| Integrations | Review SCIM configuration, API credentials, and integration ownership during admin offboarding. |
| License freed | Seat reuse behavior is contract-dependent and not publicly documented in detail. |
Watch out for:
- Some tenants may still rely on support involvement for changes, so offboarding lead time matters.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Small Business | Archiving and compliance features for smaller organizations | From $15/user/month |
| Enterprise | Full platform access including SCIM provisioning; custom pricing | Up to $50/user/month (1000+ users); custom negotiated |
- Where to check usage: Administration / Users and Roles
- How to identify unused seats: Review the current user list and any visible login or activity metadata. No public unused-seat report was verified.
- Billing notes: Pricing is volume-based and largely custom for mid-market and enterprise tiers. Public pricing figures are indicative only; actual contracts are negotiated directly with Smarsh.
The cost of manual management
Manual user management in Smarsh carries real operational drag. Reviewers report that provisioning and de-provisioning workflows are not fully self-service and often require opening a ticket with Smarsh support.
Without a clear path to audit active versus inactive seats, license sprawl is difficult to catch - and at up to $50/user/month at Enterprise scale, unused seats are expensive to overlook. Pricing is volume-based and contract-negotiated, so there is no public rate card to cross-check against.
The decision
Manual management is viable only for small, stable teams where headcount changes are infrequent and compliance risk from stale accounts is low. Every app handling regulated communications data - Smarsh included - becomes a liability when offboarding lags behind actual departures. SCIM provisioning via an Enterprise plan is the practical path to reliable lifecycle automation.
If Enterprise tier is not in scope, factor in the ongoing support overhead before committing to a manual workflow.
Bottom line
Smarsh's manual user management is constrained by limited self-service tooling and a documented reliance on vendor support for provisioning changes. The permission model is role-based but not publicly detailed, and seat auditing lacks in-product transparency.
Teams managing more than a handful of users should treat SCIM provisioning at Enterprise tier as a prerequisite, not an upgrade - the alternative is a support-mediated workflow that scales poorly and leaves compliance gaps open between ticket submission and resolution.
Automate Smarsh 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.
