This section describes how to edit the locking system settings on iLOQ Manager.

1. Select Administration > Edit locking system information.

   

    
2. Select Settings in the Views area.
3. The system settings screen is opened. The settings are:

   • Handed over key can be attached to another person without returning the key — If this setting is in use, you can detach or re-attach a handed-over key to another person without returning the key first. This feature is useful, if the key changes owner without returning the key to the administrator.

     Note:

     If you attach a handed-over key to another person without returning the key first, pay attention to the audit trails on locks that have no clocks. These audit trails will show that the key owner is the person to whom the key was attached to at the audit trail picking moment, as a clockless lock does not know when the person has changed. If the key is returned before handing it over to a new person, even the clockless locks will know which user has accessed the lock. Therefore, it is recommended to return the key before handing it over to a new person.

   • Estate functionality active — If this setting is used, estates are enabled. For more information, see Estates.

   • Code-access groups in use — If this setting is used, code-access groups are enabled. For more information, see Calendar Controlled Doors.

   • Key PIN-codes in use — If this setting is used, key PIN-codes are enabled. For more information, see Calendar Controlled Doors.

   • Key RFID tag number function available — The keys can contain RFID tags. If this is the case, the RFID data can be managed as follows:

     • Not in use — The keys contain no RFID tags.
     • Field locked — The keys with RFID tags are delivered by iLOQ, and the tags contain unique IDs. The unique ID is automatically transferred to the software when the key is programmed. You cannot edit the ID manually.
     • Field editable — The keys are delivered by iLOQ. The keys are equipped with RFID tags by the customer, and the tags contain identifiers. The user must type in the tag identifier manually when programming the key. The user can later edit the identifier.

   • Default access right — You can select the system default access right in this drop-down menu. The default access right will be automatically added to new locks.

   • Net Bridge firmware remote update in use — If this setting is in use, Net Bridge automatically updates the software and firmware on itself and on the bus devices.

   • Update time — You can define the start time for the allowed software and firmware installation period. The allowed installation period lasts for three hours.

   • Postponed Hot spot key update in use — If this setting is in use, you can define access right changes on keys for the future. These changes are not available at the Key Programming Hot Spot until the defined date.

   • Key fob expiration time — If this setting is in use, the system suggests a default offline expiration time for new Key Fobs.

   • Phone Key expiration time — If this setting is in use, the system suggests a default offline expiration time for new Phone Keys.

   • API access rights in use — If this setting is in use, access rights can be managed through an API. There are two types of access rights:

     • Standard access rights. These access rights are Programming Token encrypted. It is possible to add or remove standard access rights to/from a key or lock, through an API. However, programming requires the presence of a physical Programming Token, as the keys or locks are left in the In planning state if edited through the API.

       It is recommended to use standard access rights for access rights that open a large amount of locks, and/or when no API is used to manage access rights.

       Standard access rights provide a higher security level, as the user need a user ID, password and the Programming Token to program keys and locks.

     • API access rights. These access rights are database encrypted. Programming API access rights to/from a deployed key or lock does not require the presence of a physical Programming Token.

       It is recommended to use API access rights for access rights that open a limited amount of locks only, not for, for example, the master access right that can open all locks in the system.

       With API access rights, deployed keys and locks can be programmed with a user ID and password only, without the Programming Token.

4. Select Save and close.