Control Hub managed Webex sites

Control Hub is the administrative portal for all of Cisco's cloud collaboration products. You can manage every Webex service in one location. The benefits of managing sites in Control Hub include:

  • Unified license assignments across all Webex services.

  • Consistent security policies across all Webex services.

  • Common sign-in experience for all end users between different Webex services.

  • Modern administrator controls, such as Directory Connector, SCIM, and active directory groups.

  • License templates to assign multiple licenses to users automatically.

Site Administration managed Webex sites

Site Administration is an administrative portal for only the Webex Meetings Suite. If your organization decides to add more products, such as the Webex App or Webex Calling, you'd have to manage those products in Control Hub while still using Site Administration to manage Webex Meetings.


If you chose Site Administration at first but want to switch over to Control Hub, you can convert to Control Hub at any time.

Administrator experience comparison between Control Hub and Site Administration

The following table explains the significant differences between managing a Webex site in Control Hub and Site Administration.

Table 1. Administrative differences between Control Hub and Site Administration

Administrative experience

Control Hub

Site Administration

User management

Users are managed centrally in Control Hub, including assigning licenses and service level configurations.

Webex Meetings users and settings are managed in Site Administration. If you have other Webex products, such as the Webex App, you have to manage the users and settings for that product in Control Hub.

Users will use the same credentials to sign in to both the Webex App and Webex Meetings.

If the Webex site is linked, then users can sign in to the Webex App using the same credentials for their Webex Meetings site.

Users can't request for host privileges or additional services from their Webex site landing page.

Users can request for host privileges or additional services from their Webex site landing page if an administrator allows it.

Administrators can't block users from changing their profiles, unless Directory Connector is set up.

Administrators can block users from changing their profiles.

There is no option to control whether hosts can change their avatars.

Administrators can control whether hosts can change their avatars.

Users can be assigned licenses across any Webex service and multiple Webex sites in one operation, including when a user is first created with an automatic license template.

Users can only be assigned licenses for one Webex site at a time.

Users can be automatically created through People and SCIM APIs, Directory Connector, and Azure Active Directory.

Users can be automatically created through SSO auto account creation and XML API.

Different groups of users in Active Directory can be assigned different licenses based on a license template.

Active Directory isn't available for Site Administration.

Deactivate or reactivate users on a Webex site by removing or adding licenses.

Deactivate or reactivate users on a Webex site with a check box.

External and internal participants

Administrators can identify internal participants with an internal tag option.

Administrators have to add a custom label to identify internal participants.


 

This option is only available for SSO-enabled sites.

Tracking codes

Tracking codes are optional for new hosts.

Administrators can make tracking codes required for new hosts.

Customizing email templates

Content of account onboarding emails, such as welcome emails, isn't customizable.

Content of account onboarding emails is customizable.

Administrator licensing and hosting

Administrators can manage a Webex site without consuming a license, but requires a license to host meetings.

Full admins in the organization has write access to all Control Hub managed Webex sites.


 

Administrators from partner organizations can host test meetings without consuming a license.

Administrators consume a license to become a site administrator and can host meetings.

Full admins in the organization owning multiple Webex sites don't automatically have administrative access to all Site Administration managed sites.They must be explicitly granted administrative access to each Site Administration Webex site.

Hosts in other companies or organizations

Users must be in the Control Hub organization to be assigned a host or attendee license in Webex Meetings.

A host on a Webex site can belong to any company or organization.

Multiple Webex sites

All Webex sites in Control Hub share common settings, such as user creation and how users authenticate to Webex.

Users can only have one password across all Webex services. The same user can't have different passwords in different Webex sites.

If an organization is configured for SSO, then all Control Hub managed Webex sites in the same organization follow the same SSO.

Each Webex site is autonomous and the same user can have different email addresses and passwords across different Webex sites.

A company with multiple Webex sites can choose which Webex sites to enable or disable SSO for.

APIs** and integrations

Control Hub uses People REST APIs for user management, such as creating or licensing users. Other configurations can use Webex XML APIs.

API integrations can be built entirely with Webex XML APIs.

Authentication with username not supported for Webex Webex XML APIs. Authentication with email address supported for Webex XML APIs.

Authentication with username or email address and password supported.

Admins bypassing SSO

External admins can bypass SSO of the organization that owns the Webex site.

Admins can bypass a Webex site's SSO to sign in if the credentials are stored in the Webex site.

SSO for multiple sites

All sites share the same SSO configurations and identity provider (IdP). You can either have the same SSO for all sites, or no SSO at all.

Each site can be set up with different SSO configurations and IdPs.

SSO authentication for attendees

This feature isn't available at this time for Control Hub managed sites.

In the future, we're working on allowing admins to configure Control Hub to require sign in for all atendees whose email addresses match domains claimed by the organization. This will apply to all users in the organization, and it'll apply when those users are joining all meetings, including external meetings.

Admins can require "SSO authentication for attendees" for participants whose email addresses match specific domains.


 

This requirement only applies to meetings on that site.


** API integrations done for Site Administration managed Webex sites may need to be modified in order to work in Control Hub managed Webex sites if you decide to update to Control Hub later on.

API integrations should be tested thoroughly to make sure that all features are working after Webex sites are updated from Site Administration to Control Hub.

Customized email templates

Some of the email templates in Site Administration aren’t applicable to Control Hub, so customization for those email templates isn't applicable in Control Hub managed sites. For example, self sign-up isn't supported in Control Hub managed sites, welcome emails are controlled through licensing of users, and admins aren't involved in user password management.

The following email templates aren't customizable in Control Hub managed sites, but you can customize these emails in Site Administration:

  • Export Finished or Aborted Notification

  • Import Finished or Aborted Notification

Comparison chart for user features in meetings

Feature

Control Hub

Site Administration

Pre-Meeting Features

Scheduling Option

NA

If administrators configured site with "SSO authentication for attendees", then hosts can:

  • Restrict events to invited attendees only in the Webex Events (classic) scheduler.

  • Restrict meetings to invited attendees only in the Webex Meetings scheduler.

Join Audio Portion of PCN Before Host

NA. Attendees have to wait in lobby until the host joins.

Yes

In-Meeting Features

Display Suffix in Participants List

If the Display internal user tag in participant list is enabled by the admin, a suffix will show as internal for authenticated users and no suffix will show for non-authenticated users. SSO isn't required for this feature.

Administrators can customize the suffix for authenticated and non-authenticated users. SSO is required for this feature.

End User Sign In Experience

Consistent sign in experience across all Webex sites and services. Users sign in with one email address for every service.

Users can have different email addresses or passwords across different Webex sites.