Summary and recommendation
Influitive 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.
Influitive is a B2B advocate marketing platform built around a hub-and-challenge model.
Admins configure the hub, manage members, and build challenge programs;
Advocates (Members) interact only with the hub-facing experience to complete challenges and earn rewards.
There is no native SCIM support, so every app provisioning and deprovisioning action must be handled manually or via direct API calls.
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 | Full platform access including hub configuration, member management, challenge creation, reporting, and integrations. | ||||
| Advocate (Member) | Access to the advocate hub to complete challenges, earn rewards, and participate in community activities. | Cannot access admin configuration or reporting dashboards. | Advocate seats are counted against the plan's advocate limit (e.g., up to 100 advocates on the base AdvocateHub plan at ~$3,000/mo). |
Permission model
- Model type: role-based
- Description: Influitive 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 | 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, 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 |
|---|---|---|
| Advocate seat | Access to the advocate hub for completing challenges and earning rewards. | Counted against plan advocate limit; base plan listed at approximately $3,000/mo for up to 100 advocates. |
- 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 is plan-based with advocate count limits. AdvocateHub at ~$3,000/mo (up to 100 advocates); Upshot at ~$10,000/mo; Enterprise pricing is custom. Seat-level billing details are not publicly documented.
The cost of manual management
Influitive's pricing is plan-based with hard advocate-count ceilings. The base AdvocateHub plan is listed at approximately $3,000/mo for up to 100 advocates; Upshot is listed at approximately $10,000/mo;
Enterprise pricing is not publicly documented. Because seats are counted against plan limits, unreviewed inactive advocates directly consume capacity you are paying for. Seat-level billing granularity is not publicly documented, so identifying unused seats requires manual audits against your hub's member list.
The decision
Without native SCIM, every app in your stack that touches Influitive advocate records requires a manual or scripted workflow for joiner/mover/leaver events. Teams managing more than a handful of advocates will feel this gap most acutely at offboarding, where a departed advocate left active continues to count against the plan's advocate limit.
If your organization already maintains CRM or HR system data on advocates, a scripted sync via the REST API is the most reliable path to keeping records current.
Bottom line
Influitive works well as a standalone advocate hub when advocate volume is modest and admin overhead is acceptable.
The absence of SCIM and the two-role permission model mean that scaling provisioning across a larger advocate base, or enforcing fine-grained access controls, requires either custom API automation or disciplined manual processes.
Teams evaluating Influitive should factor in the operational cost of managing advocate lifecycle events without directory-sync support.
Automate Influitive 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.
