Linking Pure Access Cloud with Engage

To add supported Schlage devices (RC11, RC15, RCK15, LE, LEB, NDE, NDEB) to a Pure Access Cloud tenant, the tenant must first be linked with Engage. Once linked, the tenant undergoes some changes which are addressed here.

Commissioning Hardware

  • Schlage devices commission to an Engage site created when the PAC Tenant is linked with Engage.
  • Legacy Isonas RC-04 and IP Bridges continue to commission directly to Pure Access Cloud through the ISONAS configuration tool.

Credential Changes After Linking

Schlage devices do not read data in the same manner that Isonas devices do*. Therefore, when a tenant is linked with Engage, credential enrollment is changed to comply with the requirements of Schlage devices (see below). As a result, existing credentials (except Isonas Pure Mobile and Key Pins) go into an “Unknown Format” that will still work with Isonas devices; but will need to be migrated or re-enrolled before they will work with compatible Schlage devices.

Credential Migration

Migration converts existing credential data into the format required by Schlage devices, and requires the credential’s format to be known and entered. See Migrating Credentials (Legacy to Engage) [link TBD] for the procedure.

  • If migration fails:
    • Present the credential at an RC04 where it will be declined or at either an RC03 or IP Bridge where either it can be approved or declined.
  • If migration fails again:
    • The credential will need to be re-enrolled for it to work with compatible Schlage devices.

Whats required to for a credential to migrate successfully

Credential migration will work if:

  • The user selects the correct format when performing the migration.
  • The existing credential GUID contains the full decline data, which results from:
    • Presentation enrollment.
    • Manual enrollment, followed by the credential being declined at an RC04, or approved or declined at an RC03 or IP Bridge.

Credential migration will not work if:

  • The user selects the wrong format. If this happens, it will not prevent migration from being moving forward; however the resulting credential is not going to work.
  • The credential was enrolled manually and only approved at RC04s thereafter.

Credential Enrollment Methods

Method Requirements
Presentation Enrollment This can only be performed at a Schlage RC and it requires the correct credential format to be entered.
  • If you add only Schlage Wi-Fi devices (NDE, LE) to a tenant with existing Isonas devices, presentation enrollment will not be available on that tenant until a Schlage RC is enrolled. .
Manual Enrollment Requires the correct credential format, facility code, and badge ID. Facility code is not required for Isonas Proprietary Prox, Isonas DESFire, Isonas HID, Isonas Mobile, or Schlage Mobile credentials.

Supported Credential Formats

Although Schlage devices can support numerous 125kHz Prox formats and 13.56MHz smart credentials, when utilizing both Isonas and Schlage devices in the same Pure Access Cloud tenant, it is important to utilize a credential format that is supported by both devices and that the bitmask be set properly on Isonas devices.

Isonas devices can only support ONE Prox format credential via bitmasking and therefore once a prox format credential has been selected and the bitmask pushed out to the Isonas devices, you will want to stay with that format in order to avoid credential read issues going forward

Mobile Credentials

Credential Compatible hardware
Isonas Pure Mobile RC-04 Reader Controllers and IP Bridges equipped with Isonas R1 readers.
Schlage Mobile Schlage Reader Controllers, Bluetooth-enabled NDEB/LEB Wi-Fi locks, and IP Bridges with MTB readers. Requires Schlage Compatibility Mode enabled on the corresponding IP Bridge access point in Pure Access Cloud device settings.

Both mobile ID apps can be installed on the same phone and tied to the same cardholder record. Select the app that matches the reader or controller model at each access point.

Credential Special Properties

Setting Behavior with Schlage devices
Credential Time Limit Resolves to the hour, not the minute (as Isonas devices do). A 9:40–11:15 window approves the credential between 9:00 and 11:00.
Credential Count Limit Approvals at Wi-Fi devices do not deduct from the count limit on check ins.

Auto-Unlock with Badge (“First Person In”)

Auto-Unlock w/Badge rules are configured differently with Schlage devices, using a feature called First Person In. Enable it under Auto-Unlock rules in the Schlage Reader Controller’s device settings. Any user with Grant Access permission at the access point during the auto-unlock window can start the unlock by presenting a valid credential.

Holiday Events

Schlage devices do not support single events that run beyond 24hrs and therefore Holiday Events are not available in Engage linked tenants.
Events (Lock, Unlock and Lock Down) can be used to achieve similar outcomes. For periods extending beyond 24hrs, individual events must be created or each day.

The only event that will override a Grant Access weekly rule is a Lock Down event; wherein the only users that will have access are those with permission via an existing weekly rule AND who hold a credential with the Pass Through special property. An alternate option is to temporarily deactivate the weekly rule and then reactivate it at the end of the desired period

Tenant Global Settings

Setting Behavior with Schlage devices
Global Re-lock Time Does not currently apply to Schlage devices.

Active Directory

Once a tenant is linked with Engage, Active Directory can no longer sync credential data — only users and user groups. Active Directory integration requires an RMR or 51+ door license.

Hardware Differences: RC-04 vs. Schlage RC

Look here for more details between the RC-04 and Schlage can be found here.

Using the Engage Mobile App

ALL administration is performed in Pure Access cloud (device settings, user management, schedules, etc).
For Pure Access Cloud integrations, the Engage mobile app is used ONLY for:

The Engage mobile app is ONLY use for:

  • Commissioning supported Schlage devices
  • Schlage device network configuration
  • Updating Schlage Wi-Fi devices from the server outside their scheduled check-in window

Additional Resources

Expanding Your Pure Access Cloud Business with Schlage’s Wi-Fi Locks
A video that gives a good overview of linking a PAC tenant with Engage

Linking to Engage section of the Pure Access Manual that explains how to link with Engage

Adding a Schlage device using ENGAGE section of the Pure Access Manual that deals with commissioning Schlage devices into Pure Access

Last modified: 10 September 2026

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.