Locations
Record your offices, data centers and other sites once, with an address and map coordinates, and link assets and vendors to them.
A location is a place where your organization works or keeps data, such as the head office or a data center. You save it with an address and coordinates. Assets and vendors point to a location, so you can see what is at each site. Policies and records can mention it with :, and the policy PDF prints the address.
To import, archive or delete locations, see Collections. Scripts and integrations: see API below.
Add a location
- Open Collections, then Locations, and choose Add location.
- Enter the Name, for example
Zurich head office, and a Description if you want. - Choose Select location. A dialog opens.
- Type the address in the search field and choose the right result. The map shows the place and the coordinates are filled in.
- If the pin is not exactly right, open Fine-tune Coordinates and change Latitude or Longitude.
- Choose Save Location, then Create.

See what is at a location
- Open the location.
- On the Detail tab, Related Data lists the assets and vendors that use it.
To link an asset or a vendor, open it, choose Edit and choose the location.
Reference
| Field | Required | Notes |
|---|---|---|
| Name | yes | 2 to 255 characters. |
| Description | no | |
| Location | yes in the app | The address, chosen in the search. The policy PDF prints it in place of a mention. |
| Latitude, Longitude | no | Filled in by the search. Change them under Fine-tune Coordinates. |
| Slug | yes | Made from the name. See Collections. |
- The address search and the map use Google Maps.
- A CSV import does not search for the address. Fill in
latitudeandlongitudeyourself if you need them. - In an asset or vendor CSV import, the
locationIdcolumn can hold the location's name instead of its id. - When you delete a location, the assets and vendors that used it keep no location.
CSV columns
The template from Download CSV template has these columns. Leave slug empty to make it from the name.
slug,name,description,latitude,longitude,address
zurich-head-office,Zurich head office,,47.3673,8.5399,"Bahnhofstrasse 1, 8001 Zürich"API
The calls are the same for all collections; see the Collections API. The path is /locations/.
| Field | Type | Required |
|---|---|---|
organizationId | string | on create |
name | string, 2 to 255 characters | yes |
slug | string, lowercase with hyphens | yes |
description, address | string | no |
latitude, longitude | number | no |
{
"organizationId": "<organization id>",
"name": "Zurich head office",
"slug": "zurich-head-office",
"address": "Bahnhofstrasse 1, 8001 Zürich, Switzerland",
"latitude": 47.3673,
"longitude": 8.5399
}How is this guide?
Labels
Tag risks, assets, vendors, evidence, incidents and processes with your own colored labels, so you can group and filter them the same way everywhere.
Schedules
Define your recurring cycles once, such as "every quarter", and use them for policy reviews, evidence reviews, trainings, vendor assessments and automated checks.