Locations¶
Locations document where your IT infrastructure is hosted -- data centers, cloud regions, office server rooms, and colocation facilities. Assigning assets and applications to locations gives you geographic visibility, helps with capacity planning, and keeps facility contacts within reach when you need them.
Getting started¶
Navigate to IT Landscape -> Locations to open the location registry. Click Add Location to create a new entry.
Required fields:
- Code: A unique short identifier (e.g., DC-EU-WEST, AWS-US-EAST-1)
- Name: A descriptive display name
- Hosting Type: The kind of facility -- on-premises data center, colocation, cloud region, etc.
Strongly recommended: - Country: Where the location sits geographically - Provider or Operating Company: Who operates the facility
Tip: Use consistent naming conventions. Prefixing cloud locations with the provider name (AWS-, AZURE-, GCP-) makes them easy to spot in lists and reports.
Working with the list¶
The list gives you a searchable overview of every registered location.
Default columns: - Code: Location code (click to open the workspace) - Name: Display name - Hosting Type: On-prem, colocation, public cloud, etc. - Provider / Company: Cloud provider for cloud-type locations, or operating company for on-prem locations - Country: Country name and ISO code - City: City name - Assets: Number of assets assigned to this location - Created: When the record was created
Filtering: - Quick search: Free-text search across all rows - Column filters: Text filters on Code, Name, and City; set filter on Hosting Type
Actions:
- Add Location: Create a new location (requires locations:member)
You can also show, hide, and reorder columns using the column chooser.
The Locations workspace¶
Click any row to open the workspace. It has three tabs: Overview, Contacts & Support, and Relations. The Contacts & Support and Relations tabs become available after the location is saved for the first time.
Overview¶
The Overview tab captures identity and geographic information, split into two sections, plus a sub-locations panel.
Basic information: - Code: Unique identifier (required) - Name: Display name (required) - Hosting Type: Category of facility (required). Hosting types are configurable in IT Landscape -> Settings.
Location details -- the fields shown here depend on the hosting type category:
For on-premises hosting types: - Operating Company: The company that runs the facility. Selecting a company auto-fills Country and City if they are blank.
For cloud hosting types: - Cloud Provider: The cloud provider (e.g., AWS, Azure, GCP) - Region: Cloud region or availability zone
Both categories also show: - Country: Selected from the ISO country list - City: City name - Additional Info: Free-form notes about the location
How it works: Switching between an on-prem and a cloud hosting type clears the fields that belong to the other category. The editor asks for confirmation before making the switch.
Sub-locations¶
Below the main form, the Sub-locations panel lets you break a location into smaller physical areas -- buildings, rooms, racks, cages, or any other subdivision that makes sense for your infrastructure.
Each sub-location has: - Name: A short label (e.g., "Building A - Room 1 - Rack 5") - Description: Optional additional detail
Sub-locations are available after you save the location for the first time. They are saved together with the Overview form when you click Save.
Assets can be assigned to a specific sub-location within a location, which lets you track exactly where hardware sits. When sub-locations exist, the Relations tab shows which sub-location each asset belongs to.
Contacts & Support¶
This tab organises the people and references associated with a location into three sections.
Internal contacts: Team members from your organisation linked to this location. Each row has a User picker and a free-text Role field (e.g., "Ops lead", "Security officer").
External contacts: Third-party contacts pulled from your Contacts master data. Each row has a Contact picker and a Role field (e.g., "Account manager", "NOC contact").
Relevant websites: Useful links such as provider portals, facility documentation, or status pages. Each row has a Description and a URL.
Click Save in the workspace header to persist changes across all three sections at once.
Relations¶
The Relations tab shows entities that are linked to this location. It is read-only -- relationships are managed from the related records themselves.
Assets: A table of assets hosted at this location, showing Name, Environment, Type, Provider, Region/Zone, and Status. When the location has sub-locations, an additional Sub-location column appears showing which sub-location each asset is assigned to. Click an asset name to jump to its workspace.
Applications: A table of applications that have infrastructure at this location, showing Name and Environments. Click an application name to jump to its workspace.
Deleting a location¶
From the workspace header, click Delete to remove a location.
- Requires
locations:memberpermission. - Linked assets are not deleted -- they are automatically unassigned (their location reference is cleared).
- If you have unsaved changes in the workspace, those changes are lost on deletion.
Hosting types¶
Hosting types are configurable in IT Landscape -> Settings. Each type belongs to a category that controls which fields appear in the workspace.
| Type | Category | Example |
|---|---|---|
| Private Data Center | On-prem | Company-owned facility |
| Colocation | On-prem | Rented space in a shared facility |
| Public Cloud | Cloud | AWS, Azure, GCP |
| Private Cloud | Cloud | Company-operated cloud platform |
| Edge | Cloud | Edge computing locations |
Permissions¶
| Action | Minimum level |
|---|---|
| View the list and workspace | locations:reader |
| Create, edit, or delete a location | locations:member |
| Configure hosting types and providers | settings:admin |
Tips¶
- Be consistent with codes: A clear naming convention makes locations easy to identify at a glance and keeps filters useful.
- Use sub-locations for granularity: If a data center has multiple rooms or racks, model them as sub-locations rather than separate locations. This keeps the list clean while still tracking physical placement.
- Track cloud regions individually: Create one location per cloud region you use, not just one per provider.
- Link assets to locations: This enables geographic reporting, DR planning, and quick impact analysis during outages.
- Document contacts early: Having facility contacts on file before an incident saves critical time when it matters most.