Perplexity User Management Guide

• Model type: role-based
• Description: Perplexity Enterprise uses a two-role model: Admin and Member. Admins manage the organization; Members consume AI features. No intermediate roles or custom permission sets are available. Role assignment is either manual via the admin console or automated via IdP group-to-role mapping through SCIM/SSO.
• Custom roles: No
• Custom roles plan: Not documented
• Granularity: Coarse - only Admin vs. Member distinction. No per-feature or per-Space permission controls documented.

1. Navigate to perplexity.ai/settings/admin.
2. Select 'Members' or 'Invite Members' in the admin console.
3. Enter the invitee's email address and select their role (Admin or Member).
4. Click 'Send Invite'. The invitee receives an email to accept and activate their seat.
5. Alternatively, configure SCIM provisioning via Okta, Microsoft Entra ID, or Google Workspace to auto-provision users from your IdP.

Required fields: Email address, Role (Admin or Member)

Watch out for:

• Invitations are email-based; users must accept the invite before the seat is active.
• SCIM auto-provisioning requires SSO to be configured first and is only available at 50+ seats (Enterprise Pro) or any Enterprise Max subscription.
• IdP-initiated sessions are not supported; users must initiate login from Perplexity's login page even with SSO enabled.
• Domain-based auto-join (domain whitelisting for automatic seat assignment) is not documented as a supported feature.

• Can delete users: Unknown
• Delete/deactivate behavior: Perplexity's admin documentation does not clearly distinguish between deactivation and permanent deletion of user accounts. Admins can remove members from the organization (revoking access), but whether underlying account data is deleted or merely deactivated is not explicitly documented in publicly available official sources. SCIM deprovision from the IdP will revoke access.

1. Navigate to perplexity.ai/settings/admin.
2. Select 'Members'.
3. Locate the user and select the option to remove or revoke their membership.
4. Confirm removal. The user loses access to the organization's Enterprise features immediately.
5. If SCIM is configured, deprovisioning the user in the IdP (Okta, Entra, Google Workspace) will automatically revoke their Perplexity access.

Watch out for:

• Annual Enterprise contracts may not allow mid-term seat reduction; seat removal may not reduce the invoice until renewal.
• SCIM deprovision is the recommended path for automated offboarding; manual removal requires admin console access.
• No documented grace period or re-activation window after removal.

• Where to check usage: perplexity.ai/settings/admin → Usage or Analytics section (exact label may vary by account configuration)
• How to identify unused seats: Admin console provides member list with last-active or usage data; specific 'inactive seat' reporting is not explicitly documented in official sources.
• Billing notes: Enterprise Pro requires a minimum of 5 seats (minimum seat count per official pricing pages; SCIM requires 50+ seats). Enterprise Max has no documented minimum seat count for SCIM. Annual billing is discounted vs. monthly. Seat additions mid-contract are prorated; seat reductions may only take effect at renewal depending on contract terms.

Without SCIM, onboarding is email-invite-only: navigate to perplexity.ai/settings/admin, select 'Invite Members', enter each email, assign a role, and wait for the invitee to accept before the seat activates. There is no documented CSV bulk-import path, so large onboarding batches require one invite per user.

Offboarding carries its own friction. Admins must manually locate and remove each member in the console. Annual Enterprise contracts may not allow mid-term seat reductions, meaning a removed user's seat cost may persist until renewal.

The distinction between account deactivation and permanent deletion is not clearly documented in official sources, leaving data-retention questions open.

Role changes are equally manual without IdP group mapping. Because only Admin and Member roles exist, any permission adjustment is a binary flip - and it must be done by an Admin through the console or via IdP reconfiguration.

The 50-seat minimum for SCIM on Enterprise Pro is the most frequently cited barrier. Teams below that threshold that still need automated provisioning have no supported path short of upgrading to Enterprise Max.

The absence of IdP-initiated session support is a consistent pain point. Users cannot launch Perplexity directly from their Okta or Entra dashboard tile, which breaks the single-pane-of-glass experience most IT teams expect from SSO-connected tools.

Two additional gaps surface regularly: the binary role model (no Space-level or feature-level permissions) and the lack of clarity around what happens to a removed user's threads and search history. Neither issue has a documented workaround in official sources.

Common complaints:

• 50-seat minimum for SCIM access on Enterprise Pro is a barrier for smaller teams that still need automated provisioning.
• No IdP-initiated session support means users cannot launch Perplexity directly from their SSO portal (e.g., Okta dashboard).
• Role management is binary (Admin vs. Member only); no granular permissions for managing Spaces or restricting specific features.
• Lack of documented CSV bulk-import means large manual onboarding requires either SCIM setup or tedious one-by-one email invites.
• Clarity around data retention and what happens to a removed user's threads and history is absent from official documentation.
• Annual contract terms make it difficult to reduce seat count mid-year if team size shrinks.

Manual management is viable only for small, stable teams where seat counts rarely change and onboarding volume is low. The email-invite flow works, but it does not scale and offers no bulk tooling.

For teams at or above 50 seats on Enterprise Pro - or any team on Enterprise Max - SCIM via a supported IdP is the correct path. It eliminates manual invite and removal steps and ties user lifecycle directly to your existing identity workflows. SSO configuration is a hard prerequisite and must be completed first.

Teams below 50 seats on Enterprise Pro who need automated provisioning should evaluate whether Enterprise Max's per-seat cost is justified by the operational savings, or whether manual management is acceptable given their churn rate.

Bottom line

Perplexity Enterprise is a capable AI search platform with a straightforward two-role permission model, but its provisioning story has real constraints that affect every app in your stack that depends on consistent, automated user lifecycle management.

SCIM is available and follows standard SCIM 2.0 patterns, but it is locked behind a 50-seat minimum on Enterprise Pro and requires SSO to be live first.

Teams that meet those thresholds will find IdP-driven provisioning reliable; teams that do not will manage users manually through the admin console with no bulk tooling and limited visibility into inactive seats.