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.
An employee's identity travels between offices, but permission to enter does not.
Local approval protects each site's doors, while occasional visits make permanent permissions difficult to justify.
Who you’d be doing this for
“Yesterday a manager called from the lobby, and I had to find someone local to escort her between meetings.”
Clement Henderson · Regional Security Administrator · a character in this brief
Manages access for employees who move between offices and receives requests to arrange entry at unfamiliar sites.
What is at stake
Visiting employees accounted for 46 of 120 sampled Intercom calls seeking help. You must weigh convenient entry across offices against local approval and permissions that end with the visit.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- advance certainty vs arrival flexibility
- employee convenience vs local authority
- reuse of access levels vs precision for one visit
- narrow launch scope vs representative customer learning
Why Verkada
Users, credentials, access levels, and schedules must support occasional visits without making directory sync the source of temporary door permissions.
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 users, groups, credentials, access levels, door associations, and schedules.
- Own visitor access, including how guests are invited, credentialed, and expired
- Lead Product Manager, Users & Permissions (opens in a new tab)
- 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.
- Drive the implementation of advanced identity and access management (IAM) capabilities, including multi-factor authentication(MFA), role-based access control (RBAC), and single-sign on (SSO) integrations
- Senior Product Manager, Intercom Calling (opens in a new tab)
- Build tools that let admins configure, test and manage routing at scale across many sites, users, and devices (including receiver groups, SCIM syncing)
- We see many more interactions it can automate, including wayfinding, appointment management and granting building entry.
- Lead Product Manager, Connectivity / Gateways (opens in a new tab)
- Verkada Gateways enable cameras, intercoms, access control, and sensors to be deployed in locations without stable internet or power.
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 crossing a deadline that can't be undone.
Regulated IT administrators cannot yet govern Computer access by role.
You must decide which controls belong in reusable terms and which require customer-specific approval.
Fifteen pilot customers cannot yet show whether routine access work has left their legacy VPN console.
You must weigh a repeatable value programme against each customer’s different access architecture and proof standard.
Administrators are rebuilding private-application inventories because they cannot choose a safe first migration group.
You have to weigh a guided path to a faster pilot against controls that keep production access reviewable.
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.
Other problems with a similar purpose
In each of these, as in this one, the aim is to remove a real security exposure while keeping the everyday workflow people depend on running smoothly.
Staged testing shows a 0.6% session failure rate on older mobile versions before an irreversible authentication cutover.
You need to close the token exposure without locking members out of liquidity and repayment flows.
One authentication mode has a confirmed flaw and has to be off in every managed workspace within 21 days.
You have to sequence migration and enforcement so exposure closes without breaking data delivery.
Valid workspace members are looping through sign-in despite appearing in the right SSO groups.
You have to restore access while preserving the permission boundary administrators rely on.
