Zoom User Management Guide

• Model type: hybrid
• Description: Zoom uses a combination of fixed system roles (Owner, Admin, Member) and optional custom roles. System roles are hierarchical and account-wide. Custom roles allow scoped admin permissions - for example, managing only Zoom Rooms or only viewing reports - and are assigned in addition to or instead of the default Admin role. User Groups are also available to apply settings policies to subsets of users without granting admin access.
• Custom roles: Yes
• Custom roles plan: Business plan or higher
• Granularity: Custom roles can be scoped to specific admin portal sections: User Management, Dashboard, Reports, Zoom Rooms, Zoom Phone, Webinars, Account Settings, and more. Each section supports read-only or edit access configured independently.

1. Sign in to the Zoom Admin portal at https://zoom.us/account/user
2. Navigate to Admin > User Management > Users
3. Click the 'Add Users' button in the upper right
4. Enter the user's email address (required)
5. Select User Type: Basic or Licensed
6. Optionally assign Department, Job Title, Location, and User Group
7. Optionally assign add-on features (Zoom Phone, Webinar, Large Meeting) if licenses are available on the account
8. Click 'Add' to send an invitation email to the user
9. User must accept the invitation email to activate their account; alternatively, use the API 'autoCreate' action type to bypass the invitation flow and create the account immediately

Required fields: Email address, User Type (Basic or Licensed)

Watch out for:

• Users added via invitation ('create' action type) must accept the email invite before their account is active. Unaccepted invitations appear as 'Pending' in the user list but still consume a Licensed seat if one was assigned.
• If the user's email domain is not associated with the Zoom account, the user may be prompted to create a separate personal Zoom account rather than joining the organization. Domain association must be configured first under Account Settings > Account Profile.
• Adding a Licensed user when no seats remain will prompt the admin to purchase additional licenses. The add action will not complete until a seat is available.
• Users with an existing personal Zoom account on the same email address must disassociate or transfer their personal account before they can join the organization account. This step is not automated.
• Basic users do not consume a paid seat but also do not receive Licensed features. Upgrading them later requires available Licensed seats on the account.
• Bulk CSV import does not support assigning add-on licenses (Zoom Phone, Webinar, Large Meeting) at import time. Add-ons must be assigned individually or via API after the import completes.

• Can delete users: Yes
• Delete/deactivate behavior: Zoom supports both deactivation and permanent deletion. Deactivation suspends the user's access while retaining their data, settings, and license assignment - the Licensed seat is NOT freed by deactivation alone. Deletion permanently removes the user account from the organization; admins are prompted to optionally transfer the deleted user's cloud recordings, scheduled meetings, and webinars to another user before confirming deletion. Deletion is irreversible and cannot be undone.

1. Sign in to the Zoom Admin portal at https://zoom.us/account/user
2. Navigate to Admin > User Management > Users
3. Locate the user by searching their name or email address
4. Click the '...' (More) menu next to the user's name
5. Select 'Deactivate' from the dropdown menu
6. Confirm the deactivation in the confirmation dialog
7. User status changes to 'Inactive'; they can no longer sign in but their data and seat assignment are retained

Watch out for:

• Deactivating a user does not reclaim their paid seat. Admins must explicitly downgrade the user to Basic or delete the user to free the license for reassignment or billing reduction.
• Deletion is permanent and cannot be undone. Zoom does not provide a recycle bin or recovery period for deleted user accounts.
• Cloud recordings owned by a deleted user must be transferred before deletion or they are permanently lost. The transfer prompt appears during the deletion flow but can be skipped, resulting in unrecoverable data loss.
• Scheduled meetings and webinars owned by the deleted user are cancelled. Attendees are not automatically notified of the cancellation.
• If the user was the sole manager or owner of a Zoom Phone call queue, auto-receptionist, or shared line group, those must be reassigned before deletion to avoid service disruption.
• Deactivated users still appear in the Users list under the 'Inactive' filter. They continue to count toward the account's user roster and their Licensed seat remains consumed until explicitly downgraded to Basic or deleted.
• Pending invitation users (status 'Pending') who were assigned a Licensed seat consume that seat even though they have never signed in. These must be manually identified and deleted or downgraded.

• Where to check usage: Admin > Account Management > Billing > Current Plan (shows purchased vs. used Licensed seats); also Admin > Reports > Active Hosts for meeting activity by user
• How to identify unused seats: Navigate to Admin > Reports > Active Hosts and filter by a date range (e.g., last 30 or 90 days) to identify Licensed users who have not hosted any meetings. The Admin > Reports > User Activity report also lists users who have not signed in within a specified period. Users with zero activity are candidates for downgrade to Basic or removal.
• Billing notes: Zoom bills per Licensed seat on a monthly or annual basis. Annual plans are prepaid; unused seats mid-term are generally non-refundable. Adding seats mid-cycle results in prorated charges for the remainder of the billing period. Removing Licensed users or downgrading them to Basic mid-cycle does not generate a refund on annual plans - the seat count reduction takes effect at the next renewal. Business plan requires a minimum of 10 Licensed users; dropping below 10 may require a plan downgrade. Pending invitation users assigned a Licensed seat consume that seat immediately upon assignment, before the invite is accepted.

Three billing traps catch Zoom admins repeatedly. First, deactivating a user does not reclaim their Licensed seat - you must explicitly downgrade the user to Basic or delete them to free the seat for reassignment or billing reduction.

Second, pending invitation users assigned a Licensed seat consume that seat immediately upon assignment, before the invite is ever accepted; unaccepted invites can silently accumulate paid seats for months. Third, on annual plans, removing or downgrading users mid-cycle does not generate a refund - the seat reduction takes effect only at the next renewal.

Identifying waste requires a manual detour: the default Users list has no native last-login column. Admins must run a separate Active Hosts or User Activity report under Admin > Reports, filtering by a 30- or 90-day window, to surface Licensed users with zero meeting activity.

Bulk CSV import also cannot assign add-on licenses (Zoom Phone, Webinar, Large Meeting) at import time - those must be assigned individually or via API after the import completes.

The deactivation-vs-deletion confusion is the most consistently reported admin pain point across Zoom's community forums. Admins routinely deactivate users expecting the license to be reclaimed automatically, only to find the seat still billed at the next cycle.

The fix - downgrade to Basic or delete - is not surfaced in the deactivation confirmation dialog.

Pending invite billing is a close second. Users who never accept their invitation still consume a Licensed seat from the moment it is assigned, and the Users list does not flag this prominently.

A third recurring complaint is the absence of a last-login column in the default Users view; pulling a separate Active Hosts report is an extra step that many admins discover only after overpaying for inactive accounts.

Common complaints:

• OAuth2 Authorization Code Grant migration from Bearer token authentication was a breaking change for existing SCIM and API integrations, with limited advance notice for some accounts.
• Domain association requirement can delay initial account setup; users with existing personal Zoom accounts on the same email must manually disassociate before joining an organization account - this is not automated.
• Zoom Phone user provisioning via SCIM has additional attribute requirements not fully documented in the main SCIM guide, causing provisioning failures for Phone-enabled users.
• Deactivating a user does not free the Licensed seat - many admins expect deactivation to reclaim the seat automatically, leading to unexpected billing charges.
• No native 'last login' or 'last active' column in the default Users list view; admins must run a separate Active Hosts or User Activity report to identify inactive users.
• Bulk CSV import does not support assigning add-on licenses (Zoom Phone, Webinar, Large Meeting) at import time; those must be assigned individually or via API after import.
• Pending invitation users still consume a Licensed seat if one was assigned, even before the user accepts the invite - these are easy to overlook in the user list.
• Custom roles are gated behind the Business plan; Pro plan admins have no way to create scoped admin access for partial delegation.
• Ownership transfer process is non-obvious and requires the current Owner to be active and accessible; there is no admin-initiated override path.
• Deleted user cloud recordings are permanently lost if the data transfer step is skipped during the deletion confirmation flow.

Community observations (summarized from cited discussions):

• We deactivated a bunch of users thinking it would free up our licenses for the month, but Zoom still charged us for them. You have to actually delete them or downgrade to Basic to get the seat back. - Zoom Community forum, Admin board - paraphrased from multiple recurring posts on deactivation vs. license reclamation (https://community.zoom.com/t5/Zoom-Admin/bd-p/ZoomAdmin)
• The pending invite users are the sneaky ones - they never accepted the invite but we were still paying for their Licensed seats for three months before we noticed. - Zoom Community forum, Admin board - paraphrased from multiple recurring posts on pending user billing (https://community.zoom.com/t5/Zoom-Admin/bd-p/ZoomAdmin)
• Wish Zoom had a proper 'last login' column right in the Users table. Having to pull a separate Active Hosts report just to find inactive users is an extra step that most admins don't know about. - Zoom Community forum, Admin board - paraphrased from multiple recurring posts on inactive user identification (https://community.zoom.com/t5/Zoom-Admin/bd-p/ZoomAdmin)

Manual administration in Zoom's portal is workable for teams under roughly 50 users with stable headcount and a single IdP. The console covers every app lifecycle action - add, deactivate, delete, downgrade, role assignment - without requiring API access or additional tooling.

The model breaks down at scale or with high turnover. Bulk CSV import cannot assign add-ons, domain association must be pre-configured before invitations go out, and users with existing personal Zoom accounts on the same email must manually disassociate before joining - none of this is automated.

Teams running frequent onboarding cycles or managing Zoom Phone alongside core licensing will hit these friction points regularly.

If your IdP supports SCIM, the Business plan threshold unlocks SCIM 2.0 provisioning and SSO, which eliminates most of the manual invite and seat-reclamation overhead. That is the natural upgrade path before investing in API-level automation.

Bottom line

Zoom's manual admin workflow is straightforward for small, stable teams but carries three hard-to-avoid cost risks: deactivation does not free seats, pending invites consume licenses immediately, and annual plan seat reductions only apply at renewal.

Every app has provisioning quirks - Zoom's are concentrated in license reclamation and the absence of inline activity data in the Users list.

Teams with more than moderate headcount churn, Zoom Phone deployments, or add-on license complexity will find the manual console increasingly inefficient and should evaluate SCIM provisioning (Business plan required) or API automation to close the gaps.