Summary and recommendation
Webex 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.
Webex user management runs through Control Hub (admin.webex.com), a centralized admin console that covers every app in the Webex portfolio - Meetings, Calling, Webinars, and Messaging - from a single pane.
Admins add users by email, assign service licenses, and optionally grant admin roles in one flow.
Because Webex sells each product as a separate license pool, seat counts for Meetings and Calling are tracked and exhausted independently.
Quick facts
| Admin console path | Control Hub (admin.webex.com) → Users |
| Admin console URL | Official docs |
| SCIM available | Yes |
| SCIM tier required | Business/Enterprise |
| SSO prerequisite | Yes |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Full Administrator | Complete access to all Control Hub settings: user management, licensing, calling, meetings, security policies, organization settings, and billing. | Cannot be restricted to a subset of admin functions without using a custom or limited admin role. | Any paid Webex plan | No additional seat cost for the admin role itself; consumes a licensed user seat | Full Admins can modify other Full Admins' settings; organizations should limit the number of Full Admins. |
| Read-Only Administrator | Can view all Control Hub settings and reports but cannot make changes. | Cannot add, edit, or remove users; cannot change any configuration. | Any paid Webex plan | No additional cost beyond licensed user seat | Useful for auditors or support staff who need visibility without write access. |
| Support Administrator | Can view user details and perform limited troubleshooting actions such as resetting PINs and viewing call history. | Cannot manage licenses, billing, or organization-wide settings. | Any paid Webex plan | No additional cost beyond licensed user seat | Scope is limited to user-level support tasks; cannot alter service configurations. |
| Device Administrator | Can manage Webex devices and workspaces within Control Hub. | Cannot manage user accounts, licenses, or calling/meeting policies. | Any paid Webex plan with device management | No additional cost beyond licensed user seat | Role is scoped to device and workspace management only. |
| Custom Administrator | Admin with a tailored subset of permissions selected from available Control Hub modules (e.g., Calling only, Meetings only, User management only). | Cannot exceed the permissions of a Full Administrator; scope is limited to modules selected at role creation. | Business or Enterprise plan | No additional cost beyond licensed user seat | Custom roles must be created by a Full Administrator; available permission modules depend on which Webex services are licensed. |
| Licensed User (Host) | Can host meetings, make/receive calls (if Calling licensed), use messaging, and access Webex services assigned by admin. | Cannot access Control Hub admin settings; cannot manage other users. | Requires an assigned Webex license (Meetings, Calling, etc.) | Consumes one paid license seat per the assigned service | Users without a license assignment can exist in the directory but cannot use paid features. |
| External User / Guest | Can join meetings or spaces when invited; limited to interaction within the specific meeting or space. | Cannot initiate meetings, access organizational content, or appear in the company directory. | No license required for the guest; host must have a valid license | No seat cost for guest/external participants | Guest access policies (e.g., external messaging restrictions) are controlled by the host organization's admin. |
Permission model
- Model type: hybrid
- Description: Webex Control Hub uses a role-based model with a fixed set of built-in administrator roles (Full Admin, Read-Only Admin, Support Admin, Device Admin) plus the ability to create custom administrator roles with granular module-level permissions on Business and Enterprise plans. End-user permissions are controlled through service license assignments and meeting/calling policies rather than individual permission toggles.
- Custom roles: Yes
- Custom roles plan: Business or Enterprise
- Granularity: Module-level for custom admin roles (e.g., Calling, Meetings, Devices, Users, Analytics). End-user feature access is policy-driven per service.
How to add users
- Sign in to Control Hub at admin.webex.com.
- Navigate to Management → Users.
- Click 'Add Users'.
- Enter the user's email address.
- Select the services and licenses to assign (Meetings, Calling, Messaging, etc.).
- Optionally assign an administrator role.
- Click 'Add' to send an activation email to the user.
Required fields: Email address
Watch out for:
- The user's email domain must be claimed and verified by the organization, or the user will be added as an external/unmanaged account.
- If the email address is already associated with a personal Webex account, the user must convert or merge that account before joining the organization.
- License availability must exist before assignment; adding a user beyond the purchased seat count will prompt a license purchase.
- Activation email is sent immediately upon adding; there is no draft/pending state for manual adds.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | Yes | Control Hub → Management → Users → Manage Users → CSV Import (download template from the same page) |
| Domain whitelisting | No | Automatic domain-based user add |
| IdP provisioning | Yes | Business or Enterprise (requires SSO and SCIM configuration) |
How to remove or deactivate users
- Can delete users: Yes
- Delete/deactivate behavior: Control Hub supports both deactivation and permanent deletion. Deactivating a user suspends their access and frees the license while retaining their account record and data. Permanently deleting a user removes the account from the organization; this action is irreversible. Admins can also remove a user from the organization without deleting the underlying Webex account, which dissociates them from the org.
- Sign in to Control Hub at admin.webex.com.
- Navigate to Management → Users.
- Search for and select the target user.
- Click the user's name to open their profile.
- To deactivate: toggle the user's status to 'Inactive' or remove all license assignments.
- To delete: scroll to the bottom of the user profile and select 'Remove User' or 'Delete User', then confirm the action.
| Data impact | Behavior |
|---|---|
| Owned records | Meeting recordings stored in the user's personal recording library may be deleted or become inaccessible depending on storage configuration. Recordings in cloud storage tied to the org may be retained per the org's retention policy. |
| Shared content | Messages and files shared in Webex spaces remain in those spaces and are accessible to other space members after the user is removed. The user's personal spaces are no longer accessible. |
| Integrations | OAuth tokens and third-party app authorizations associated with the user are revoked upon deletion. Bot and integration connections specific to that user will stop functioning. |
| License freed | Removing or deactivating a user frees the assigned license seat(s), making them available for reassignment immediately. |
Watch out for:
- Deletion is irreversible; the user's personal data and settings cannot be recovered after permanent deletion.
- If the user is the sole administrator of the organization, their account cannot be deleted until another Full Admin is designated.
- Users provisioned via SCIM/IdP should be deprovisioned from the IdP to prevent automatic re-provisioning after manual removal.
- Webex Personal Room meeting links associated with a deleted user will no longer function.
- Voicemail and call recordings associated with a Calling-licensed user may be permanently lost upon deletion; verify retention policy before deleting.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Webex Meetings (Free) | Up to 100 participants, 40-minute meeting limit, basic messaging | $0 |
| Webex Meetings Starter | Up to 150 participants, unlimited meeting duration, cloud recording, basic admin controls | Approximately $12–$14.50/user/month (varies by region and billing cycle) |
| Webex Meetings Business | Up to 200 participants, unlimited recording, advanced admin controls, custom branding | Approximately $25–$26.95/host/month |
| Webex Calling (Professional) | Cloud PBX, PSTN calling, voicemail, call queues, device management | Approximately $17–$25/license/month |
| Webex Webinars | Large-scale webinar hosting, attendee registration, Q&A, polling | From approximately $68.75/license/month |
| Webex Enterprise | All Webex services, FedRAMP option, up to 1,000 meeting attendees, unlimited recording, advanced security | Custom quote-based pricing |
- Where to check usage: Control Hub (admin.webex.com) → Management → Licenses - displays total purchased seats, assigned seats, and available seats per license type. Analytics → Meetings/Calling sections provide usage activity data.
- How to identify unused seats: Control Hub → Analytics → Meetings (or Calling) → filter by 'No activity' or sort by last active date to identify licensed users who have not used the service within a defined period. The Licenses page shows unassigned seats directly.
- Billing notes: Webex licenses are sold per named user/host seat, not concurrent usage. License counts are managed at the organization level in Control Hub. Adding users beyond purchased seat count requires purchasing additional licenses. Webex Calling and Webex Meetings are separate license pools and must be managed independently. Enterprise agreements may include true-up provisions; verify contract terms for overage handling.
The cost of manual management
License complexity is the primary operational burden. Every app a user needs - Meetings, Calling, Webinars - draws from its own seat pool, so admins must cross-check multiple license counts before provisioning at scale. Identifying unused seats requires navigating to Analytics → Meetings or Calling and filtering by last-active date;
there is no single consolidated 'unused licenses' report across all products. Organizations running Calling alongside Meetings face the steepest overhead, as Calling licenses carry a separate cost tier and must be managed independently.
What IT admins are saying
Community evidence is not specific enough to quote or summarize yet for this app.
The decision
Manual management in Control Hub is practical for organizations with stable, low-volume user changes and a single Webex product. It becomes operationally expensive when the org runs multiple Webex products simultaneously, because each license pool requires independent monitoring.
Teams that have already configured SSO and are on a Business or Enterprise plan should evaluate SCIM provisioning through their IdP to eliminate the re-provisioning risk and reduce per-user admin time. Organizations on Free or Starter plans have no SCIM option and must manage users entirely through Control Hub.
Bottom line
Webex Control Hub gives admins direct, role-gated control over every app in the Webex suite, but the multi-pool license model means that provisioning and deprovisioning correctly requires checking Meetings, Calling, and Webinars seat counts separately.
The built-in role hierarchy - Full Admin, Read-Only, Support, Device, and Custom - is well-suited to least-privilege delegation, but Custom roles require a Business or Enterprise plan. For organizations managing more than a handful of users, the manual workflow is functional but carries meaningful overhead;
the domain verification requirement, personal-account merge friction, and absence of a unified unused-seat report are the three areas most likely to create recurring admin work.
Automate Webex 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.
