Summary and recommendation
People.ai 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.
People.ai is a revenue intelligence platform built for enterprise sales teams, surfacing activity data, CRM insights, and pipeline analytics. It uses a role-based access model with at minimum Admin and Standard User roles.
Specific role names, permission granularity, and whether custom roles are supported are not publicly documented - vendor engagement is required to confirm the full permission structure.
Neither SCIM provisioning nor a public user management API is documented. SSO via SAML is confirmed through the Okta Integration Network and referenced in Microsoft Entra materials, but automated provisioning and deprovisioning are not part of any publicly available integration spec.
This means People.ai cannot participate in the automated lifecycle flows that every app with SCIM support enables.
Quick facts
| Admin console path | Administrative settings inside the People.ai platform; detailed navigation is help-center gated |
| Admin console URL | Official docs |
| SCIM available | No |
| SCIM tier required | Enterprise |
| SSO prerequisite | No |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Admin | Full platform configuration, user management, integration setup, and data access controls based on publicly referenced role descriptions. | Enterprise (all plans are enterprise; specific tier not publicly documented) | Specific permission boundaries between Admin and non-Admin roles are not publicly documented. | ||
| User (Standard) | Access to revenue intelligence dashboards, activity data, and CRM insights as configured by admin. | Cannot manage other users, configure integrations, or modify org-level settings. | Enterprise | Seat cost and exact feature access per role are not publicly disclosed; requires vendor engagement. |
Permission model
- Model type: role-based
- Description: People.ai uses a role-based access model. Specific role names, granularity of permissions, and whether custom roles are supported are not publicly documented in accessible help center articles.
- Custom roles: Unknown
- Custom roles plan: Not documented
- Granularity: Not documented
How to add users
- Sign in to People.ai with administrative access.
- Open the administrative user-management area in the platform.
- Add the new user with their work email address and assign the appropriate role.
- If enterprise SSO is enabled, confirm the user is also assigned in the IdP before first login.
Required fields: Work email address, Role
Watch out for:
- User provisioning documentation is not publicly accessible; admin steps require login to the People.ai help center or direct vendor support.
- Okta SSO integration is confirmed via Okta Integration Network, but automated provisioning (SCIM) is not publicly documented as supported.
- Microsoft Entra (Azure AD) SSO support is referenced in vendor materials but provisioning workflow details are not publicly available.
| 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: No public documentation found distinguishing deactivation from deletion in People.ai. Behavior upon user removal is not publicly documented.
- Open the departing user's record in the People.ai admin area.
- Deactivate the user or revoke their platform access.
- Review connector ownership or CRM-linked responsibilities before final removal.
| Data impact | Behavior |
|---|---|
| Owned records | Not documented |
| Shared content | Not documented |
| Integrations | Not documented |
| License freed | Not documented |
Watch out for:
- No public documentation available on what happens to activity data, CRM-synced records, or connected integrations when a user is removed.
- License release process upon user deactivation is not publicly documented.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Enterprise platform user | Access to revenue intelligence dashboards, activity capture, and CRM-linked workflows under the customer contract. | Custom enterprise pricing; no public seat rates disclosed. |
- Where to check usage: Not documented
- How to identify unused seats: Not documented
- Billing notes: People.ai uses custom enterprise pricing. No public per-seat pricing or seat tier breakdown is available. All licensing details require direct vendor engagement.
The cost of manual management
Because People.ai lacks documented SCIM support, onboarding and offboarding must be handled manually through the admin console or via vendor support. The license release process upon user deactivation is not publicly documented, which means seat reclamation cannot be reliably automated or audited without direct vendor involvement.
Admin documentation is gated behind a login to the People.ai help center, so even routine tasks like adding or removing users require either an active support relationship or access to internal runbooks. This raises the operational cost of every user lifecycle event.
What IT admins are saying
Reviewers on G2 and Gartner Peer Insights consistently flag that initial setup and user onboarding are complex and heavily dependent on People.ai's professional services team.
Admin controls and configuration options are described as non-intuitive, with most changes requiring coordination with People.ai's customer success team rather than self-serve action.
Integration setup - particularly for CRM and email/calendar connectors - is cited as requiring significant admin effort. The absence of self-serve admin documentation is a recurring theme across reviews.
Common complaints:
- Reviewers on G2 and Gartner Peer Insights note that initial setup and user onboarding can be complex and heavily dependent on vendor professional services.
- Some users report that admin controls and configuration options are not intuitive and require support from People.ai's customer success team.
- Lack of self-serve admin documentation is a recurring theme; most configuration requires working directly with People.ai support or implementation teams.
- Integration setup (particularly CRM and email/calendar connectors) is cited as requiring significant admin effort and coordination with People.ai.
The decision
People.ai is appropriate for enterprise sales organizations that already have a vendor success relationship in place and can absorb the overhead of manual user lifecycle management. Unlike every app that supports SCIM, People.ai requires manual intervention at each provisioning and deprovisioning step, which increases audit risk and operational overhead.
Before committing, confirm directly with People.ai whether SCIM provisioning is available on your contract tier, what happens to activity and CRM-linked data when a user is removed, and how license reclamation is handled at offboarding.
Bottom line
People.ai delivers revenue intelligence capabilities for enterprise sales teams, but its identity and access management story is opaque. No SCIM provisioning is publicly documented, admin workflows are gated behind vendor support, and the full permission model is undisclosed.
Teams that need predictable, auditable user lifecycle management across every app in their stack should treat People.ai as a high-touch integration requiring explicit contractual clarity on provisioning, deprovisioning, and seat reclamation before deployment.
Automate People.ai 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.
