What locations are used for
- Scoping policies — a policy can target “all devices at Gurgaon Office” instead of your whole fleet
- Scoping roles — an IT Operator’s access can be limited to a specific location, so they only see and manage what’s actually theirs
- Filtering and reporting — device, asset, and employee lists can all be filtered by location
- Grouping in bulk import — the Location column in an asset or employee import file matches against your existing location names (see Bulk Import)
Adding a location
Under Organisation → Locations, click Add location.| Field | Required? | Notes |
|---|---|---|
| Name | Yes | e.g. “Mumbai Office” — this is the name used everywhere else in the product, including in bulk import matching |
| Address | No | Street address |
| City | No | |
| State | No | |
| Country | No | |
| Timezone | No | Used for relative timestamps and scheduling shown to people at that location |
Editing or removing a location
Each location has an overflow menu (⋮) with Edit and Delete. Renaming a location updates its name everywhere it’s referenced — you don’t need to re-link devices or employees. If you’re removing a location that still has devices, assets, or employees assigned to it, check with your team first — reassign anything important before deleting to avoid losing that context.Related
- Departments — the other way to group your organisation, independent of physical location
- Employees - track the people you assign devices and assets to
- Bulk Import — location names in an import file must exactly match an existing location here