Managed

Bring Verkada into the way you work.

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

After the install, we keep Verkada running.

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.

Managed badging

Your team requests a badge. We print it and ship it, with approvals tracked in the Managed customer portal.

BadgeFlow →

Command admin support

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 →

Guest Wi-Fi sign-in

A branded guest sign-in for Meraki sites, set up and run by our team.

Captive Portal →

Network monitoring

We monitor the network gear your cameras and doors depend on, and work issues with you.

NetOps →

Camera health checks

We run camera health checks across your cameras and follow up on what we find.

LensOps →

How we work in your Verkada org

  • We work in your own Verkada organization, through API access you grant and limit to the agreed workflow.
  • Badge and access changes follow your approved process, and a person reviews every deactivation.
  • Each workflow, and each connection to another system, is scoped and tested with you before it goes live.

Built around your day-to-day work

Built around your day-to-day work

Three workflows we run today, with more detail on each below.

Booking to door access

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 →

Unlock in your own app

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 →

Verkada and the network, together

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

Your systems on one side. Verkada on the other.

Managed sits in the middle and moves the data both ways.

Diagram. Your systems on the left send data in to Managed. Managed sends events out to Verkada products on the right, and brings Verkada data back the other way.

Your systems

  • People and identityHR and identity systems: AccessOps connectors
  • Work and serviceConnectWise and Teams; other service tools and destinations scoped per project
  • Spaces and bookingsBooking access works at The Node; other booking and calendar connections scoped
  • Business systemsPOS to Helix; other business sources scoped per project
  • Network and buildingWorking network/NOC visibility; legacy panels and building systems scoped
  • DataSQL, BI and file feeds: customer-specific connections scoped per project
ManagedManagedMaps, rules, queue, audit log

Verkada

  • Access Control
  • Cameras
  • Alarms
  • Guest
  • Helix
  • Sensors
  • Command
Where it runsIn the cloud, hosted by ManagedCustomer cloud, scoped per projectOn-prem connections scoped per project; approved data may flow to cloud services

Use cases

What people connect first.

Customer configuration and validation are agreed in scope.

Booking → door access, automatically

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.

Unlock from your own app

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.

Check-in from door events

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.

Badge printing and self-service kiosk

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.

Directory sync for badging

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.

HR joiner, mover, leaver → Verkada

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.

Service tickets → access changes

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.

One view of Verkada and the network

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.

Point of sale → Helix

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.

Legacy registers and serial devices → Helix (on-site connector box)

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.

Other transaction sources → Helix

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.

Verkada events out to the tools your team uses

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.

Legacy access panels during migration

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.

Camera feeds on lobby and event displays

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.

Verkada data into your reporting

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.

Visitors from the calendar

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

Search video by transaction. Scope the connection around your source.

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.

  1. Legacy register or serial device
  2. Proposed Managed connectorHardware and offline handling to be scoped and tested.
  3. Verkada Helix
  1. Cloud POS, ERP, SQL, CSV or SFTP
  2. ManagedSource ingestion and camera mapping scoped per project.
  3. Verkada Helix

By industry

Start from your kind of site.

The use cases that come up most for each.

How it works

Checked, logged and supported by the people who install your cameras.

For IT and security reviewers.

  1. Source system
  2. Managed: map, rules, queue
  3. Verkada API
  4. Read-back where implemented
  5. Action records validated per workflow

Events the other way: Verkada webhook → Managed → Teams or a ConnectWise ticket.

Connection
Your admin grants API access scoped to the agreed workflow. We confirm region support, permissions and key handling for your environment.
Writes are checked
Booking access uses read-back and continuous reconciliation; credentials expire with the booking and cancellation revokes the booked access. Agree source authority, cancellation rules and failure handling before rollout. Other workflows are validated for the checks they need.
Events
The event receiver verifies signatures. A successful signed Verkada event and its destination must be validated for your deployment; polling is used where appropriate.
Audit
We agree which actions and triggers must be logged, then validate that record with your team.
Where it runs
Managed-hosted by default; customer cloud is scoped. On-prem connections may send approved data to cloud services.
On-site connector box
A legacy connector box is not a ready-made product. Protocols, camera mapping, secure transport, offline handling and support are agreed in the build scope.
Who supports it
The Managed service desk and NOC, with installation delivered by the installing integrator.

Prepaid with your project

Buy the service term with the build.

Prepay 12, 24 or 36 months on the same invoice as the project.

  • 12 months10% offmonthly service fees
  • 24 months15% offmonthly service fees
  • 36 months20% offmonthly service fees
  • The term starts at go-live, and no later than 12 months after the invoice.
  • The discount applies to monthly service fees only. It does not apply to setup, per-badge fees or hardware.
Example: one site with $1,615 a month of Managed services at list.
TermAt listDiscountPrepaid
12 months$19,38010%$17,442
24 months$38,76015%$32,946
36 months$58,14020%$46,512

An example, not a quote. Prices in USD, exclude applicable taxes. See the pricing page for each service.

We run it ourselves

Managed is its own first customer.

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

Start with what you want to do

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