Envoy Rules
Answers needed to lead to action.
Envoy let companies customize questions for visitors and employees, but admins needed to act on the answers. A health-screening response might mean denying entry or notifying someone before a person reached the office.
Customer calls and feedback from customer-facing teams made control a clear priority. The challenge was addressing that immediate need while creating a logic framework that could support other workplace policies later.
One flow across two products.
I partnered with the PM to define the first release, including rules with multiple conditions. I explored inline controls, a dedicated tab, and a side panel across the existing employee and visitor flows.
The side panel let admins see questions and rules together and offered a reusable entry point across products. I tested and refined that direction with customers.

Ship quickly. Learn where it breaks.
A side panel required a new component. To ship and learn sooner, I worked with engineering to retain the flow’s structure inside an existing modal. The first release supported entry denial and notifications, plus editing and deleting rules.
Legal requirements surfaced two important needs: longer screening questions made rules harder to scan, and privacy called for “OR” logic that could deny entry without revealing which sensitive answer had triggered it. These became priorities for iteration.

Adopted and put to use.
of active Protect companies had created at least one rule.
of Protect rules were created to deny entry.
of entry-denial rules had triggered at least five times.