This section provides an introduction to the blocklist.

The blocklist is a list of keys that are, for one reason or another, being denied from accessing the locks. The lock does not allow keys on the blocklist to open itself.

The blocklist version number is incremented by one every time a change is made.

The blocklist is zone-specific, if zones are enabled. Zone-specific blocklists allow to add 500 blocked keys to each lock on the zone. If a lost key has access rights to several zones, the system automatically generates blocklist updates for all zones where the key has access rights. The blocklists of locks are updated by keys, which have the lock's zone defined as the main zone.

See the figure below:

Table 1. Zone-specific blocklists

			System Master key Main zone: A Other zones: B, C Access rights: Estate A, B and C Can carry a blocklist for Zone A locks Blocklists to zone B and C must be updated with zone specific keys
	Estate A master key Main zone: A Other zones: none Access rights: Estate A Can carry a blocklist for Zone A locks only Can add a lost System Master key to Zone A blocklist		Estate B master key Main zone: B Other zones: none Access rights: Estate B Can carry a blocklist for Zone B locks only Can add a lost System Master key to Zone B blocklist		Estate C master key Main zone: C Other zones: none Access rights: Estate C Can carry a blocklist for Zone C locks only Can add a lost System Master key to Zone C blocklist
Zone A Estate A		Zone B Estate B		Zone C Estate C

If zones are disabled, the blocklist is system-wide, 500 keys for each lock. All keys update the latest blocklist to locks.

Blocklisting is a rarely needed operation, as the online capability makes is possible to manage keys remotely over-the-air. However, with blocklisting you can ensure that a key that is in the offline state (that is, cannot receive updates from the server) and does not have offline expiration time defined, cannot access a lock.

The keys get the blocklist as follows:

• Phone Keys

  • Over-the-air through the mobile network.

  • From the lock.

    If a key used on the lock has an older version of the blocklist than the lock, the lock updates the blocklist on the key. Now, the key can take the newer blocklist to the next lock.

• Key Fobs

  • Over the Programming Token.

  • From the lock.

    If a key used on the lock has an older version of the blocklist than the lock, the lock updates the blocklist on the key. Now, the key can take the newer blocklist to the next lock.

  • Through the FobApp.

• S5 keys

  • Over the Programming Token.

  • From the lock.

    If a key used on the lock has an older version of the blocklist than the lock, the lock updates the blocklist on the key. Now, the key can take the newer blocklist to the next lock.

You can upload the blocklist information to the locks through keys and the Programming Token. Networked locks and door modules receive the blocklist information automatically and keys can collect the latest blocklist from the iLOQ RFID readers, and the keys take the latest blocklist to offline locks.

The Up to date blocked list column in the lock list indicates whether the lock has the latest blocked list version or not.

• If there is a check mark in the check box, the lock already has the latest blocked list version and no actions are needed.
• If the field is empty, the blocked list must be updated for the lock. This can be done by visiting the lock with the key that has the latest blocked list version.

The number of keys on the blocklist is limited. It is not always necessary to add Phone Keys to the blocklist, as you can simply empty online Phone Keys over-the-air. Furthermore, you can also set an offline expiration time for Phone Keys. When the offline expiration time has elapsed, the key is invalidated. This feature ensures that no key with outdated credentials will remain on the field.