Summary and recommendation
Champify 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.
Champify is a pipeline intelligence tool that tracks job changes among former customers and champions, surfacing warm leads when those contacts land at new companies.
It does not offer native SCIM provisioning, so every app lifecycle action - adding users, removing leavers, adjusting access - must be handled manually through whatever admin interface Champify exposes internally.
Because pricing is structured around lead and contact volume rather than per-seat counts, the usual levers IT teams pull to control license spend (seat audits, license reclamation) do not map cleanly onto Champify's model.
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 | 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: Champify 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 | No | 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 |
|---|---|---|
| Pro | 5,000–10,000 leads tracked | $3,000/month (as referenced in pricing seed; not confirmed via live pricing page) |
| Business | Custom lead volume | Custom pricing |
| Enterprise | 80,000+ contacts | Custom pricing |
- 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 based on lead/contact volume rather than per-seat user counts, based on available pricing seed data. Seat-level billing details are not publicly documented.
The cost of manual management
Without automated provisioning, every new hire who needs Champify access requires a manual invite, and every departing employee requires a manual removal. In a sales-heavy org with regular rep turnover, that overhead compounds quickly across every app in the stack - Champify included.
There is no publicly documented path to check active user counts or identify unused access from an admin dashboard, which means identifying stale accounts requires direct coordination with Champify's support or account team. Billing is tied to contact volume (Pro starts at 5,000–10,000 leads;
Enterprise covers 80,000+ contacts), so overpaying for unused capacity is a real risk if offboarding is delayed.
The decision
Champify fits organizations running account-based or champion-led pipeline motions, particularly those already using Salesforce or HubSpot as a CRM backbone. The absence of SCIM or a public user API means IT and RevOps teams must build manual processes around access management from day one.
If your org requires automated provisioning as a baseline for SaaS adoption, Champify's current feature set does not meet that bar without a direct agreement with their team on a supported path.
Bottom line
Champify delivers clear value for sales teams tracking champion job changes, but it places the full burden of user lifecycle management on admins. Every app in a well-governed SaaS stack needs a documented provisioning and deprovisioning path;
Champify currently lacks one in the public record. Teams adopting it should establish a manual offboarding checklist and revisit automation options directly with Champify's account team, particularly as headcount scales.
Automate Champify 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.
