No-Tour Sync

Overview

The No-Tour Sync feature allows Administrators to assign and change access rights for offline and wireless devices without having to physically visit the lock to make access programming updates.

*Access updates can still always be accomplished through the normal Sync process or when device configuration is also being adjusted.
online devices DO NOT use sectors on a credential since they are synced solely through Compile.

When you change someone’s access in the Zentra web app and then program a new credential (physical or mobile), that credential will “carry” the new access information out to the lock.
Once the credential is presented to the lock:

• ADD commands will grant new access to a user.
• BLOCK commands will remove or deactivate previous users’ access on that lock.
  

Using No-Tour Sync

1. Assign or Change a user’s property access.
2. When you get to the credential portion, make sure to use either a physical credential or a Zentra Mobile Credential.
   • Keypad codes cannot be used for no-tour operations.
3. When you are ready to program the credential, you will see the devices that will be added/blocked on the credential. Some of these devices are for the user you are currently editing, and others may be for access that recently changed in the system for other users.
4. Notice the Edit icon in the top right corner. If there are devices that are a higher priority to have added/blocked than others, you can change which devices will be added to the credential, and which will need to be updated via Sync with the mobile app. Click Edit to edit the devices.
   
5. Click the check boxes to select/deselect which devices you want to program with this credential via no-tour sync.
   • Notice the number of devices updates in the top right, so you can keep track of how many devices you have checked.
6. Then, click Save.
   
7. You will see the first screen again, but with the devices arranged with the new priority. Click Next.
8. You will be directed through the Program credential process as usual.
9. Once the credential is programmed, it should be presented to each device that needs to have access updated (every device in the list from step 7).
   

Common Use Cases

Scenario 1 – Granting Access to a New Tenant – Tim is moving into Apartment 501:

1. In the Zentra web app, add Tim to Apartment 501 and any common areas (pool, laundry, etc.).
2. Real-time locks (e.g., perimeter doors) update immediately over the internet once you save and compile.
3. Wireless or offline locks need you to program Tim’s new credential or wait for a scheduled check-in (if applicable).
4. When Tim taps his new credential at Apartment 501’s lock, the lock “pulls in” the ADD command and grants him 24/7 access.
   

Scenario 2 – Removing Access for a Departing Tenant – Sherry is moving out of Apartment 321 and returns her credential:

1. In the Zentra web app, deactivate Sherry’s credential or user profile.
2. The next time any user with valid access to Apartment 321 gets a newly programmed credential, that credential will also carry a BLOCK command for Sherry’s old credential.
3. When presented to the lock on Apartment 321, the lock receives that BLOCK command and permanently removes Sherry’s access.
   

!If a resident fails to return all of their credentials, Zentra recommends you immediately sync the lock with the mobile app to ensure the missing credentials are blocked right away.

Important Notes & Best Practices

1. Offline vs. Real-Time vs. Wireless Locks
   • Real-time locks (connected via IP or Schlage RC) update immediately after you push a compile.
   • Wireless locks (e.g., Schlage NDE/LE configured for scheduled check-ins) eventually update on their own or can be manually synced.
   • Offline locks (Schlage Control, XE360, or NDE/LE if not on a wireless schedule) need either a credential presentation (no-tour) or a mobile app sync to receive updates.
2. When to Sync (Tour) Instead
   • If you need to remove someone’s access right away and they haven’t returned every credential/fob, you should walk to the lock and “sync” it with the Zentra mobile app.
   • If there are more than 11 access changes (e.g., many BLOCKs at once), the system may require a sync instead of no-tour programming.
3. Credential Programming Limits
   • Each no-tour programming attempt can write up to 11 changes (ADD or BLOCK) onto a single credential. If you have more changes pending than that, you must either sync or split up the programming among multiple credentials.
4. Schedule Changes Need a Sync
   • Any updates to lock schedules or time-based access windows (e.g., adjusting business hours) require a full sync via the mobile app. These schedule frameworks cannot be delivered via no-tour commands.
5. You Can Re-Use Credentials
   • Zentra’s no-tour technology allows you to clear or overwrite old credentials to grant new access. This is useful when recycling credentials for multiple residents over time.

Key Takeaways

• No-tour eliminates extra trips to offline/wireless locks by using newly programmed credentials to deliver changes.
• Real-time locks update instantly after you save and compile.
• Offline/wireless locks can be updated either by presenting a credential programmed with no-tour commands, waiting for scheduled check-ins (if wireless), or by syncing with the mobile app.
• If there’s any doubt that all old keys are returned, tour the lock to immediately block those keys.
  

No-tour is meant to save time and streamline your operations—giving you the flexibility to handle most access updates from the comfort of your office and only visit locks when absolutely necessary.