Matrix - LSM 3.5 SP3 Basic Online
This view forms a matrix which provides a visual display of hierarchical personnel and room structures. The matrix is also able to authorise transponder groups for complete areas. This makes it quick and easy to issue basic authorisations in the Areas/Transponder groups view. The Doors/Persons view allows you to issue deviating authorisations in the form of individual extensions or restrictions.
Doors/Persons view
| Authorisation which has been configured, but not programmed into the locking device yet. |
| Authorisation which has been programmed into the locking device. |
| Authorisation which has been removed but not transmitted to the locking device yet. |
| Yet to be programmed authorisations which are compliant with the locking system's group structure, i.e. they are from the group view, are marked with a small, black triangle. |
| Programmed authorisations which are compliant with the locking system's group structure, i.e. they are from the group view, are marked with a small, black triangle. |
| Withdrawn authorisations which are compliant with the locking system's group structure and have not been programmed yet. |
| Authorisations which are not compliant with the locking system's group structure are indicated by a cross only and do not feature a black triangle (individual authorisation). |
| Authorisations which have been withdrawn from the locking system's group structure at a later date feature the black triangle, but no longer feature an authorisation cross. |
| Chequered (greyed-out) box: No authorisations can be configured. They do not feature any write accesses or the locking plan blocks this box (e.g. for deactivated transponders or G2 cards at the active cylinder). |
Areas view/Transponder groups
| A black cross with a circle inside indicates a group authorisation. |
| A grey cross with a circle inside indicates an "inherited" authorisation. |
Group authorisation tree view
| Set manually (black) |
| Direct inheritance (green) |
| Indirect inheritance – inherited from child group (blue) |
| Both direct and indirect inheritance (blue/green) |
Programming requirement
A programming requirement may arise for a transponder or a locking device for different reasons. The programming flashes are shown in different colours to represent the different reasons for a programming requirement.
| Programming requirement for the component (yellow) |
|
|
| Programming requirement for a locking device after creating a replacement transponder in G1 system overlay mode |
- You can double-click on a component in the matrix to switch directly to the component's properties.