Managed badging
Your team requests a badge. We print it and ship it, with approvals tracked in the Managed customer portal.
BadgeFlow →Managed
Connect access and everyday workflows with Managed. We set up the connections around your systems and keep them supported, so your team has less to manage.
The setup is part of the service. Your systems, access rules and sites shape the integration. Managed handles the configuration, tests the workflow with you and provides ongoing support. We agree on the scope before work starts, including any customer-specific connections.
Verkada integration partner
Managed is a managed-services team for Verkada. After installation, we take on the day-to-day work of running Verkada, so your own team doesn't have to.
Your team requests a badge. We print it and ship it, with approvals tracked in the Managed customer portal.
BadgeFlow →The routine administration that builds up after go-live, handled by a team you can call, with tickets you can see in your portal.
Helpdesk →A branded guest sign-in for Meraki sites, set up and run by our team.
Captive Portal →We monitor the network gear your cameras and doors depend on, and work issues with you.
NetOps →We run camera health checks across your cameras and follow up on what we find.
LensOps →Built around your day-to-day work
Three workflows we run today, with more detail on each below.
Give people access for the time they've booked. At The Node, the booking and door access work together, with access removed when the booking ends or is canceled.
See the booking workflow →Keep getting in part of the same experience as booking a space. The Node Android app server-relays an unlock request through Managed.
The Node app is on Android, iPhone and the web.
See The Node app →Our NOC brings Verkada devices and network information into one place to help the team investigate problems across a site.
Talk about your sites →The map
Managed sits in the middle and moves the data both ways.
Use cases
Customer configuration and validation are agreed in scope.
For: Coworking, flex office, meeting suites, campuses that rent space.
A confirmed booking creates a Verkada Access user with start and end dates set to the booking window and adds them to the right door group. Cancel or expiry removes the access, and a scheduled reconciler keeps Verkada in step with the booking source.
Systems: Booking app, payments, Verkada Access
Running today at The Node, our coworking space in West Chester.
No front desk handing out keys; access lasts exactly as long as the booking.
For: Operators who want their brand on the phone, not a separate app.
Members tap Unlock in the Android app or phone browser. The server checks booking and building hours, then relays the unlock through Verkada. It works on Android, iPhone and the web. No Bluetooth or mobile SDK is used.
Systems: Customer app, Verkada Access
Running today in The Node app on Android, iPhone and the web.
One app for booking, paying and getting in.
For: Coworking, visitor-heavy offices, training centres.
Managed uses a booked user's first credential entry event to update check-in signs and dashboards. This records credential activity, not independent proof of the person's physical presence.
Systems: Verkada Access events, booking app, displays
Customer deployment is scoped per site.
Access-event-based check-in reporting.
For: Hospitals, universities, large offices with constant onboarding.
Staff tap an old badge or enter their details at a kiosk. Managed matches them to their Verkada user, prints the new badge and activates the card in Verkada. Managed can also print and ship badges.
Systems: Verkada Access, badge printer, kiosk
Customer deployment is scoped per site.
Badges in minutes, without a line at the security office.
For: Any site printing badges or running kiosks.
Verkada users and credentials are mirrored into Managed's badging workflows. Removing someone takes effect shortly after the change is made.
Systems: Verkada Access
Customer deployment is scoped per org.
A synchronized directory for badging workflows.
For: Multi-site employers, healthcare systems, school districts.
AccessOps connects HR to door access. HR connectors and role-to-door mappings must be built and validated for the agreed systems before live access changes.
Systems: HR/identity connectors; Verkada Access
We confirm which HRIS connector fits your system before go-live, and we cannot promise access changes the same day.
Access follows the person; leaver timing depends on the deployed connector.
For: Organisations that run requests through a service desk.
ConnectWise ticket-driven badge issuance runs at Managed. Customer deployments require approved access rules. Deactivation requires human review before revocation; ambiguous matches stop for resolution. ServiceNow is scoped per project.
Systems: ConnectWise, Verkada Access. ServiceNow: scoped build.
Customer deployment is scoped per site.
Reviewed requests with traceable access changes.
For: IT teams and managed service providers running many sites.
Managed pulls cameras, access devices and sites from multiple Verkada orgs into one NOC console, maps each camera to its network switch port and raises problems when a device drops.
Systems: Verkada Command (multi-org), Meraki, ticketing
Delivered through the Managed NOC.
Investigate whether a camera issue starts with the device or its network.
For: Retail, restaurants, hospitality.
Managed's till sends sales, voids and drawer events to Verkada Helix for video search, with offline queueing and replay. Camera routing is tailored per site. Refund events are not included.
Systems: POS, Verkada Helix
Customer setup and camera routing are scoped and validated.
Find the matching sale or drawer event on video.
For: Retail, grocery, fuel, quick-service, warehouses, banks, anywhere old equipment can't call an API.
A connection for legacy serial or network transaction outputs. Managed scopes the protocol, hardware, camera mapping, secure transport, offline handling and support before a customer-specific build.
Systems: Legacy POS and serial devices, connector box, Verkada Helix
Scoped per project after agreeing the source, hardware, development and support.
Design goal: Search video alongside records from older equipment.
For: Any business that wants video tied to its records.
Cloud APIs, ERP, SQL, files and webhooks are possible source patterns, not ready-made connectors. Managed reviews each source and agrees development, camera mapping and testing. No Square, Toast, Shopify, Clover or NCR connector is available today.
Systems: Cloud APIs, databases, files, connector box, Verkada Helix
Each source requires a scoped build.
Design goal: Search video by the transaction types agreed for your source.
For: Security operations, facilities, IT.
Implemented routing can post to Microsoft Teams and open ConnectWise tickets. We validate a signed Verkada event through to its destination for your site. Slack, email and other destinations require a scoped build.
Systems: Verkada webhooks, Teams, ConnectWise
Scoped per-customer configuration and signed-webhook validation; switched on per customer.
The right person hears about it, not a shared inbox.
For: Campuses moving from on-prem access control to Verkada a building at a time.
An on-prem connector keeps users and credentials in step between the legacy system and Verkada until the last building cuts over.
Systems: On-prem panels (for example Lenel, Software House, Genetec), Verkada Access
A pattern we deliver to order on the same platform.
One person record during a multi-year migration.
For: Lobbies, operations centres, events.
Approved Verkada camera views play on display screens alongside schedules and messages.
Systems: Verkada Command, displays
Customer deployment is scoped per site.
For: Facilities and operations leaders.
Occupancy, access and device-health data flows to a data warehouse or BI tool on a schedule.
Systems: Verkada APIs, SQL, warehouse or BI
A pattern we deliver to order on the same platform.
For: Offices and clinics with scheduled visitors.
A meeting invite or appointment pre-registers the guest in Verkada Guest and sends the visitor their arrival details.
Systems: Outlook, Google Calendar, scheduling systems, Verkada Guest
A pattern we deliver to order on the same platform.
Helix
The Managed till demonstration sends sales, voids and drawer events to Helix today. Connections for other cloud systems or legacy equipment are scoped per project after agreeing the source, camera mapping and delivery.
Point of sale → HelixOn-site connector boxOther sources, scoped per project
By industry
The use cases that come up most for each.
How it works
For IT and security reviewers.
Events the other way: Verkada webhook → Managed → Teams or a ConnectWise ticket.
Prepaid with your project
Prepay 12, 24 or 36 months on the same invoice as the project.
| Term | At list | Discount | Prepaid |
|---|---|---|---|
| 12 months | $19,380 | 10% | $17,442 |
| 24 months | $38,760 | 15% | $32,946 |
| 36 months | $58,140 | 20% | $46,512 |
An example, not a quote. Prices in USD, exclude applicable taxes. See the pricing page for each service.
We run it ourselves
We run our own shared workspace on it. A confirmed booking opens the right doors for exactly the booked time, and members unlock from an app on their phone. That runs on Managed and Verkada Access today.
Start with one system
Tell us which systems you use and what you want to happen between them. We'll walk through the workflow and the setup it needs.
Tell us about your integration