ElevateOS & Pointcentral Integration: Setup & Connection Guide

For: Property managers and Point Central administrators connecting a new building to the Point Central integration

This guide walks through everything needed to connect a building to Point Central in ElevateOS. Once connected, residents are auto-linked to their unit's Point Central customer record and can unlock doors and adjust thermostats from inside the resident app — no resident login required.

For day-to-day usage of the integration once connected, see the Point Central X ElevateOS Property Manager Guide.

Before you start

Have these in hand:

• An active Point Central account with admin access at the building level
• The admin username and password for that account
• Your building's haiku — the unique customer identifier Point Central assigns to your property
• An apartment-naming convention used in ElevateOS that matches (or can be aligned to) the customer / unit names in Point Central
• A decision on which Point Central sub-features you want enabled — locks, thermostats, or both
• Confirmation from your Point Central administrator that current residents have customer records configured with the right apartment names and door / thermostat assignments

Step 1 — Confirm Point Central has your residents configured

Before connecting, confirm that each resident you want to enable already has, on the Point Central side:

• A customer record
• The correct apartment name on that record
• At least one door assigned (if you'll enable locks) and / or at least one thermostat (if you'll enable thermostats)

Anything missing on the Point Central side means the affected residents will have nothing to unlock or control after the connection runs.

Step 2 — Align apartment names

Auto-mapping uses case-insensitive exact matching between apartment names in ElevateOS and customer apartment names in Point Central. If names differ, residents won't be matched.

• Apartment 101 matches customer apartment 101 ✓
• Apartment Apt 101 does not match customer apartment 101 ✗

Pick one convention and apply it on both sides before the next step. If you discover mismatches later, you can fix the names and use Disconnect Resident on the affected profile to force a fresh mapping attempt.

Step 3 — Decide which sub-features to enable

Point Central in ElevateOS has two independent features:

• PointCentral locks — exposes door unlock to residents
• PointCentral thermostats — exposes thermostat control to residents

You can enable just locks, just thermostats, or both. Decide before the next step — your choice gets passed to your ElevateOS representative along with the credentials.

Step 4 — Provide credentials and configuration to ElevateOS

Send your ElevateOS representative:

• The Point Central admin username
• The Point Central admin password
• Your building's haiku
• Your sub-feature choice from step 3 (locks, thermostats, or both)

Your representative will register the integration on your building. ElevateOS:

1. Logs in to Point Central with the admin credentials
2. Pulls the list of customer records and their apartment names
3. Matches each customer to a resident in your building using case-insensitive exact apartment-name matching
4. Stores the apartment-to-customer mapping for every successfully matched resident
5. Encrypts and stores the admin credentials for ongoing use

Credentials are stored encrypted at rest.

Step 5 — Verify with a test resident

Pick one resident, or create a test client, to confirm everything works end-to-end:

1. Confirm their apartment in ElevateOS matches a Point Central customer's apartment exactly.
2. On their phone, sign in to the ElevateOS resident app.
3. If locks are enabled, confirm the assigned locks appear in Keyless Access and test cloud unlock at one.
4. If thermostats are enabled, confirm the thermostats appear in Smart Home and test changing the target temperature, mode, and fan mode.

The resident does not enter any Point Central credentials. If they see no locks or thermostats, the apartment-to-customer mapping likely didn't take — see Troubleshooting below.

After connection — what to plan for

• No resident credentials needed. Once their apartment is matched to a customer, residents just open the resident app and their locks and thermostats are there.
• Use Disconnect Resident on unit moves. When a resident changes units, click Disconnect Resident on their profile. The next time they open Point Central in the resident app, the mapping is recreated against the new unit.
• Apartment renames break mappings. Renaming an apartment in either system can break the existing mapping for that resident. Audit after renames and use Disconnect Resident to force a clean re-link.
• New residents need to be mapped. A resident added after the initial connection won't show up automatically until their mapping is created. Re-run the building integration, or use a per-resident remap if available, to pick them up.
• Move-out cleanup happens in Point Central. Disable each departing resident's customer record in Point Central. Once the resident is no longer Current in your PMS, their mapping in ElevateOS also drops.
• Webhook events. Point Central can send webhook events for door and thermostat activity. ElevateOS receives these today; event-driven notifications inside the resident app are an upcoming feature.

Troubleshooting connection issues

• Admin login fails. Confirm the admin username and password are correct and the account is active in Point Central. Confirm the haiku matches your actual building or property identifier.
• Some residents weren't mapped at registration. Compare apartment names in ElevateOS with customer apartment names in Point Central — naming mismatches are the most common cause. Fix one side. Affected residents can also be mapped on their first Point Central use in the resident app, provided names align by then.
• Resident sees no locks. Confirm PointCentral locks is on for your building. Confirm the customer record in Point Central actually has doors assigned. Confirm the lock devices are online in Point Central. Confirm the apartment-to-customer mapping was created — use Disconnect Resident on the profile to force a fresh attempt.
• Resident sees no thermostats. Confirm PointCentral thermostats is on for your building. Confirm the customer record in Point Central has thermostats assigned. Confirm the thermostat devices are online in Point Central. Confirm the apartment-to-customer mapping was created — use Disconnect Resident on the profile to force a fresh attempt.
• Resident is on the wrong unit's locks / thermostats. Use Disconnect Resident on their profile in ElevateOS, then have them open Point Central again from the resident app.
• Re-registration after credential rotation. If the Point Central admin credentials change, re-register the building with the new credentials. Existing apartment-to-customer mappings stay in place; only the building-level session is renewed.