ElevateOS & Brivo Integration: Setup & Connection Guide

For: Property managers connecting a new building to the Brivo Access integration

This guide walks through everything needed to connect a building to Brivo Access in ElevateOS. Once connected, residents unlock doors with a Bluetooth mobile credential from inside the resident app, and visitors can be issued time-limited PIN codes.

For day-to-day operation of the integration once connected, see the Brivo X ElevateOS Property Manager Guide.

Before you start

Have these in place:

• An active Brivo Access account with Super Administrator access
• A PMS connection between Brivo and your property management system (Entrata, Yardi, RealPage, etc.) so that resident emails stay in sync
• The email address provided by your ElevateOS Customer Success representative (typically dev@elevatedliving.com)

By the end, you'll send ElevateOS two pairs of credentials:

• A Client ID and Client Secret for a Password-type API token
• A Client ID and Client Secret for an Invitation-type API token

Step 1 — Establish the PMS connection

ElevateOS matches residents to Brivo by email. Before connecting Brivo to ElevateOS, make sure Brivo is connected to your PMS so resident emails are populated and stay in sync.

If a resident's email doesn't match between Brivo and ElevateOS, they won't be found in Brivo when they try to use the resident app — fix the mismatch on whichever side is wrong.

Step 2 — Disable Brivo's automated mobile credential emails

In Brivo Access, request that Mobile Credential invitation emails be disabled. Going forward, ElevateOS generates and delivers credentials to residents through the resident app — you don't want Brivo also sending invitation emails for the same residents.

If you can't disable them yourself, open a ticket with Brivo support or your Brivo administrator.

Step 3 — Add ElevateOS as a Brivo administrator

In Brivo Access:

1. Go to Settings → Administrators.
2. Click Create Administrator.
3. Fill in the details:
   • First Name: ElevateOS
   • Email: the email address provided by your ElevateOS Customer Success representative (typically dev@elevatedliving.com)
   • Phone Number: any value works — ElevateOS doesn't use it
   • Time Zone: Central Time (ElevateOS servers are in Central Time)
4. Under Roles, assign the Administrator role.
5. Under Sites, choose:
   • All Sites if ElevateOS should manage every site, or
   • The specific site(s) you want to scope ElevateOS to
6. Click Save Changes.

Step 4 — Create the Password API token

Still in Brivo Access:

1. Go to Marketplace.
2. Click Generate New API Token.
3. Fill in the details:
   • Application Name: ElevateOS
   • Application Description: ElevateOS Integration
   • Application Type: Password
4. Click Save to generate the token.
5. Open the new Password integration you just created.
6. Copy the Client ID and Client Secret — you'll send both to ElevateOS.

Step 5 — Create the Invitation API token

Repeat the process for an Invitation-type token:

1. In Marketplace, click Generate New API Token.
2. Fill in the details:
   • Application Name: ElevateOS
   • Application Description: ElevateOS Integration
   • Application Type: Invitation
3. Click Save.
4. Open the new Invitation integration.
5. Copy the Client ID and Client Secret — you'll send both to ElevateOS.

You should now have two pairs of credentials: one Password pair and one Invitation pair.

Step 6 — Send the credentials to ElevateOS

Add the four values to your ElevateOS support ticket, or send them through whatever secure channel your ElevateOS representative has set up:

• Password Client ID
• Password Client Secret
• Invitation Client ID
• Invitation Client Secret

ElevateOS stores them encrypted and finishes enabling Brivo for your building.

Step 7 — Verify with a test resident

Once ElevateOS has confirmed Brivo is enabled for your building:

1. Pick a resident, or create a test client, whose email matches a person record in Brivo.
2. On their phone, sign in to the ElevateOS resident app.
3. Open Brivo and confirm a mobile credential is issued.
4. Test Bluetooth unlock at one of the doors they're entitled to.
5. If you're using visitor PINs, create a test visitor pass with PIN access enabled and confirm the PIN works at the door during the valid window.

After connection — what to plan for

• Email hygiene is the main ongoing task. Brivo lookups are email-based. Any mismatch between Brivo and ElevateOS means the resident is told "not found" the first time they try to unlock. Audit emails when onboarding new residents and after email changes.
• Move-out revoke is manual. ElevateOS does not auto-revoke Brivo credentials when a resident moves out. Add "revoke Brivo credential" to your move-out checklist.
• Re-issue cleanly when residents change phones. Use revoke and re-issue rather than leaving stale credentials in place.
• Visitor PINs auto-expire. As long as you set both a start and end time on each visitor pass, PINs invalidate themselves at the end of the window.

Troubleshooting connection issues

• Resident isn't found in Brivo. The resident's email in ElevateOS doesn't match any person record in Brivo. Confirm the email matches exactly on both sides. If the email recently changed, force a PMS sync or update the resident manually in Brivo.
• Credential issuance fails. Confirm the ElevateOS administrator account in Brivo is still active and assigned to the right sites. Confirm the Password and Invitation tokens haven't been revoked or rotated in Brivo. If credentials were rotated, send the new Client ID and Client Secret pair to ElevateOS.
• Residents are receiving Brivo's automated invitation emails alongside ElevateOS-issued credentials. Brivo's automated emails weren't fully disabled. Re-check the Brivo configuration or open a ticket with Brivo support to confirm Mobile Credential invitation emails are off for your account.
• Visitor PIN doesn't appear in the visitor pass form. Confirm visitor PIN access is enabled for your building in ElevateOS. Without it, the PIN code option doesn't show.