Envoy
Envoy turned the roster it already had into a physical-security product, and is now hardening it.
◆Recent moves
- 5d ago
Audit logs for move management
The Event Log now records published changes to the workplace map — desk and reservation edits, move-queue tasks, and desk lending updates. It is the accountability layer for features already shipped, and the second consecutive release aimed at making shared workplace state safe for multiple teams to edit.
View source ↗ - 6d ago
Location-based blocklists
Blocklist records can now be scoped to chosen locations instead of applying company-wide, letting a site team block someone locally while the global list stays protected. A delegation fix rather than a new capability, and one that matters more as Envoy adds security surfaces across multi-site customers.
View source ↗ - 11d ago
Executive/VIP protection
VIP protection narrows threat monitoring from regions to named individuals, with a radius drawn around each person's home or office and its own alert routing. It is the highest-value slice of the Response launch it shipped alongside, built on the same dashboard rather than extending it.
View source ↗ - 11d ago
Remote worker safety
Employee home addresses synced from HRIS appear as a layer on the Threat Dashboard and count toward each threat's impacted totals, pulling offsite staff into emergency notifications and safety confirmations. This is what makes the July HRIS directory sync pay off, and it stretches the duty-of-care workflow past the office footprint.
View source ↗ - 11d ago
Threat intelligence
⚡ SPARKThreat Intelligence is the release that made Envoy a security vendor rather than a workplace one, and the two features shipped beside it are refinements of the dashboard it introduced. Everything since — scoped blocklists, map audit logs — reads as preparing the platform for customers who will now use it in that register.
View source ↗ - 22d ago
Manage Deliveries with new endpoints in the Developer API
Deliveries gain full Developer API coverage, so mailroom records can be created, retrieved, and synced with external systems instead of exported by hand. Routine API completion work, and part of the pattern of making each Envoy module addressable programmatically.
View source ↗