Authorized dealer · Certified installers · Charlotte, NC headquarters
360 Technology Group is an authorized Verkada dealer and certified installer
We have been selling, installing, programming and servicing Verkada systems across North and South Carolina since 2018 — more than 8 years. Our scope covers Verkada cameras, access-control controllers and readers, intercoms, alarms, environmental sensors and Verkada Command administration.
- Authorized Verkada dealer — we quote and supply genuine Verkada equipment, licensing and subscriptions.
- Certified Verkada installers — our technicians install, wire, program, commission and document the system.
- Repair and takeover — we service, troubleshoot, expand and take over existing Verkada installations we did not originally install.
- 24/7 emergency service — on-call service technicians for emergency repairs, plus scheduled preventive maintenance.
We cover every city in North Carolina and South Carolina from our Charlotte headquarters. Request a quote or service call Call 704-726-4254
Identity and integration planning
Verkada with Okta, Entra ID, SSO, SCIM and APIs
Define the identity lifecycle, administrative boundary, role model, token ownership and acceptance tests before connecting Verkada Command to enterprise systems.
Choose the correct identity function
OIDC or SAML SSO
SSO controls how authorized users authenticate to Command. Verkada currently documents OIDC and SAML options and recommends OIDC when available. Establish emergency access and recovery before enforcing SSO.
SCIM provisioning
SCIM can create, update and deactivate users and synchronize groups from supported identity providers. Map source groups to intended Command roles; synchronization alone does not design least privilege.
Command API
Verkada documents a REST-based API for programmatic interaction with Command and devices. Define the business use case, data owner, endpoint scope, rate behavior, error handling and audit trail before generating credentials.
Okta and Microsoft Entra ID planning checklist
- Inventory administrators, operators, viewers, installers and service accounts, including site-level boundaries.
- Choose OIDC or SAML based on the supported tenant, security policy and recovery requirements.
- Define SCIM source groups, attribute ownership, joiner/mover/leaver behavior and what happens when synchronization fails.
- Keep a tested break-glass path outside the normal federation failure domain.
- Run a pilot with non-critical accounts before requiring SSO for the organization.
- Test user creation, role change, group removal, termination, token rotation, administrator recovery and audit visibility.
Use Verkada’s current Okta guide or Microsoft Entra ID guide. Interfaces and prerequisites change, so verify the live documentation during implementation.
API integration acceptance
| Control | Planning question | Evidence |
|---|---|---|
| Authorization | What minimum scope and organization access does the integration require? | Approved role and endpoint matrix |
| Secrets | Where are credentials stored, rotated and revoked? | Vault record and tested rotation procedure |
| Data | Which events, video references, access records or device data leave Command? | Data-flow and retention approval |
| Reliability | How are timeouts, throttling, retries and duplicate actions handled? | Failure-mode test results |
| Audit | Can an administrator distinguish human and integration actions? | Searchable event and change evidence |
| Offboarding | How is the integration disabled without disrupting unrelated systems? | Revocation and rollback test |
Installer, identity-team and client responsibilities
The access-control installer validates controllers, readers, doors, credentials and site behavior. The identity team owns authoritative directories, authentication policy and provisioning rules. The client security owner approves roles, data use and emergency access. Integration work succeeds when those responsibilities are explicit and jointly tested.
Review the official Verkada Command API guide.
Plan integration and field acceptance together
360 Technology Group can coordinate Verkada configuration and field testing with the client’s authorized identity, security and software teams.
Official Verkada software, firmware and support
Use these manufacturer-owned portals for current downloads, release notes, manuals, advisories and technical resources. 360 Technology Group links to official sources and does not copy or host firmware files.
Update carefully: confirm the exact model, region, hardware revision, installed version, prerequisites, required intermediate releases, support entitlement, integrations, backup, maintenance window, rollback limitations and post-update tests. The wrong package or sequence can interrupt service or prevent a downgrade.
Some portals require a customer, dealer, certified-technician or active-support login. Cloud-managed products may update automatically and may not offer a public firmware file.