A boutique hotel's camera plan should cover entrances, the lobby and front desk, elevators and corridors, loading dock, cash and storage rooms, and parking — and must exclude guest rooms, spa treatment rooms, restrooms, and staff changing areas entirely. Camera type, storage, retention, and who can view or export footage should all be decided zone by zone, not as one blanket spec. The camera network itself should also run on its own VLAN, separate from guest Wi-Fi, so surveillance traffic never shares a broadcast domain with guest devices.
This is a governance question as much as a hardware question. A property that gets the zone list right but skips staff permissions, retention limits, or network separation still ends up with a system that is hard to defend to a guest, an insurer, or a regulator.
Which zones should actually have cameras?
Entrances, the lobby and front desk, elevator cabs and landings, guest corridors, the loading dock, cash-handling and storage rooms, and parking areas are the standard coverage list for a boutique property. These are the spaces where incidents are most likely to need a verifiable record — deliveries, cash movement, access disputes, and common-area safety.
Camera selection should match what each zone demands. Entrances and parking benefit from long-range night vision and wide fields of view; Ubiquiti's G6 Pro Bullet, for example, is built around a "Multi-TOPS AI Engine, 1/1.2" CMOS, long-range IR night" vision sensor with IR reach up to 60 meters with an add-on Vision Enhancer, which suits an unlit loading dock or driveway better than a compact indoor unit (UniFi Physical Security). Lobby and corridor cameras, by contrast, are usually judged on discretion and image clarity at close range rather than long-distance IR throw, so a dome or turret form factor with vandal resistance tends to fit better in those finished public spaces than a bullet camera designed for exterior reach.
Loading docks and cash or storage rooms are also a natural fit for the AI-based detections UniFi Protect supports — including person, vehicle, and license-plate recognition on compatible camera models — since those zones benefit from alerts tied to specific activity rather than continuous passive recording alone (UniFi Physical Security).
Where should cameras never be installed?
Guest rooms, spa treatment rooms, restrooms, and staff changing rooms should stay off-camera as a matter of policy, regardless of how convenient coverage there might seem. These are spaces where guests and staff have an expectation of privacy that a hotel cannot reasonably override with a notice sign. Decisions about exactly which adjoining areas (such as a spa reception versus a treatment room, or a guest corridor versus a guest room door) count as public versus private should be confirmed with legal counsel and included in the property's written security policy before any camera is mounted.
Where a camera sits close to an excluded zone — a corridor camera near a guest room door, for example — privacy masking should be applied in software so the field of view is blacked out past the boundary, and signage should disclose that recording is in progress in the surrounding public area.
How should retention and footage access be handled?
Retention length and who can view or export footage are decisions a property should make deliberately rather than leave at manufacturer defaults. UniFi Protect's "Enhanced Retention mode intelligently reduces older footage quality to optimize storage, keeping recent recordings in full clarity while preserving months — or even years — of critical video," which gives a property room to keep lower-resolution older footage for longer without needing proportionally larger storage (UniFi Physical Security). A hotel should decide upfront how long full-clarity footage needs to stay available against how long a lower-quality archive should be kept, based on its own incident-review and insurance needs, and confirm that choice with counsel and the property's insurer.
Role-based access also matters. UniFi Protect supports adding "new users and admins with the click of a button" and lets an owner "grant or restrict access to whatever cameras are needed" per user — meaning a front-desk manager, a security lead, and a GM can each be scoped to only the zones and permissions their role requires, rather than giving every staff member blanket access to every camera on property (UniFi Physical Security). Export of clips is also a tracked, deliberate action rather than an open download — footage can be exported from the mobile app or Site Manager, which means a property should decide in policy who is authorized to pull and share a clip, and for what purpose, before an incident makes that decision under pressure.
How does the camera network stay separate from guest Wi-Fi?
The camera system should sit on its own VLAN, isolated from the guest, staff, and PMS networks, so camera traffic never competes with guest devices for bandwidth and a compromised guest device can't reach camera feeds or the NVR. This is standard practice for any serious hospitality network design, and it fits the same segmentation logic that separates guest, staff, IoT, and PMS/POS traffic described in Cave Group's broader hospitality technology work. A property's IT or integrator should confirm during design which VLAN the NVR and each camera live on, and that remote access to footage goes through an encrypted connection rather than a port opened directly on the guest network.
Storage sizing should follow the same zone-by-zone logic as camera selection: a UniFi Protect console or NVR should be sized to the number of 4K versus HD streams the property actually runs and the retention window chosen for each zone, rather than picked as a flat per-camera number. Ubiquiti's NVR line spans consoles rated from roughly 15 HD or 6 4K cameras up to enterprise units supporting several hundred cameras, so capacity should be matched to the camera count and resolution mix the zone plan produces, not guessed at in advance (Ubiquiti Store).
For properties weighing packaged guest-room automation and access alongside this camera plan, Cave Group's hospitality service page covers how surveillance, access control, and PMS integration are typically scoped together for boutique and luxury properties.
Frequently asked questions
Can cameras be placed in a spa or guest-room corridor?
A corridor outside guest rooms is a public space and is a standard coverage zone, but the camera's field of view should be masked so it does not capture the interior of any guest room when a door opens; the guest room and spa treatment room interiors themselves should stay off-camera entirely.
How long should hotel camera footage be retained?
Retention should be set deliberately rather than left at a default — UniFi Protect's Enhanced Retention mode can preserve lower-quality archives for months or years while keeping recent footage in full clarity, so a property should decide its full-clarity and archive windows based on its own incident-review and insurance needs, confirmed with counsel.
Who should be allowed to export hotel surveillance footage?
Export should be limited to specific authorized roles rather than open to every staff member with camera access; UniFi Protect allows an owner to grant or restrict access per user and per camera, so a property's policy should define which roles can view feeds and which can additionally export and share clips.
Does the camera network need to be separate from guest Wi-Fi?
Yes — placing cameras and the NVR on a dedicated VLAN isolated from guest, staff, and PMS traffic keeps surveillance bandwidth and access separate from guest devices, which is a standard part of hospitality network segmentation design.
What camera type fits a loading dock versus a lobby?
A loading dock or parking area typically benefits from a long-range, IR-capable camera built for low light and distance, while a lobby or corridor camera is usually chosen for discretion and close-range clarity in a finished space; matching the camera to the zone's actual demands works better than specifying one model property-wide.