---
title: Locations
summary: 'A location is a named physical site that users and SIP devices are assigned to, so the system can target "everyone at the Zurich office".'
section: features
tags:
  - crud
  - telephony
  - attributes
updated: '2026-08-12'
---

> A **location** is a named physical site (an office, a building, a floor) that users and SIP devices are assigned to, so routing can target *"everyone at the Zurich office"*. Each user and device has one location at a time.

## Overview

A location is the place-based dimension of your tenant. Where [Tags](tags.md) say *"what kind of person"* and [Groups](groups.md) say *"what team"*, locations say *"where physically"*. Each user and device has one location at a time, and reassigning moves them - there is no multi-location membership.

## What it does

A location does not affect callers directly. It affects *which users and devices ring* when a routing entity filters by location. Locations become routing-relevant when consumed by:

- [Pools](pools.md) - both Include and Filter phases accept locations.
- [Multicasts](multicasts.md) - target devices at a specific site, for example a *Building A* overhead page that *Building B* never hears.
- [Call flow steps](call_flow_steps.md) - the *Dial* step type can target users by location.

The **Enable location as presence status** toggle is opt-in per location. When on, users can select the location in the Voxbi app to show colleagues where they are working from. Use it for places people actually occupy (office, home office, customer site) and leave it off for organizational-only locations like a warehouse or server room.

## See also

- [Users](users.md) - the primary location-bearer.
- [SIP devices](sip_devices.md) - the secondary location-bearer.
- [Pools](pools.md) - the main consumer.
- [Multicasts](multicasts.md) - paging by location.
- [Tags](tags.md) - the attribute-based counterpart.
- [Languages](languages.md) - the language-based counterpart.

```yaml fields
name:
  label: Name
  tab: General
  hint: 'A short name for this location, e.g. "Zurich office".'
enable_location_as_presence_status:
  label: 'Enable location as presence status'
  tab: General
  hint: 'Lets users show colleagues they are working from this location.'
is_home_office:
  label: 'Remote office'
  tab: General
  hint: 'Marks the user as working from home on their Microsoft 365 calendar (needs the Graph Calendar integration).'
description:
  label: Comment
  tab: General
  hint: 'Optional note, editable from the list.'
users:
  label: Users
  tab: General
  hint: 'Users based at this location. Also drives location-based call routing.'
is_fixed_location:
  label: 'Fixed geolocation'
  tab: 'Address & map'
  hint: 'On for a site with a fixed address; off for dynamic ones like home office or field work.'
street_no:
  label: 'Street number'
  tab: 'Address & map'
  hint: 'Street number of the site.'
street:
  label: Street
  tab: 'Address & map'
  hint: 'Street name of the site.'
postal:
  label: 'Postal code'
  tab: 'Address & map'
  hint: 'Postal or ZIP code.'
city:
  label: City
  tab: 'Address & map'
  hint: 'City or town.'
country_id:
  label: Country
  tab: 'Address & map'
  hint: 'Country of the site.'
latitude:
  label: Latitude
  tab: 'Address & map'
  hint: 'Latitude in decimal degrees, e.g. 49.6116. Set with longitude to place the map pin.'
longitude:
  label: Longitude
  tab: 'Address & map'
  hint: 'Longitude in decimal degrees, e.g. 6.1319. Set with latitude.'
geofence_radius_m:
  label: 'Geofence radius (m)'
  tab: 'Address & map'
  hint: 'How far from the coordinates still counts as being here. Leave empty to skip geofencing.'
icon_class:
  label: Icon
  tab: General
  hint: 'Icon shown on the location badge.'
bg_color:
  label: 'Icon color'
  tab: General
  hint: 'Badge background color.'
font_color:
  label: 'Text color'
  tab: General
  hint: 'Badge text color.'
sipDevices:
  label: 'Phones / SIP devices'
  tab: General
  hint: 'Phones based at this location. Also drives location-based targeting.'
```