Summary and recommendation
Spiff 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.
Spiff is a sales commission management platform used by finance, revenue operations, and sales operations teams to automate incentive compensation plans.
Administrators manage users, plans, and teams from a centralized table view, with the ability to add effective dates on any user or plan and lock historical statements.
The platform surfaces real-time commission statements to every app user - reps, managers, and finance - across web, mobile, and Salesforce.
Publicly available documentation on the specific admin console path, user types, permission model granularity, and step-by-step add/remove user flows is sparse.
The research did not surface a confirmed admin console URL or enumerated role definitions from official Spiff help documentation.
Quick facts
| Admin console path | Settings / Administration > Users and Roles (exact labels vary by tenant) |
| 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 |
|---|---|---|---|---|---|
| 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: Spiff 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 | Yes | Enterprise |
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 seat | $75/user/month (Pro tier, per pricing seed data; Enterprise pricing is custom) |
- 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: Pricing seed data indicates $75/user/month for Pro tier; Enterprise pricing is custom. These figures could not be independently verified against a current official pricing page at research time.
The cost of manual management
Spiff uses named user seats. The Pro tier is listed at $75/user/month; Enterprise pricing is custom and requires direct engagement with Spiff's sales team.
These figures are drawn from third-party sources and could not be independently verified against a current official Spiff pricing page at research time - treat them as directional only.
No usage-check path or method for identifying unused seats was confirmed in publicly available documentation. License reclamation workflows are not described in Spiff's public help content.
The decision
Manual user management in Spiff is viable for smaller teams or organizations not yet on the Enterprise plan, but the absence of documented self-serve admin flows is a meaningful gap. Every app user who needs commission visibility - reps, managers, finance - requires a named seat, so seat hygiene directly affects cost at scale.
If your organization is on or moving to the Enterprise plan and uses a centralized IdP, SCIM provisioning is the more defensible path for lifecycle management. Manual management without SCIM introduces offboarding risk, particularly for a platform where departing reps retain access to real-time commission data until manually removed.
Bottom line
Spiff's manual user management story is underdocumented in public-facing resources: admin console paths, role definitions, and deactivation steps were not confirmed at research time.
What is clear is that every app user consumes a named seat, making unused-seat audits important for cost control - yet no self-serve usage-check path is publicly described.
Teams managing more than a handful of users should treat SCIM on the Enterprise plan as the intended provisioning path rather than a premium add-on.
Automate Spiff 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.
