00 · Header

T1 · Control Hub & Platform Foundations

Locations & Sites

A location is a physical address that can hold both calling and workspaces. A user belongs to one location. A workspace belongs to one location. Webex generates a Location ID. Changing the location time zone does not change the time zone already stored on an auto attendant, hunt group, or call queue.

Expand all sections

01 · Executive summary

Five lines, then why it matters

• CSV create leaves Location ID blank. CSV edit does not change Location ID. Country in the CSV is the 2-letter code. [cite:1]
• Floors are a number plus an optional name, on the Floors tab. The workspace-locations API is the floor-capable endpoint. /v1/locations is the calling-locations API after the migration off the previous calling locations API. [cite:1]
• Adding or removing a user on a location applies the organization license template when one exists, unless the user is on a group template or you are managing them with CSV or the API. [cite:1]
• A Webex Calling workspace cannot move to a new location until the Calling license is removed, the workspace is moved, and Calling is entitled again. [cite:1]
• On create, an auto attendant, hunt group, or call queue takes the location time zone. After creation there is no way to alter that feature time zone. A different time zone from the location is not supported. [cite:1]

02 · Architecture map

One address, then the objects that may live there

• 1Users
• 2Workspaces
• 3Floors
• 4Calling

flowchart TB
  Loc[Location] --> Users
  Loc --> Workspaces
  Loc --> Floors
  Loc --> Calling

Studio asset still required: assets/diagrams/T1-R04/arch.svg

03 · Concept deep-dive

The address is the anchor

Locations organize users and workspaces by a physical location identified by an address. The same location can carry calling and workspace management. The article’s header on the retrieved page is June 05, 2026. [cite:1]

Create and identify

Delete, move, and time

04 · Ecosystem

Ecosystem and sister technologies

Glossary

Location

A physical address that organizes users and workspaces, and can hold calling and workspace management together. [cite:1]

Location ID

The identifier Webex generates at create time. Leave it blank in a CSV row that adds a location. Do not edit it. [cite:1]

Floor

A number, and an optional name, on a location. [cite:1]

Disable calling

The action required before a Calling location can be deleted. [cite:1]

-CALL suffix

The rename applied when a migrated calling location collided with an existing name. [cite:1]

Workspace location versus calling location

Older orgs could have both. A workspace can now be assigned to one location. Double assignment is not supported. [cite:1]

Emergency Service Address

Mandatory for U.S. and Canada Cisco Calling Plan locations in the trunk and dial-plan article. It is set on the location’s PSTN connection. [cite:2]

Routing prefix

A per-location prefix, length 1–7, set under the location’s Calling dialing settings. [cite:3]

Mind map

mindmap
  root((Location))
    Users
    Workspaces
    Floors
    Calling
    PSTN

Sister-technology matrix

Integration edges

Cross-platform bridges

Future-integration hooks

• Canon planning: a CSV of location names and 2-letter countries taken from a download, with Location IDs left untouched. Study sheet only.
• Consolidate a -CALL pair by copying information, deleting the non-suffixed location, and renaming. The article says there is no functional impact from the suffix itself. [cite:1]
• The article says a fix for the license-template side effect will be rolled out very shortly. re-check that sentence before you rely on the side effect still happening.

Ecosystem troubleshooting

05 · Flow

From an address to a Calling tab

06 · Config

Click paths

1. Sign in to Control Hub. Management > Locations > Manage location > Create manually. [cite:1]
2. Enter a unique name, a country, and a street address. Pick a suggestion if you want the map. Set email language and time zone. [cite:1]
3. Add a floor now or later: Floors tab, Add floor, required floor number, optional name. [cite:1]
4. Create. Record the Location ID. Use What’s next to set up Calling, workspaces, floors, and users. [cite:1]
5. Bulk: Manage location > Add and edit by CSV. Download data or the template. Leave Location ID blank for new rows. Country is the 2-letter code. [cite:1]
6. Add users from the location: Actions > View users > Manage users. Manual add is up to 25. You can also paste email addresses separated by commas. Then assign Messaging, Meeting, or Calling. [cite:1]
7. Or open the user: Profile > User details > Locations, choose the location, Save. [cite:1]
8. Calling: open the location, Calling tab, Set up calling. PSTN choices are the trunk article’s job after this. [cite:1] [cite:2]
9. Delete one location with Actions > Delete location. Delete many with Manage location > Delete by CSV and a file whose Location ID column lists only the locations to remove. [cite:1]
10. For Puerto Rico, Guam, American Samoa, or the U.S. Virgin Islands, set the country to the territory when the numbers are territory-specific. [cite:1]

Screenshot placeholder. The paths above are the article.

07 · Limits

Numbers the article states

08 · Troubleshooting

Ten failures that follow from the article

09 · Self-question ladder

Twelve rungs

10 · Lab

Address desk, no production org

• Goal: mark ten location actions as allowed or blocked using only article ajh6iy.
• Prereq: this room. Do not delete a production location.
• Step 1. CSV row for a new location has a Location ID filled in. Expected: the article says leave it blank.
• Step 2. Manual add of 30 users from the location screen. Expected: the manual path says up to 25. CSV is the bulk path.
• Step 3. Delete a Calling location before Disable calling. Expected: blocked.
• Step 4. Country United States for a Guam location that needs a Guam number. Expected: territory-specific numbers are blocked.
• Step 5. Change the location time zone and expect the hunt group schedule to move. Expected: the feature time zone stays.
• Evidence: the ten marks and the sentence you used.
• Break it: plan a delete CSV that still contains a location you want to keep. Recovery: remove that row, including its Location ID, before upload.
• Reflection: which of your sites are names without a street the suggestion list would recognize.

11 · Quiz

Twelve questions

12 · Audio

Slots for Studio

13 · Interview

Oral answers

30 seconds. A location is a physical address. One user, one workspace. Webex issues the Location ID. Calling and workspaces can share it. I do not delete a Calling location until I disable calling and remove Calling licenses from the people and places that still have them.

2 minutes. Manual create needs name, country, and street. The map appears when I pick a suggested address. CSV country codes are two letters. New CSV rows leave Location ID blank. Floors need a number. Manual user add from the location is 25. Changing the location time zone does not move an auto attendant, hunt group, or call queue, because those features copied the time zone at creation. A migrated name collision shows up as a -CALL suffix. Double-assigned workspaces are not supported.

30 seconds, territories. Puerto Rico, Guam, American Samoa, and the U.S. Virgin Islands use the territory as the country when the numbers are territory-specific. United States as the country blocks those numbers.

2 minutes, neighbors. PSTN is chosen on the location after it exists. U.S. and Canada Cisco Calling Plan locations need an emergency service address. The routing prefix is also per location. A survivability gateway is per site, in the local network. Adding a user here can apply the organization license template when preserve is off. Group templates, CSV, and the API are the paths that article excludes.

What you will say about an organization-wide location cap. This article does not state one. The 250 figure belongs to how many locations one Webex Calling administrator can be assigned, and that sentence is in the delegation article.

14 · Citations

1. Locations in Control Hub — help.webex — article ajh6iy — help.webex.com article ajh6iy — header June 05, 2026 — retrieved 2026-10-14. Create fields, Location ID, one user, one workspace, 25-user manual add, delete gates, floors, CSV, territory countries, time zone freeze, -CALL suffix, /v1/locations, workspace-locations API.
2. Configure trunks, route groups, and dial plans for Webex Calling — help.webex — article n0xb944 — help.webex.com article n0xb944 — retrieved 2026-10-14. PSTN assigned on the location. ESA for U.S. and Canada Cisco Calling Plan locations.
3. Configure Webex Calling for your organization — help.webex — article njvdjf2 — help.webex.com article njvdjf2 — routing prefix length 1–7, unique per location. Detail lives in T2-R03.
4. Delegate location administration — help.webex — article 760wbi — help.webex.com article 760wbi — header August 05, 2026 — a Webex Calling administrator can administer up to 250 assigned locations. That is not an organization-wide location cap.
5. Site survivability for Webex Calling — help.webex — article d68vi1 — help.webex.com article d68vi1 — header July 06, 2026 — each site that deploys Site Survivability requires a Survivability Gateway in the local network.
6. Migrate Unified CM to Webex Calling, introduction — help.webex — article nbedetf — help.webex.com article nbedetf — header January 14, 2026 — plan phase collects location details including emergency response address, users, internet access, and PSTN access.

15 · Re-engineer later

• Open questions: whether the license-template side effect described as “rolled out very shortly” has shipped.
• Facts still TODO-verify: 0. That side-effect sentence is re-check.
• Assets missing: location screenshot, audio.
• Ideas for v1.0: a CSV column cheat sheet taken from a downloaded template, with no customer data.
• Next review: when ajh6iy changes the delete gate or the one-location rule.