The setting
makes cloud-managed physical security systems for organizations with many sites. Its lets people manage doors, access schedules and user credentials from web and mobile devices.
A confirmed visit does not tell a guest when the door will admit them.
Clear arrival instructions preserve approved access windows, while earlier lobby access accommodates visitors who arrive ahead of time.
Who you’d be doing this for
“Three hosts called me before nine asking why their guests were stuck outside. Their visits were confirmed, just not active yet.”
Defne Abbasi · Office Security Administrator · a character in this brief
Manages visitor schedules and credentials across the four affected offices.
What is at stake
38 of 200 office visitors needed help because they arrived before their credentials became active. You weigh clearer invitations against earlier lobby access, with one release slot and another week of visits approaching.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- clear instructions vs earlier entry
- concise invitations vs explicit timing
- fast delivery vs coverage of schedule edits
- visitor convenience vs approved access windows
Why Verkada
Visitor invitations and credentials determine whether guests enter directly or turn to Intercom and Voice Directory for help.
Written with these in mind
Not your kind of problem? 77 more at Verkada, or browse every organization.
Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.
The organization context comes from public information. The situation and characters are written for the brief.
Job postings it was written from
Public descriptions of the work at Verkada. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Senior Product Manager, Access Management (opens in a new tab)
- Own visitor access, including how guests are invited, credentialed, and expired
- Permissions, identity, provisioning, policy, or configuration-heavy admin tooling is directly relevant, as is any product where one person's settings decide what thousands of other people can do
- Lead Product Manager, Users & Permissions (opens in a new tab)
- Collaborate with stakeholders to design user permission hierarchies and access workflows optimized for large-scale, distributed organizations
- In this role, you will design advanced functionality for managing user access, permissions, and security controls to meet the complex needs of national and global enterprises.
- Senior Product Manager, Intercom Calling (opens in a new tab)
- Identify, prototype and launch new voice AI use cases with the goal of finding product-market fit
- You'll own the underlying calling pipeline, enterprise-grade call routing, the context and controls that help people answering make better decisions, and the AI that automates call responses.
- Lead Product Manager, Connectivity / Gateways (opens in a new tab)
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.
Where similar work appears
Other live briefs connected to this one, and what connects them.
Similar problems at other organizations
Like this one, each of these turns on easing someone in at the cost of understanding.
Terminal request completion fell from 76% to 61% after the acknowledgement appeared.
You have to weigh a durable compliance record against a request step riders can understand quickly.
The same setting, from another role
Each is set around Verkada’s Access Control, written for a different role. They’re separate briefs, not the same scenario.
Vulnerability findings reach engineers without the controller context needed to judge their severity.
You have to decide where the route stops assembling firmware and exposure evidence for a finding and where an engineer takes over to set its severity.
Security and network objections are appearing after customers request deployment plans.
You must decide which evidence earns attention and which judgment stays with the Solutions Lead.
Late events leave security administrators with conflicting accounts of what a door did.
You must decide what AI can assemble and what engineers must verify before acting.