Brivo operating-workflow guide
Cloud administration, mobile credentials and visitor access
Translate Brivo Access features into named owner workflows: identity approval, credential issuance, guest check-in, door response, reporting and lifecycle support.
Design Brivo Access around responsibility
Brivo Access centralizes access-control administration in a hosted environment. Organizations can manage authorized sites, people, credentials, schedules, doors, alarms, reports and supported video or integration workflows. The technology does not decide who should have authority; the implementation must define site ownership, role boundaries, approval, periodic review and emergency access.
Brivo publishes multiple Access editions with different features and included services. Confirm the current edition, subscription term, mobile-credential package, reporting requirements, integrations and retention at proposal time. Record who owns the tenant, primary administrator accounts and recovery contacts.
Identity source
Decide whether people are created manually or synchronized from an approved identity, HR, tenant or property system; name the authoritative record.
Administrator security
Assign least-privilege roles, MFA or SSO where included and appropriate, account-recovery ownership and administrative-log review.
Site and group structure
Design sites, groups and schedules around real operational boundaries so a convenient template does not grant excessive access.
Event response
Define which events create notifications, who receives them, expected response, escalation and after-hours handling.
Audit and retention
Confirm event availability, report needs, export responsibility and the selected edition rather than assuming indefinite retention.
Lifecycle records
At handoff, record tenant ownership, edition, subscriptions, integrations, support path, installed hardware and current release information.
Mobile Pass, wallet credentials and mobile administration
Brivo Mobile Pass lets a supported smartphone act as an access credential at a compatible reader. Brivo also promotes supported Apple Wallet and Google Wallet experiences. Availability depends on the selected Brivo service, reader, mobile device, operating system, region and current manufacturer support.
Brivo Access mobile is an administrator or operator tool for supported management actions, which is a different risk from a user credential. Separate the two roles in policy: credential holders should not automatically receive remote door control or system administration.
| Mobile workflow | What to confirm | Acceptance evidence |
|---|---|---|
| Mobile Pass | Compatible reader, BLE behavior, invitation, activation, phone policy and license/edition. | Successful issue, use, revoke, phone replacement and denied-access tests. |
| Apple / Google wallet | Current platform availability, reader and panel requirements, NFC/BLE behavior and issuance method. | Test supported devices at representative readers, including locked-screen and lost-device response. |
| Access mobile administration | Authorized roles, MFA, remote-unlock rules, event/video visibility and incident logging. | Role-based test accounts, remote-action logs and emergency revocation procedure. |
| No-phone alternative | Physical credential or another approved accessible method. | Documented equivalent workflow for users without a compatible personal device. |
Credential and guest lifecycle
Visitor Management powered by Envoy
Brivo’s current Visitor Management offering is powered by Envoy and is intended to connect guest registration and check-in with access workflows. Published capabilities include kiosk-style check-in, host or delivery handling, badge printing and configurable screening. Brivo guest access may use a PIN or Mobile Pass with pre-registration and time-bounded permissions.
The final workflow should state what data is collected, how long it is retained, who can view it, whether a badge or credential is issued, which doors it opens, when it expires and what happens during an evacuation or network outage. A visitor application does not replace the site’s physical reception and emergency procedures.
Pre-registration
Define the sponsor, required fields, identity checks, privacy notice, arrival window and approval threshold.
Check-in station
Plan tablet or kiosk, network, accessibility, camera or ID workflow if used, printer, consumables and unattended behavior.
Host notification
Choose supported notification paths, escalation for unavailable hosts and after-hours responsibility.
Guest access
Limit doors and schedules, automate expiration and prevent a check-in record from granting broader access than intended.
Deliveries
Separate courier and delivery handling from escorted visitors, including package location and recipient notification.
Emergency accountability
Define whether visitor data supports evacuation accountability and how a current list is obtained during service disruption.
Acceptance and privacy checklist
- Test joiner, mover, leaver, temporary access, lost phone and credential revocation workflows.
- Verify least-privilege administrator roles and visibility across sites.
- Test Mobile Pass and supported wallet credentials on representative approved devices and readers.
- Confirm no-phone and accessibility alternatives.
- Exercise pre-registration, walk-in, denied check-in, host unavailable, badge print, guest expiration and evacuation-list workflows.
- Document data fields, notice or consent, retention, export, deletion and integration ownership with the organization’s privacy team.
- Verify operation during internet, controller, mobile-network, printer and kiosk interruptions.
Official Brivo product and support resources
Use Brivo-owned pages for current specifications, manuals, release notes, firmware status and application access. Availability, subscriptions and supported combinations can change.
Define the Brivo operating model before deployment
We can map users, administrators, mobile credentials, visitor handling and site boundaries into a testable Brivo Access scope for Carolina operations.
Official Brivo 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.