Brivo’s cloud platform for managing doors, users, mobile credentials, visitors and remote security operations.
Product and design guidance
Brivo Access centralizes permissions, schedules, events and remote door control. Mobile Pass supports phone-based access, while visitor tools address guest registration and delivery workflows. Decide who owns the Brivo account, subscriptions, identity data, visitor policy and administrator roles before commissioning.
- Cloud account, sites, users and operator roles
- Mobile Pass enrollment, phone replacement and fallback credentials
- Visitor preregistration, host notification and delivery rules
- Offline access, internet resilience and emergency operations
- Code-compliant lock, egress and fire-alarm sequence
- Network, power, battery and outage behavior
- Licenses, subscriptions, integrations and data ownership
- Administrator training, documentation and maintenance
How Boston High Tech helps
We survey the doors, existing panels and readers, credentials, network, identity workflow and integrations before finalizing a bill of materials. We may confirm relevant certification privately, but do not publish certificate copies, license numbers or named certificate-holder information.
Request a product-specific consultation
Serving projects from our Charlotte headquarters and local client offices in Massachusetts, New York and New Jersey. Please arrange office visits in advance.
Official manufacturer references
How to compare and specify this product family
For Brivo Access, Mobile Pass and Visitor Management, the right model and architecture depend on the site, existing infrastructure and operating policy. A proposal should clearly document the following access-control system decisions before equipment is ordered:
- Number and type of controlled openings
- Controller, reader, lock and credential compatibility
- Cloud or on-premise administration and ownership
- Offline behavior, backup power and emergency operation
- Directory, HR, video, visitor and elevator integrations
- Licensing, cybersecurity, training and lifecycle support
Installation, testing and handoff
A site survey records each opening, door hardware, cable path, power, network, credential policy and integration requirement. The design then maps readers, controllers, locks, inputs, outputs and administrator roles to the operational workflow. Commissioning includes door-by-door functional tests, failure-mode and backup-power checks, permission and schedule tests, event verification, administrator training and as-built documentation. Product availability, subscriptions and supported integrations are confirmed for the current project before procurement.
Frequently asked questions
Questions that come up when a property moves door management, mobile credentials and visitor handling onto Brivo’s cloud platform.
An employee got a new phone. Do they lose their access?
Not if a re-enrollment path and a second credential are already defined for that user. Mobile Pass enrollment, phone replacement and fallback credentials are decided before commissioning: who approves a re-enrollment, how quickly it happens, and whether staff at certain doors carry a backup credential so a dead battery does not strand those people outside.
Can a courier be let in without someone at the desk buzzing them?
Brivo’s visitor tools address guest registration and delivery workflows, so a courier can follow a rule you write instead of a person watching a screen. Set visitor preregistration, host notification and delivery rules before go-live: which entrance a delivery may use, which hours the rule covers, who gets notified, and how the event lands in the log.
Do we have to replace the readers we installed five years ago?
The survey answers that per door instead of by blanket policy. We survey the doors, existing panels and readers, credentials, network, identity workflow and integrations before finalizing a bill of materials, and reuse depends on what the installed readers put out, the condition of the wiring in each frame, and whether the current credential population is staying.
What do these doors do when the fire alarm goes off?
Whatever the approved life-safety sequence for the building requires, which outranks any access schedule in the platform. The code-compliant lock, egress and fire-alarm sequence is documented per opening during design, reviewed with the authority having jurisdiction, and then demonstrated door by door at commissioning so the alarm technician and the security administrator see the same result.
Do we own the account, or does the integrator hold it?
You decide that before commissioning, and the proposal states the answer in writing. Ownership of the Brivo account, subscriptions, identity data, visitor policy and administrator roles is assigned by name, because the account holder controls who can be added, what employee data lives in the platform, and what happens to that data if a vendor relationship changes.
Will Brivo talk to the system we use for employee records?
Nothing is promised until the specific system and its version are checked. Identity workflow and integrations are part of the survey, and licenses, subscriptions, integrations and data ownership are recorded together in the proposal. Any connection that cannot be validated for your version stays out of the bill of materials instead of becoming a commissioning surprise.
Official Brivo software, firmware and support
Official manufacturer resources. We link out rather than host firmware.
Before updating: confirm model, hardware revision, current version, entitlement and rollback plan, and schedule monitored or life-safety-adjacent systems with the administrator.