Summary and recommendation
Apollo.io 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.
Apollo.io user management lives at Settings > Users and Teams (https://app.apollo.io/#/settings/users/list). Every app in the sales tech stack has a permission model, and Apollo's is built around named permission profiles assigned at invite time-controlling feature-level access across prospecting, engagement, email visibility, CRM sync, sequences, and workflows.
Four seat types exist: paid user seats, Billing and Seat Manager seats (free, up to 5, no prospecting access), Call Assistant seats (deal review only, no prospecting credits consumed), and the standard Admin role. Custom permission profiles require the Organization plan; lower plans are limited to built-in defaults.
Quick facts
| Admin console path | Settings > Users and Teams |
| Admin console URL | Official docs |
| SCIM available | Yes |
| SCIM tier required | Enterprise |
| SSO prerequisite | Yes |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Admin | Full access to all admin settings including user management, billing, security (MFA, SSO, IP whitelisting), integrations, sequences, workflows, and all team data. Can access all sequences and workflows created by any user on the team. | Admin permission profile settings related to user management, billing, appearance, and interface are enabled by default and cannot be turned off. | All paid plans (one admin required per account) | Counts as a paid seat at the plan's per-user rate | If the sole admin leaves the organization, admin access must be recovered via Apollo support. Apollo recommends assigning admin permissions to at least 2 users. |
| User (standard, with permission profile) | Access determined by the permission profile assigned at invite time. Profiles can enable/disable prospecting, engagement, sequences, email visibility, CRM sync, and other features via granular toggles. Non-admins can only access sequences or workflows created by others if the creator shares access or the permission profile allows it. | Cannot access admin-only settings unless explicitly granted via a custom permission profile. Cannot view other users' emails unless the 'can see all emails' toggle is enabled in their profile. | All plans; custom permission profiles require Organization or Custom plan | Counts as a paid seat at the plan's per-user rate | Custom permission profiles (beyond built-in defaults) are gated behind the Organization or Custom plan. On lower plans, only default profiles are available. |
| Billing and Seat Manager | Access to admin and billing settings, tracking subdomain and integration settings, system activity settings, and the Apollo homepage. Can configure core admin settings but cannot use prospecting, engagement, or integration tools directly. | Cannot use prospecting, engagement, or Apollo Dialer features. Cannot update records synced from Salesforce, HubSpot, or Pipedrive CRMs, which can cause CRM sync failures if set as team sync credentials user. | Plan-dependent; not available on all plans. Requires upgrade if not included. | Free seat; does not consume a paid license. Up to 5 billing and seat manager seats allowed per account. | Converting a full user to a billing and seat manager frees their paid seat but removes all prospecting/engagement access. Converting a billing and seat manager to a full user consumes a paid seat and may trigger an immediate charge if no seats are available. |
| Call Assistant | Limited, non-admin access to deal and meeting management features: reviewing call recordings, tracking pipeline, attending sales meetings. Does not consume prospecting credits. | No access to Apollo Dialer, full prospecting tools, or engagement features. Cannot perform outbound prospecting. | Available on paid Apollo plans; rolling out progressively. Accounts signed up via Apollo Sales team must contact Customer Success to enable. | Separate call assistant seat type; cost not publicly specified in official docs. | Reassigning an existing full user to a call assistant seat causes them to lose all previously accessible permissions. Recommended only for new users. |
Permission model
- Model type: permission-sets
- Description: Apollo uses named permission profiles assigned per user. Each profile contains granular feature-level toggles (prospecting, engagement, email visibility, CRM access, sequences, workflows, billing, etc.). Admins can create, edit, and assign profiles at any time. Built-in profiles include Admin, standard user defaults, Billing and Seat Manager, and Call Assistant. Custom profiles allow per-feature toggle control.
- Custom roles: Yes
- Custom roles plan: Organization or Custom plan
- Granularity: Feature-level toggles per profile (e.g., prospecting on/off, email visibility scope, sequence access, CRM write access, billing access). Admins can expand features to view and configure sub-permissions per feature area.
How to add users
- Navigate to Settings > Users.
- Click 'New User'.
- Select a permission profile from the available list.
- Enter the email address(es) of the user(s) to invite.
- Click 'Send Invites'.
- Apollo sends an email invite; the user clicks 'Accept Invitation' to set up login or sign in via SSO.
Required fields: Email address, Permission profile selection
Watch out for:
- Inviting a user requires an available paid seat. If seats are exhausted, additional seats must be purchased before inviting.
- Free plans are limited to 1 seat after 100 days of active use.
- If an invited user's email is already linked to another active Apollo account, Apollo will prompt them to switch, which deactivates their previous account and does not migrate data.
- Newly created accounts appear under 'Current users' only after the invite is accepted.
- If an invite is not received, the user should check spam; admins can resend by repeating the invite steps.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | No | Not documented |
| Domain whitelisting | Unknown | Automatic domain-based user add |
| IdP provisioning | Yes | Organization plan (supports Okta and Entra ID via SCIM/SSO) |
How to remove or deactivate users
- Can delete users: No
- Delete/deactivate behavior: Apollo does not offer a permanent user deletion option from the admin UI. Admins can only deactivate users. Deactivated users can be reactivated at any time. Deactivating a user does not automatically free a paid seat or reduce the subscription; seat count must be managed separately in subscription settings.
- Navigate to Settings > Users.
- Click '...' (ellipsis) next to the user to deactivate.
- Click 'Deactivate'.
- Click 'Deactivate' again in the confirmation dialog.
- After deactivation, unlink the user's connected mailbox to prevent scheduled emails from being marked 'Not sent'.
- Reassign ownership of the deactivated user's contacts, accounts, sequences, deals, tasks, and workflows to another team member.
| Data impact | Behavior |
|---|---|
| Owned records | Contacts and accounts owned by the deactivated user remain in Apollo but require manual reassignment to a new owner. Apollo does not auto-reassign on deactivation. |
| Shared content | Active sequences owned by the deactivated user must be manually transferred. Scheduled emails from deactivated accounts are marked 'Not sent' if the mailbox is not unlinked and reassigned. |
| Integrations | The deactivated user's connected mailbox remains linked until manually unlinked by an admin. CRM sync credentials set to the deactivated user may cause sync failures. |
| License freed | Deactivating a user does NOT automatically reduce the seat count or billing. Admins must separately reduce seats in subscription management to affect billing. |
Watch out for:
- Deactivating the sole admin requires contacting Apollo support to regain access and reassign admin permissions.
- Scheduled emails from a deactivated user's mailbox will be marked 'Not sent' unless the mailbox is unlinked and emails are reassigned to another mailbox.
- Seat reductions are not permitted mid-contract on annual plans; deactivating a user does not reduce the billed seat count until the contract term allows it.
- Ownership of sequences cannot be bulk-updated across all sequences at once; each sequence must be updated individually.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Paid user seat | Full access to Apollo features as configured by the assigned permission profile (prospecting, engagement, dialer on eligible plans, CRM integrations, sequences, workflows). | Free: $0 (1 seat, limited credits); Basic: $49/user/month (annual) or $59/month; Professional: $79/user/month (annual) or $99/month; Organization: $119/user/month (annual) or $149/month, minimum 3 users |
| Billing and Seat Manager seat | Admin and billing settings access, tracking subdomain settings, system activity, Apollo homepage. No prospecting or engagement tools. | Free; up to 5 per account. Does not consume a paid license slot. |
| Call Assistant seat | Limited access to deal management, call review, meeting attendance, and pipeline tracking. No prospecting credits consumed. | Not publicly specified in official docs; available on paid plans. |
- Where to check usage: Settings > Plan Overview (Admin settings > Plan overview > Manage Subscription) to review seat count, credit usage, and billing details. Settings > License Settings for domain and seat management preferences.
- How to identify unused seats: No native 'unused seat' report is documented in official help articles. Admins can review the user list at Settings > Users to identify inactive or deactivated users and cross-reference with seat count in Plan Overview.
- Billing notes: Seat count increases take effect immediately and are charged immediately. Seat count decreases (downgrades) take effect immediately but refunds are not issued for mid-term downgrades. Switching from a paid plan to a free plan limits the account to 1 seat, with all other seats removed 10 days after downgrading. Credits do not roll over between billing cycles; unused credits expire at the end of each billing cycle. Additional credits cost $0.20 each with a minimum purchase of 250 credits (monthly) or 2,500 credits (annual). Organization plan upgrades require contacting Apollo Sales.
The cost of manual management
Deactivating a user does not free a paid seat-seat count reductions must be managed separately in subscription settings and are not permitted mid-contract on annual plans. There is no native unused-seat report; admins must manually cross-reference the user list at Settings > Users against seat count in Plan Overview.
When a user departs, sequence ownership cannot be bulk-transferred-each sequence must be updated individually. If the sole admin is deactivated, account recovery requires contacting Apollo support directly.
What IT admins are saying
Recurring friction reported across Trustpilot, Capterra, and G2 centers on three areas: pricing volatility (multiple price increases reported within single annual cycles), feature gating (SSO and SCIM locked to the Organization plan at $119/user/month annual, custom permission profiles also gated there), and SCIM IdP limitations (only Okta and Microsoft Entra ID are supported; Google Workspace and OneLogin are not).
Users on annual plans also report that credit policy changes and new feature rollouts do not apply retroactively to existing annual subscribers.
Common complaints:
- Enterprise lock-in for SSO/SCIM (Organization plan required)
- Limited to Okta and Entra ID for SCIM/SSO; Google Workspace and OneLogin not supported
- Deactivating a user does not automatically free a paid seat; seat reductions must be managed separately and are not permitted mid-contract on annual plans
- No bulk sequence ownership transfer; each sequence must be updated individually when reassigning a departing user's content
- Custom permission profiles gated behind Organization or Custom plan; lower plans cannot create custom roles
- Pricing has changed frequently, with users reporting multiple price increases over short periods
- Credits expire at end of billing cycle with no rollover, creating use-it-or-lose-it pressure
- Sole-admin lockout risk: if the only admin leaves, account access requires contacting Apollo support
- Billing and seat manager role not available on all plans; plan upgrade required for access
- Seat reductions not allowed mid-contract on annual plans; teams pay for unused seats until renewal
The decision
Every app that gates SSO and SCIM behind its highest commercial tier forces a real cost-benefit calculation, and Apollo is no exception-the Organization plan runs $119/user/month annual with a minimum of 3 users, and SSO must be fully configured before SCIM can be enabled.
Teams below that tier manage every user lifecycle action manually through the Apollo UI.
The Billing and Seat Manager role is useful for finance or ops stakeholders who need billing visibility without consuming a paid seat, but assigning it to a user who was previously a full seat holder removes all prospecting and engagement access immediately.
Call Assistant seats are best reserved for net-new users only-converting an existing full user to this role strips all previously held permissions.
Bottom line
Apollo.io's user management is functional but carries meaningful operational overhead at scale.
Every app requires seat hygiene, but Apollo's combination of no mid-contract seat reductions, no bulk sequence reassignment, no unused-seat reporting, and a $119/user/month annual floor for SSO/SCIM means that teams relying on manual administration absorb compounding costs in both time and license spend.
The permission profile system is genuinely granular once unlocked, but the Organization plan gate means smaller teams get limited role flexibility.
For any team managing more than a handful of seats, the absence of automated provisioning is a real gap-and the IdP restriction to Okta and Entra ID narrows the SCIM path further for teams on other identity providers.
Automate Apollo.io 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.
