Countries and cities
The fixed Dashboard source maps the Enterprise Countries/Cities option to /all-settings?category=places. The Enterprise panel requires Enterprise eligibility and at least one returned Enterprise category; the all-settings route is restricted to level-0 administrators.
The source-defined page has Countries and Cities views, search, and country-to-city hierarchy. Its controls can create, update, enable, or delete geographic records, so the page is an operational manager rather than a read-only settings list.
Country and city records can affect addresses, availability, delivery or service coverage, and related business configuration. No production record should be created, changed, enabled, or deleted to validate this guide.
Source-defined data contract
Country creation requires name. An optional code is limited to 1–255 characters, and enabled is Boolean. City creation requires name and an existing parent country_id; an administrator assignment is optional and enabled is Boolean. City mutation routes remain scoped to their parent country.
Mounting the manager initiates authenticated reads for countries, including requested city and metadata relationships, plus city-manager and dropdown data. Those reads occur even before the Cities view is selected. The returned rows, available administrators, metadata, option lists, and project-specific enablement remain runtime-dependent.
Country and city mutations invoke API extension hooks. Multi-selection deletion is implemented as a sequence of individual deletes and stops when an error is encountered; it is not an atomic batch transaction, so earlier deletions can persist.
Evidence and capture boundary
The existing screenshot is retained as historical media. Safe evidence is limited to an approved synthetic, empty manager view showing navigation and inactive controls. Real countries, cities, administrators, addresses, businesses, metadata, or opened mutation controls must not be captured.
The fixed source establishes the route, validation, hierarchy, requests, and mutation semantics. It does not establish the records returned by a deployed project or the downstream effect of a particular geography change. Those claims require immutable deployment and runtime receipts.
The legacy control DASH-LEG-012 (/settings/places) remains a terminal audit-only reference to this same manager, not a second public page. Re-entry requires an approved synthetic Enterprise geography fixture that proves Enterprise entitlement, the returned places category, and unique direct-route behavior while no country, city, enable, edit, or delete action is opened or invoked.
Related guides: Enterprise settings