How to remove user access on a TTLock smart lock

Smart Lukko is an independent third-party app for TTLock-compatible smart locks, not affiliated with TTLock or Sciener, and revoking access follows the same underlying rules as the wider TTLock ecosystem. Before removing anyone's access, make sure you have:

• Admin or authorised-admin rights on the lock; normal eKey holders cannot revoke other users.
• Bluetooth range of the lock, or a working paired gateway, for any change that has to physically write to the lock's memory (passcodes, cards, fingerprints).
• An idea of what to remove — check the user list first so you revoke the right eKey, passcode, card or fingerprint rather than a similarly named entry.

1. Revoke an eKey. Open the lock, go to the user or eKey list, select the person, and tap Delete/Revoke eKey. This is generally sent through the cloud, so it can take effect even if you are not standing at the door, once the recipient's app or the lock next syncs.
2. Delete a passcode. Open Passcodes, select the code to remove, and tap Delete. If it is a synced (not offline-algorithm) passcode, this deletion needs to reach the lock's own memory — connect over Bluetooth or let a gateway push it.
3. Remove a card or fingerprint. Open Cards or Fingerprints, select the entry, and tap Delete. These almost always require a live connection to the lock (direct Bluetooth or via gateway) because the credential template is stored physically on the lock's controller board.
4. Confirm the sync completed. The app typically shows a spinner or success message when the deletion has actually reached the lock; if it fails, move closer or check the gateway's status before assuming the user is locked out.
5. Re-check the user list. Refresh the screen to confirm the eKey, passcode, card or fingerprint no longer appears.

eKeys live primarily in the cloud account system, so revoking one is often just a database change that the recipient's app respects the next time it checks in — no direct radio link to the lock is strictly required for the revocation to be recorded, though the lock itself may need a sync for fully offline enforcement. Passcodes, cards and fingerprints, by contrast, are stored as data directly on the lock's own controller. Deleting them from the app only queues the instruction; the lock has to actually receive and execute that instruction to erase the credential, which means either your phone connecting over Bluetooth or a paired gateway relaying the command over Wi-Fi. Until that sync happens, the old card, fingerprint or offline passcode will still work at the door even though it looks deleted in the app.

After removing access, it is worth confirming the change actually reached the lock rather than assuming the app screen tells the full story:

• Re-open the user, passcode, card or fingerprint list and verify the entry is gone after a sync, not just marked pending.
• Check the unlock records for any successful entries using the revoked credential after the deletion time, which would indicate the sync had not yet reached the lock.
• Test in person for high-stakes situations, such as an ex-employee or a lost card, by attempting the old code or card yourself once the deletion should have synced.