Locations in Control Hub
Locations allow you to organize users and workspaces based on a physical location. You can configure both calling and workspace management functions into the same location.
Locations help you arrange your organization’s workforce into logical groupings. For example, a multinational enterprise may have multiple offices around the world, each with markedly different Webex collaboration requirements.
Users and workspaces can be assigned to a location, identified by a physical address. For example, you may want to create a Headquarters location identified by an address in a specific city. Users in your organization can be assigned that location as their home office. Workspaces can be physical areas within that location, such as the Main conference room workspace in the Headquarters location.
In addition to the organizational benefits of locations, you can use a single location for both calling and workspaces. You can also apply settings templates and other administrative features to groups and locations.
To add a single location, follow the steps below. To add multiple locations using a CSV file, see Add or edit multiple locations.
Before you begin
1 |
Sign in to Control Hub, then under Management, select Locations. |
2 |
Click . |
3 |
Enter the following information about the location:
|
4 |
Add floors to the location you just created. You can also add floors later in either of the following ways:
|
5 |
Click Create to finish creating the location. A unique Location ID is generated by Webex. |
What to do next
To add or edit multiple locations using a CSV file, follow the steps below. To add a single location, see Add a single location.
Before you begin
1 |
Sign in to Control Hub, then under Management, select Locations. |
2 |
Click . |
3 |
If you already have a CSV file of locations and want to add to it or edit it, click Download data and make your changes. - or -
If you want to add locations using a new CSV file, click Download .csv template and add your locations.
|
4 |
Add or edit information about the location.
The following fields are required:
If you're not certain of your standard country, time zone, and language codes, add a location from Control Hub. You can then download the data and copy it directly to your spreadsheet. |
5 |
When you’re done editing your existing CSV file or adding locations to a new CSV template, drag and drop your CSV file into the box to upload it, or select Choose a file to browse to it. |
6 |
Click Upload. |
A user can only be assigned to one location.
Add users to locations in any of the following ways:
Add users in Control Hub | Follow the steps in Add users to locations manually or in the CSV file. If you have configured Webex Calling for users, you must assign a location to them. |
Assign locations to users one by one | Follow the steps in Assign users to locations one by one. |
Assign locations when you add multiple users | Follow the steps in add multiple users in Webex Control Hub with the CSV template. |
Use the API to add users to locations | Follow the steps in Add users to locations in the API. |
Add users to locations manually or in the CSV file
- Sign in to Control Hub, then under Management, select Locations.
- Select a location.
- Select
- Click Manage users, then click either Manually add users to add up to 25 users, or CSV add or edit to add users in bulk.
- Add the user's first name, last name, and email address, then click +.
You can also add users by entering their email addresses separated by commas.
- When you're done adding users, click Next.
- Assign a Messaging, Meeting, or Calling license to the users, then click Next.
- Click Add users.
- Click Finish.
Assign users to locations one by one
If this user has Webex Calling, see Special considerations.
- Log in to Control Hub, then select Users.
- Select the user.
- In the Profile tab, under , select the location from the drop-down list, then click Save.
Add users to locations in the API
Admins can manage locations and add users to locations in the API.
The previous calling locations API has been fully migrated to using /v1/locations. You can utilize this API endpoint to manage the calling workload.
The workspace locations API is located in https://developer.webex.com/docs/api/v1/workspace-locations. While the primary CRUD operations for /v1/workspace-locations will interact with the same database as /v1/locations, it provides additional capabilities, such as management of floors.
As a full administrator, you can assign administators to manage the Calling service and devices in a location.
You can view and edit the users and workspaces assigned to a location. For Webex Calling users, see Special considerations.
1 |
Sign in to Control Hub, then under Management, select Locations. |
2 |
Select a location. |
3 |
Select the tab and pane you want to edit, then click to make changes.
|
4 |
To view users and workspaces assigned to this location, select the Actions menu, then select View users or View workspaces. You can select a user or workspace and add a location. |
What to do next
Before you begin
1 |
Sign in to Control Hub, then under Management, select Locations. |
2 |
Select a location. |
3 |
Select .
|
4 |
Click Delete. |
To delete multiple locations using a CSV file, follow the steps below. To delete a single location, see Delete a location.
- If locations are not configured for Webex Calling, they can be deleted, and the users and workspaces will be unassigned from those locations.
- If locations contain users and/or workspaces that are configured for Webex Calling, they can't be deleted until you remove the Webex Calling license. For more information, see Special considerations.
1 |
Sign in to Control Hub, then under Management, select Locations. |
2 |
Select . |
3 |
If you already have a CSV file of locations, click Download data and make your changes.
|
4 |
When you’re done editing your CSV file, drag and drop it into the box to upload it, or select Choose a file to browse to it. |
5 |
Click Upload to delete. |
6 |
Click Confirm. |
1 |
Sign in to Control Hub, then under Management, select Workspaces. |
2 |
Click Add workspace. |
3 |
Add the workspace name (required), as well as optional details such as the type of workspace (meeting room, open space, desk, etc.), the workspace capacity, and its location, then click Next. |
4 |
Add devices or click No device, then click Next. You can also add devices later by editing a workspace.
|
5 |
Add Calling or Scheduling services or select None, then click Next. You can also add services later. For more information, see Add services to an existing workspace with Webex Room, Desk, and Board Devices.
|
Using territory-specific numbers
When you add locations for Puerto Rico, Guam, American Samoa, or the U.S. Virgin Islands, it’s recommended to set these locations as country to use territory-specific numbers. Control Hub doesn't allow using territory-specific numbers when you set the country as the United States.
Webex Calling workspaces
If there are Webex Calling workspaces assigned to a location, you can’t move that workspace to a new location. You must first remove the Webex Calling license, move the workspace, and then re-entitle the workspace with the Webex Calling license.
To remove the Webex Calling license, see Turn off messaging or calling for Webex App users.
Licenses being added or removed
When adding users to or removing users from a location in Control Hub, the organization-license template (if one is defined) is applied to the user. This may result in additional licenses being added to the user, or licenses being removed from the user, if preserve license is turned off. This impacts users who have a different set of licenses from the organization template. This does not affect users who are using the group license template, or who are managing users with a CSV or the API. A fix for this issue will be rolled out very shortly.
Workspace locations and calling locations
Some organizations who have workspaces that were previously assigned to both the calling and workspace locations. As a workspace can now only be assigned to one location, we are proactively migrating these workspaces to the new experience and associating them with the calling location only. Customers with many workspaces are being handled with an exemption process. Contact your account representative if you have questions.
Exempt organizations | Special characteristics |
---|---|
Workspaces without a workspace location | Assigned to their calling location. |
The Workspace details page shows the calling location. | |
Workspace/device lists are filtered by the calling location. | |
Workspaces with both a workspace location and a calling location | Double-assigned to both the workspace location and the calling location. We recommend that you review your workspaces that are double-assigned, and assign the workspace to only one location. You can choose either the calling or the workspaces location that has been migrated. Cisco does not support double-assigned workspaces, and offers playbooks to customers to assist with the migration in scenarios where they have a large number of impacted workspaces. Contact your account representative for more information. |
The Workspace details page shows the workspace location, and does not show the calling location. | |
Workspace/device lists are filtered by the workspace location. If you filter by calling location, the relevant workspace is not shown. | |
The workspace location of a calling workspace can be changed. | |
The Location with Calling Details workspace summary card doesn't show the workspace count. | |
To find the calling location associated with a workspace, search for a workspace name under | .|
If the calling service is added to a workspace, it is also added to existing locations associated with that workspace, even if they don't have the calling service. |
Workspaces that are assigned to a single location will be fully migrated to that location.
All customers and partners see the new locations experience. New locations are created in the new infrastructure.
Duplicate workspace and calling location names
Existing workspace locations and calling locations have been migrated to a single location for both workspaces and calling. Duplicate names encountered in the migration process were renamed, as duplicate names are not allowed.
In cases where the migration of a calling location encountered a name conflict, the calling location was migrated with a -CALL suffix after its name.
There is no functional impact for this issue. For example, the administrator might just see Location1 and Location1-CALL in the list of locations.
If desired, the administrator can consolidate the two locations by completing these steps:
- Copy any relevant information from Location1 to Location1-CALL.
- Delete Location1.
- Rename Location1-CALL to Location1.