Summary and recommendation
Reachdesk 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.
Reachdesk is a B2B gifting and direct-mail platform where seat counts are bundled into annual contracts rather than sold individually.
Plans run from 3 seats at the Business tier up to 10 seats at Enterprise, with send volumes fixed per tier.
Like every app that gates user management behind vendor touchpoints, adding or removing users outside those bundles requires going back to Reachdesk sales
there is no self-serve seat expansion in the admin console.
Quick facts
| Admin console path | Settings / Administration > Users and Roles (exact labels vary by tenant) |
| SCIM available | Yes |
| SCIM tier required | Contact Sales |
| 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 capabilities outside the modules or features enabled for the tenant. | Detailed built-in role names are not fully documented publicly. | ||
| Standard User | Can use the core product features exposed to their assigned role. | May not be able to manage tenant settings, integrations, or other users. | Exact privileges can vary by tenant configuration and contract scope. |
Permission model
- Model type: role-based
- Description: Reachdesk 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 before the user can sign in.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | Unknown | Not documented |
| Domain whitelisting | Unknown | Automatic domain-based user add |
| IdP provisioning | Yes | Contact Sales |
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, service accounts, or 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 content and workspace records typically remain available unless separately removed or reassigned. |
| Integrations | Review service credentials, workflow ownership, and integrations 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, integration, and service-account review, not just interactive login removal.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Named user seat | Seat counts are bundled per plan tier: 3 seats on Business ($20,000/yr), 5 seats on Company ($35,000/yr), 10 seats on Enterprise ($50,000/yr). Additional seats and send volumes available via negotiation. | Bundled into annual plan price; incremental seat cost not publicly disclosed. |
- 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: All plans are annual contracts. Seat counts and send limits are fixed per tier; overages or additional seats require contacting Reachdesk sales. Pricing data sourced from third-party references aligned with context seed; not confirmed on a current public pricing page.
The cost of manual management
Because user management is not fully self-serve, every app lifecycle event - onboarding a new rep, offboarding a departing one, or reallocating a seat - can require a touchpoint with Reachdesk's customer success team. That friction compounds across your stack when no automated provisioning is in place.
Unused seats are especially hard to identify: the admin view offers limited visibility into per-user send activity and budget consumption, making it difficult to reclaim licenses proactively.
The decision
Every app with contract-gated seat management creates recurring overhead when headcount changes frequently - Reachdesk is no exception. If your team size fits cleanly within a bundled seat tier and headcount is stable, manual management is workable but requires discipline around offboarding.
If you're running frequent onboarding cycles or need granular per-user reporting, the lack of self-serve controls and limited admin visibility will create compounding friction that SCIM provisioning is the practical path to resolving.
Bottom line
Reachdesk's seat model is contract-driven and tier-fixed, which means user management carries more operational weight than in usage-based SaaS tools.
Manual provisioning is feasible for small, stable teams but becomes a liability at scale - limited admin visibility, CS-dependent onboarding, and fixed seat bundles all work against clean joiner/mover/leaver hygiene.
Teams running frequent headcount changes should prioritize SCIM setup to keep access in sync without repeated vendor touchpoints.
Automate Reachdesk 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.
