Why access restriction is required?
Access restrictions are required to allow users to interact with devices — for example, opening a door with a card or accessing a building with a license plate.
Even if the user and device are both added and licensed, no access will work without a rule.
What do access restrictions connect?
User or user group — who is trying to access;
Device — which door, gate, or panel;
Schedule — when access is allowed (optional);
Optional Identifier type — how access is granted, for example by card, UKEY, PIN code, or license plate; if none is selected, all linked identifiers will work by default.
Where to create them:
Go to Access management → Access restrictions in the web interface.
Each rule can include one or more of the following:
Access points — devices that the rule controls
Schedules — time frames for access
Users — specific people or groups the rule applies to
Identifiers — specific QR codes, cards, PINs, etc.
Objects — building sections or logical zones (optional)
You can combine these elements as needed. For example, a rule may apply to a group of users, a single identifier, or all residents of a building.
These combinations help solve real-life scenarios. For example:
Assign a rule to a user with working-hour limits to control cleaning staff access;
Apply a rule to a license plate without linking a user — for deliveries or contractors;
Add both user and identifier to restrict access to one person with one QR code;
Use objects to extend the same rule across all entrances to a specific zone.
🔹 Basic setup to make it work:
To quickly allow access:
Add a rule with no schedule or time limits.
Select a group — this is the simplest and most reliable way to grant access
If you skip this step or assign access only to individual users, they may not see devices in the app, and the system won’t send identifiers to those devices.
Choose the target device.
Save the rule.
👉 That’s it — the user will now be able to access the device using their identifier.