No. Enhanced Offline Access builds on No-Tour Sync and is fully compatible with existing workflows. The programming steps are the same — the system now uses Group IDs behind the scenes to fit more access onto a single credential. You do not need to change how you program credentials day-to-day.

It depends on how your No Tour Groups are configured. If your doors are organized into groups, the system uses Group IDs to cover multiple doors per sector. With 11 sectors and up to 2 commands per sector, a single credential can hold up to 22 commands — covering significantly more than 11 individual doors when Group IDs are used. If the total still exceeds the credential limit, the system will prompt you to select which access to program now and deliver the rest separately via Sync or a second programming session.

First, confirm the user has access to that door in the Zentra web app. If the door is an offline lock, check whether the credential has been programmed for that door — navigate to the user’s profile and look at the credential programming history. If the credential was deactivated or there are pending blocks on any credential for that door, check block status for any credential that previously had access to that location. If the device has never been synced after No Tour Groups were configured, it may not recognize Group ID commands — sync the device and re-program the credential.

A credential-level block is programmed to the physical credential itself. It prevents that credential from using No-Tour to re-add its own access if it is ever presented to a lock in the future. This type is used for returned credentials where you have physical possession. A door-level block is stored in the lock’s database and prevents a specific credential from working at that lock even if it is presented. This type is used for lost or stolen credentials. Door-level blocks must be delivered to each lock via Sync, a block credential, or piggybacking.

Check the credential’s block status. If blocks have already been delivered to the locks, the credential cannot be safely reused without re-programming, as the door databases now reject it. If blocks are still pending delivery, contact your Zentra administrator about reversing the lost status. In either case, if the credential needs to be put back into active use, it will need to be re-programmed via the standard credential programming workflow.

Piggybacking delivers blocks the next time any credential is programmed for a user who has access to the affected door, and then presented at that door. Timing is completely unpredictable — it could be minutes if a credential is being programmed right now, or days if no credential programming happens at that door. Do not rely on piggybacking for lost or stolen credentials. Use Sync or a block credential for urgent situations.

Yes — you can deselect devices that require Sync during the Edit credential access screen, then deliver that access separately via the Zentra Mobile App Sync. However, until the device is synced or the credential is presented there, the user will not have access at that door. For critical locations such as unit doors or main building entrances, complete the Sync or credential presentation promptly.

No. Keypad codes cannot be used for No-Tour operations. If a user accesses doors by keypad code only, their access is managed through the standard Compile process in the Zentra web app. Enhanced Offline Access programming requires a physical credential (fob or card) or a Zentra Mobile Credential.

The operation will fail with a connection error. The credential will remain in its previous state — it will not be partially programmed. Restore the internet connection to the Enrollment Reader and retry the programming operation.

The device must be commissioned with the Zentra Mobile App before it can receive No-Tour access updates. Navigate to Devices in Zentra and complete the commissioning process, then return to program the credential. Additionally, if No Tour Groups were recently configured at your site, make sure the device has been synced at least once since that configuration was applied — unsynchronized devices will not recognize Group ID commands.

No. A credential with pending blocks is not ready for reuse. All pending blocks must be fully delivered before the credential can be safely assigned to a new user. Assigning a credential with undelivered blocks could cause an access conflict if the new user’s access overlaps with a blocked location. Use the Identify Found Credential workflow or the credential detail view to check block status and deliver all blocks before reassignment.

Use Sync when: you need to remove access immediately and cannot wait for the next credential presentation; a user has more access changes than can fit on a single credential; you need to update schedule changes (schedule changes cannot be delivered via credential programming and always require a Sync); or a device requires direct connectivity to receive its update. If there is any doubt about whether a lost credential has been blocked at a particular door, syncing that door is the fastest way to confirm delivery.