SmartIntego settings: Difference between revisions
Jump to navigation
Jump to search
Telcredstaff (talk | contribs) (Created page with " If the privilege has been defined with this type, the credential ID will be stored in the lock's own whitelist. In contrast, for privileges of type ''Regular'', it is the co...") |
Telcredstaff (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
There are a few settings that are necessary in order for locks from SimonsVoss SmartIntego to work correctly. |
|||
First, it is necessary to define whether the card ID is Mifare UID or data stored in the card memory itself. This setting is done in the Organization Owner view and must match the programming of the SmartIntego locks (done with the SmartIntego software from SimonsVoss). |
|||
[[File:smartintego-settings|SmartIntego settings]] |
|||
Revision as of 17:48, 4 November 2021
There are a few settings that are necessary in order for locks from SimonsVoss SmartIntego to work correctly.
First, it is necessary to define whether the card ID is Mifare UID or data stored in the card memory itself. This setting is done in the Organization Owner view and must match the programming of the SmartIntego locks (done with the SmartIntego software from SimonsVoss).
If the privilege has been defined with this type, the credential ID will be stored in the lock's own whitelist. In contrast, for privileges of type Regular, it is the controller that makes the access control decision.