ElevateOS & Openpath / Avigilon Alta Integration: Property Manager Guide

For: Property managers and on-site staff

This guide covers how Openpath cloud unlock works for residents through ElevateOS, what property managers do in the Openpath dashboard, and how to handle common issues. Use it as a reference when onboarding a building to Openpath or troubleshooting a resident's access.

Background

Openpath lets residents unlock building doors from inside the ElevateOS resident app. There's no separate Openpath app for residents to install and no login step — the first time a resident uses Openpath, ElevateOS matches them to their existing Openpath user by email and they're ready to go.

Most of the work happens in the Openpath dashboard, not in ElevateOS. ElevateOS reads each resident's entries from Openpath and exposes them in the resident app. User creation, entry assignment, and account deactivation are all handled in Openpath.

Unlike Bluetooth-based systems, Openpath unlock is cloud-based — the resident's phone needs internet at the moment of unlock.

What residents see

Inside the ElevateOS resident app, residents get:

A list of accessible entries pulled from their Openpath user record
Cloud unlock — tap an entry and the door opens
The option to favorite frequently used entries

Residents do not need to install the Openpath app.

How resident unlock works

The first time a resident uses Openpath in the ElevateOS resident app:

The app looks them up in your Openpath organization by email.
If they don't already have a cloud-key credential, one is created automatically.
The list of entries they have access to appears in the app.

For day-to-day use:

The resident taps an entry in the app.
The app sends an unlock request to Openpath.
Openpath authorizes and the door opens.

Because unlock runs through Openpath's cloud, the resident's phone needs Wi-Fi or cellular at the door.

What property managers control

Openpath user lifecycle and door permissions are managed in the Openpath dashboard, not in ElevateOS. The ElevateOS resident profile shows whether a resident is connected to Openpath, but permissions are sourced from Openpath.

Day-to-day, in the Openpath dashboard:

Create or update users when residents move in or change permissions
Assign or change entries for each resident
Disable users when residents move out

ElevateOS reads from this configuration; it does not write to it.

Resident requirements

For Openpath to work for a resident:

They have Current status in your PMS
A user record with their email already exists in your Openpath organization
That user has at least one entry assigned to them in Openpath
Their phone has internet at the moment of unlock

Best practices

1. Email is the link

The integration matches residents to Openpath users by email. Mismatches are the most common source of failure — keep emails canonical and consistent on both sides. When you change a resident's email in one system, change it in the other.

2. Treat Openpath as the source of truth

Door permissions are configured in the Openpath dashboard. Don't look for door pickers on the ElevateOS resident profile — there aren't any.

3. Build move-out discipline

Disable the resident in the Openpath dashboard as part of your standard move-out process. ElevateOS will not auto-revoke access.

4. Set onboarding expectations

When a new resident moves in, tell them:

Their phone is their key — no separate Openpath app needed
The first unlock connects them automatically, with no login step
Unlock requires internet at the door — if their phone has no signal in a basement garage or stairwell, unlock will fail there

Troubleshooting

"User not found" the first time a resident uses Openpath. The resident doesn't exist in your Openpath organization, or their email doesn't match. Check the email on the Openpath user record and update either side so they match exactly. Then have the resident retry from the app.
Resident is connected but sees no entries. No entries are assigned to them in Openpath. Assign at least one entry in the Openpath dashboard and have the resident refresh the app.
Cloud unlock fails at the door. Confirm the resident's phone has Wi-Fi or cellular reach at that location. Confirm the entry is in the user's permission list in Openpath. Dead zones at specific doors are usually a connectivity issue, not an Openpath issue.
Resident still has access after move-out. Disable the user in the Openpath dashboard. ElevateOS does not auto-revoke.

FAQs

Does the resident need the Openpath app? No. Cloud unlock happens inside the ElevateOS resident app.

Does unlock work without internet? No. Openpath is cloud-based — the phone needs internet at the door.

Can I configure which doors a resident can open from inside ElevateOS? No. Door permissions are managed in the Openpath dashboard.

Does ElevateOS create Openpath users automatically? No. Residents must already exist in Openpath. ElevateOS links them on first use and creates the cloud-key credential if one doesn't already exist.

What happens when a resident moves out? Disable the user in the Openpath dashboard. ElevateOS will not auto-revoke.