Skip to content
English
Go to app.elevatedliving.com
  • There are no suggestions because the search field is empty.

ElevateOS & Brivo Integration: Property Manager Guide

Brivo Property Manager Guide

For: Property managers and on-site staff

This guide covers how Brivo mobile credentials and visitor PINs work for residents through ElevateOS, what property managers control, and how to handle common issues. Use it as a reference when onboarding a building to Brivo or troubleshooting a resident's access.

Background

Brivo turns a resident's phone into a building key. Inside the ElevateOS resident app, residents unlock the doors they're entitled to over Bluetooth — no separate Brivo Mobile Pass app needed, no login step, and unlock works offline once the credential is activated. Property managers can also issue time-limited PIN codes to visitors.

Brivo matches residents to existing Brivo person records by email. Keeping resident emails aligned between your PMS and Brivo is the main data-hygiene task.

Unlike most other access integrations in ElevateOS, Brivo provisioning is on-demand — there's no nightly run that pre-creates credentials. Credentials are issued when the resident first opens Brivo in the app, or when a property manager triggers issuance manually.

What residents see

Inside the ElevateOS resident app, residents get:

  • A mobile credential tied to their resident email
  • Bluetooth unlock that works offline once activated
  • A list of accessible doors and access points, with the option to favorite frequently used ones
  • Automatic credential refresh in the background, plus a manual refresh option if the cached pass expires

Residents do not need to install the Brivo Mobile Pass app. Visitors don't need an app either — they get a numeric PIN.

How resident unlock works

The first time a resident opens Brivo in the ElevateOS resident app:

  1. ElevateOS looks them up in Brivo by email.
  2. A new mobile credential is generated and provisioned to their phone.
  3. The credential is cached on the device.

For day-to-day use:

  1. The resident approaches a door.
  2. They tap the lock in the app, or use a favorite shortcut.
  3. The phone broadcasts the credential over Bluetooth and the door opens.

Bluetooth and location permissions must be granted to the ElevateOS resident app. No internet is required at unlock time once the credential is cached.

How visitor PINs work

When a property manager creates or edits a visitor pass with PIN access enabled:

  1. A numeric PIN is generated and bound to the visitor's stay window.
  2. The visitor uses the PIN at the configured access point during the valid window.
  3. The PIN expires automatically after the visitor's end time.

PINs can be revoked early if plans change.

What property managers control

On the resident profile, in the Brivo section, you can:

  • Re-issue a credential — when a resident loses their phone or needs a fresh credential, revoke the old one and issue a new one
  • Confirm activation — check whether a resident's credential has been issued if they report access issues
  • Revoke on move-out — clear the resident's Brivo credential as part of the move-out workflow (ElevateOS does not auto-revoke)

On the visitor record:

  • Issue a visitor PIN — generate a time-bounded PIN and share it with the guest

There is no nightly auto-provisioning run for Brivo. Credentials are issued when residents request them in the app or when a property manager triggers issuance manually.

Resident requirements

For a resident's mobile credential to work:

  • They have Current status in your PMS
  • Their email in ElevateOS matches the email on their Brivo person record
  • They've granted Bluetooth and location permissions to the ElevateOS resident app
  • They've completed the in-app activation once

Best practices

1. Email is the link

Brivo lookups are email-based. The single biggest source of failure is a mismatch between the email in ElevateOS and the email on the Brivo person record. Audit emails when onboarding new residents and after any email changes.

2. Treat move-out revoke as a manual step

There's no auto-revoke on move-out. Add "revoke Brivo credential" to your move-out checklist.

3. Re-issue cleanly

When a resident gets a new phone, use the revoke and re-issue flow rather than leaving stale credentials in place.

4. Practice visitor PIN hygiene

Always set both a start and end time so PINs auto-expire. Don't share PINs over insecure channels — they grant real building access. If a visitor's plans change, revoke the PIN rather than letting it sit unused.

5. Set onboarding expectations

When a new resident moves in, tell them:

  • Their phone is their key — no separate Brivo app needed
  • They need to grant Bluetooth and location permissions to the ElevateOS app
  • The credential works offline once activated
  • Mobile credentials are issued on request, not pre-provisioned the day before move-in

Troubleshooting

  • Resident isn't found in Brivo. The email in ElevateOS doesn't match any person record in Brivo. Confirm the email matches exactly on both sides — no typos, no extra whitespace. Re-sync from your PMS if the email changed recently.
  • "Active credential already exists." The resident already has an active mobile credential. Ask whether they have a working pass on a previous device. If they need a re-issue (lost phone, replaced device), revoke the old credential before issuing a new one.
  • Bluetooth unlock fails at the door. Confirm Bluetooth and location permissions are granted to the ElevateOS app. Confirm the resident is within Bluetooth range of the lock. Toggling Bluetooth or restarting the app usually clears transient issues. If the cached credential has expired, the manual refresh button in the app re-syncs it.
  • Resident can't unlock a specific door. Confirm they're assigned to the right access group or level in Brivo. Confirm the door is wired to accept the group they're in. Confirm the credential was actually activated on their phone.
  • Visitor PIN doesn't work. Confirm the current time is within the visitor's valid window. Confirm the door is configured in Brivo to accept PIN-based entry.

FAQs

Does the mobile credential work offline? Yes. After activation, the credential is cached on the phone and unlocks over Bluetooth without internet.

Does Brivo run a nightly sync like some other integrations? No. Brivo provisioning is on-demand. Residents request their pass and the system fulfills it in real time.

What happens when a resident moves out? ElevateOS does not auto-revoke. Revoke the credential manually as part of your move-out workflow.

What if a resident loses their phone? Use the revoke option to invalidate the old credential, then issue a new one. Their email stays the same.

Can a resident have both a mobile credential and a PIN? Mobile credentials are for residents through the app. PINs are designed for visitors. The two flows are separate.

Does this work with Yardi, Entrata, RealPage, or other PMS systems? Yes. ElevateOS looks up the resident in Brivo by email regardless of where the data originated. Just keep emails in sync.

Does the resident need the Brivo Mobile Pass app? No. Unlock works inside the ElevateOS resident app