Multi-Location Support
The One Visitor is built for organizations that manage visitor check-in at more than one site. All locations share a single Visitor account, with independent settings, badge inventory, and kiosk displays per site. The dashboard aggregates across all locations.
What Is a Location?
A location represents a single physical site — an office, warehouse, datacenter, branch, or client site. Every visitor record is associated with exactly one location.
Location Types
| Type | Example Use Case |
|---|---|
| Office | Corporate headquarters, regional offices, MSP office |
| Warehouse | Distribution center, storage facility |
| Datacenter | Colocation or owned datacenter |
| Branch | Satellite office or smaller branch location |
| Client Site | A managed client's office where you deploy Visitor as part of a managed service |
| Other | Any site that doesn't fit the above categories |
Creating Locations
- Click Locations in the left navigation
- Click Add Location
- Fill in name, address, type, capacity, and timezone
- Configure location-level settings (see below)
- Click Save
There is no limit on the number of locations per tenant. Billing is based on active locations — locations that have had at least one check-in in the current billing month.
Per-Location Settings
Each location can be configured independently:
| Setting | Description |
|---|---|
| Require NDA | Require NDA acknowledgment before check-in completes |
| Require Photo | Require visitor photo capture (planned feature) |
| Auto-Checkout Hours | Number of hours before automatic check-out (default: 12) |
| Kiosk Enabled | Whether self-service kiosk check-in is allowed at this location |
These settings override tenant-level defaults. For example, you might require NDA at a client datacenter but not at your MSP office.
Location-Specific Badge Inventory
Badge inventory is managed per location. When you assign a badge to a visitor, you select from the badges registered at that visitor's location. Badges cannot be assigned across locations.
This ensures badge numbers are meaningful within a site (e.g., Location A has V-001 through V-050, Location B has its own V-001 through V-030).
Location-Specific Kiosk Displays
Each kiosk display is registered to one location. When a visitor checks in at a kiosk, their visitor record is automatically associated with that kiosk's location. There is no manual location selection on the kiosk — it is determined by which display they are using.
Dashboard — Aggregated View
The dashboard shows metrics across all locations:
- Visitors Today — total across all locations
- Checked In Now — total currently in the building across all locations
- Active Locations — count of locations with check-ins today
- Displays Online — count of kiosk displays that have connected recently
The Recent Check-Ins feed on the dashboard shows the 10 most recent check-ins across all locations, with the location name displayed in each row.
Filtering by Location
On the Visitors page and the Badges page, use the Location filter to narrow results to a single site. This is useful when:
- A specific location needs a security review
- A badge inventory reconciliation is needed at one site
- A reception manager wants to focus on their site
MSP Multi-Client Deployments
For MSPs deploying Visitor across multiple managed clients:
- Create one location per client site
- Use the location name to identify the client (e.g., "Client: Acme Corp HQ")
- Each client's visitors appear in the shared log, filterable by location
- Each client site can have its own kiosk with its own badge inventory
Timezone Handling
Each location has a timezone setting. Auto-checkout calculations use the location's timezone. For example, if a location is set to Pacific Time and auto-checkout is configured for 10 hours, the system calculates 10 hours from the local check-in time before auto-checking out the visitor.
Visitor log timestamps are stored in UTC and displayed in the browser's local time.
Location Capacity
You can set a capacity on each location to track the maximum occupancy. Capacity is informational — Visitor records the value but does not currently block check-ins when capacity is reached. An alert when approaching capacity is planned for a future release.