ElevateOS & Swiftlane Integration: Setup and Connection Guide

For: Property managers, on-site IT, and Swiftlane administrators connecting a new building to the Swiftlane integration

This guide walks through everything needed to connect a building to Swiftlane in ElevateOS. There are two paths depending on which features you want — pick the one that matches your building.

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

Pick your path

Path A — Keyless access only. Residents unlock doors from the resident app, and visitors can be given PIN codes. Setup needs only an API token shared with ElevateOS. This is the lighter path.

Path B — Full setup. Keyless access, intercom calls ringing inside the resident app, automated daily resident provisioning, and visitor PIN codes. Requires a one-time authorization request to Swiftlane.

You can start with Path A and upgrade to Path B later.

Path A — Keyless access only

Before you start

Have these in hand:

• An active Swiftlane account with admin access
• Admin permissions to generate an API key in the Swiftlane admin portal
• Your Swiftlane account name (visible under account settings)

Step 1 — Generate an API token in Swiftlane

In your Swiftlane admin portal:

1. Go to Settings → API Keys.
2. Generate a new API key for ElevateOS.
3. Copy the token.

A walkthrough video is available: How to obtain an API key

Step 2 — Send the token to ElevateOS

Send your ElevateOS representative:

• The API token from step 1
• Your Swiftlane account name

ElevateOS stores both encrypted and finishes enabling Swiftlane keyless access for your building.

Step 3 — Verify with a test resident

1. Pick a resident, or create a test client, whose email matches their Swiftlane user.
2. On their phone, sign in to the ElevateOS resident app.
3. Open Swiftlane and confirm the assigned doors appear.
4. Test cloud unlock at one of the doors.

If the resident sees no doors, see Troubleshooting connection issues below.

Path B — Full setup

This path covers keyless access, intercom calls, automated resident sync, and visitor PIN codes. ElevateOS needs deeper access to your Swiftlane account, which Swiftlane authorizes on request.

Before you start

Have these in hand:

• An active Swiftlane account with all integrations you plan to use (intercoms wired up, residents already provisioned or ready to be provisioned)
• Your Swiftlane account name and property name
• A decision on which sub-features you want enabled — keyless access, intercom calls, auto resident sync, visitor PINs
• The IDs and names of the Swiftlane access groups for residents and visitors
• A decision on whether to auto-assign apartment doors for residents and / or visitors

Step 1 — Authorize ElevateOS with Swiftlane

Email integrations@swiftlane.com and ask Swiftlane to authorize the elevatedliving account so ElevateOS can access your property's Swiftlane account.

Suggested message:

We're integrating our Swiftlane account with ElevateOS. Please authorize the ElevateOS account (Account Name: elevatedliving) to access our property.

Property name: [your property] Swiftlane account name: [your account name]

Step 2 — Notify ElevateOS once Swiftlane confirms

When Swiftlane confirms the authorization, let your ElevateOS representative know. They'll finish the configuration on the ElevateOS side.

Step 3 — Decide which sub-features to enable

Swiftlane in ElevateOS has four independent feature flags:

Keyless access is the base requirement. The other three are optional. Tell your ElevateOS representative which combination you want.

Step 4 — Identify your access groups

ElevateOS needs to know which Swiftlane access groups to assign by default. Send your representative:

• Resident user group IDs — the access groups auto-assigned to every new resident (for example, All Residents, Common Areas, Parking Gate)
• Visitor user group IDs — the access groups assigned when visitor PIN codes are generated (for example, Lobby Access, Main Entrance)

Each group has an ID and a name, both visible in the Swiftlane admin portal under Access Groups.

Step 5 — Decide whether to auto-assign apartment doors

Two independent options:

• Auto-assign apartment door (resident) — when a new resident is provisioned, their apartment door is added automatically by matching the apartment number to a Swiftlane unit name.
• Auto-assign apartment door (visitor) — when a visitor PIN is generated, the host's apartment door is added in addition to the visitor default groups.

Auto-assign uses case-insensitive exact matching between apartment numbers in ElevateOS and Swiftlane unit names. If names can't be aligned, leave auto-assign off and pick doors manually per resident.

Step 6 — Verify with a test resident

1. Confirm a test resident shows up in Swiftlane — either through auto-sync, or provisioned manually by ElevateOS.
2. On their phone, sign in to the ElevateOS resident app.
3. Confirm the assigned doors appear and test cloud unlock at one.
4. If intercom calls are enabled, buzz the unit on a Swiftlane intercom panel and confirm the call rings inside the resident app.
5. If visitor PINs are enabled, create a test visitor pass with PIN access and confirm the PIN works at the door during the valid window.

After connection — what to plan for

• Daily resident sync runs once per day. Residents added late in the day are picked up by the next run. For move-ins that need access immediately, provision them manually on the resident profile.
• Auto-sync only creates users. It doesn't deactivate residents whose leases end — Swiftlane handles deactivation on its own based on the date set when the user was created.
• Mid-stay door changes happen on the resident profile. Changes to access levels during a lease apply immediately and don't wait for the daily run.
• Intercom calls require resident permissions. Residents need to grant notification permissions on their phone, and Swiftlane's intercom configuration needs to be set up correctly with your installer.
• Visitor PIN validity. PIN codes generated through ElevateOS are valid from midnight to 11:59 PM on the day of issuance.

Troubleshooting connection issues

• API token doesn't work (Path A). Confirm the token was issued from the right Swiftlane account and hasn't been revoked. Generate a fresh token and re-send.
• Swiftlane hasn't responded to the authorization email (Path B). Follow up directly with integrations@swiftlane.com. ElevateOS can't proceed with Path B until Swiftlane confirms.
• Resident provisioned but sees no doors. If you rely on auto-assign apartment door, confirm the apartment number matches a Swiftlane unit name exactly. If names don't match, pick doors manually on the resident profile. Confirm at least one default access level is configured for your building.
• Daily sync isn't creating new residents. Confirm auto resident sync is enabled for your building. Confirm the resident has Current status in your PMS with an active lease window.
• Intercom calls don't ring inside the resident app. Confirm intercom calls (VOIP) are enabled for your building. Confirm the resident has granted notification permissions to the resident app. Confirm Swiftlane's webhook is configured correctly — your ElevateOS representative can verify.
• Visitor PIN flow doesn't appear in the visitor pass form. Confirm visitor PIN access is enabled for your building, and that visitor user group IDs were provided in step 4.