This section describes how to fetch audit trails from networked locks on iLOQ Manager.
Proceed as follows.
Did this article solve your problem?
Give feedback & see related articlesThis section describes how to fetch audit trails from networked locks on iLOQ Manager.
Proceed as follows.
Did this article solve your problem?
Give feedback & see related articlesThis section describes how to browse the locking system event log on iLOQ Manager.
Proceed as follows.
Did this article solve your problem?
Give feedback & see related articlesThis section provides an introduction to estates.
Large locking systems may contain several sub-estates with hundreds, even thousands of locks and keys; for example, a housing co-operative that rents its apartments may own apartments in many different buildings and locations. In cases like these, finding the desired information from a large amount of rows in the user interface, and handling that data, may be difficult. Estates provide a way of organizing information into smaller entities that are easier to handle in the user interface.
Furthermore, estates provide the benefit that you can use access rights of the same name, and the same lock placement numbers, in different estates. If your locking system must cover, for example, two or more separate but similar buildings, use estates.
Estate-specific objects are:
From the perspective of iLOQ Manager, estates are filters that, when applied, only show locking data related to a particular estate.
In large locking system implementations, you may have dozens of buildings. In these cases, it is often a good idea to organise the estates as tree structures. When you select an estate on a particular level on a tree branch, you see:
On the other hand, you cannot see:
The figure below illustrates the estate tree visibility. In the first figure, Main St 1A is selected, in the second, Main St 1. The visible estate content are shown in blue in the figures. The invisible estate content are shown in grey in the figures.
You cannot prevent users from seeing estate content on iLOQ Manager, by using estates. As estates are used as filters, all users can see all estates and their contents. To hide content, you can use zones.
You do not have to re-program anything, when you start using estates.
Did this article solve your problem?
Give feedback & see related articlesThis section describes how to enable estates on iLOQ Manager.
Proceed as follows.
Did this article solve your problem?
Give feedback & see related articlesThis section describes how to add estates to iLOQ Locking System.
Proceed as follows.
Did this article solve your problem?
Give feedback & see related articlesThis section describes how to edit the estate structure on iLOQ Manager.
Proceed as follows.
Did this article solve your problem?
Give feedback & see related articlesThis section describes how to move data to an estate on iLOQ Manager.
If you have created the estate structure as part of the overall system deployment procedure, you do not necessarily have to move data to estates. However, if you add estates to an existing locking system, you can move existing data to the estates.
Proceed as follows.
Did this article solve your problem?
Give feedback & see related articlesThis section describes how to filter information according to an estate on iLOQ Manager.
You can select the desired estate to filter out unnecessary data from other estates.
Proceed as follows.
Did this article solve your problem?
Give feedback & see related articlesThis section describes how to delete estates from iLOQ Locking System.
You cannot delete an object until you first remove all the connections that the object has (for example, you cannot delete a person with keys until you first remove the keys from that person).
Deleting an object does not delete events related to it, from the event log.
Proceed as follows.
Did this article solve your problem?
Give feedback & see related articlesThis section provides an introduction to zones.
Zones are an easy way to prevent users from viewing and editing objects on different zones on iLOQ Manager.
You can restrict access to the object types below:
If you want, for example, to allow a user to create any kind of key, excluding a key having the system master access right, you can add the access right to a zone of its own, and not assign this zone to the user. Now, the user cannot see the master access right. Thus, the user cannot add it to or remove it from a key.
You do not have to re-program anything, when you start using zones.
Did this article solve your problem?
Give feedback & see related articles