Object groups
A Group is a structure of your project for its easy management and one of the basic data that must be entered. A group can stand for a whole residential complex consisting of many houses, units, and apartments with thousands of users, or it can be a separate house or apartment, including one user.
For example, you can create a top-level group for a residential complex and assign an administrator who will install, configure, and monitor the entire system. Then, create subgroups for each building and assign a local manager (such as a concierge or security staff) to register new users (tenants), issue access identifiers, and monitor the system locally.
By creating groups and adding users you give them access to devices, restrictions, and all other possibilities of the group. For example, one house (group) might have an elevator controller, so users in this group can use elevator features, while another group might not have this option at all.
Create and manage groups: add new subgroups, assign previously added users and devices, configure licenses, restrictions, integrations, and more.
There are 2 options for creating a group:
Add a company — creates a top-level group suitable for small projects with a single building or unit;
Generate groups of objects — for quickly setting up complex hierarchies with multiple buildings, floors, and apartments.
If you are going to host several independent projects on one server, you must create a top-level group for each project (via Add a company) and then subgroups for houses, units, etc. It is important to provide correct permissions for user roles in Profiles.
How to add a top-level group
To start building your project structure, create a top-level group that will serve as the top-level group for managing users, devices, access rules, and integrations:
Go to User management → Object groups.
Click ADD OBJECT and select Add a company.
Enter a group name.
Select group type: building, unit, floor, apartment, or custom. It’s recommended to select custom for top-level groups.
Select SIP trunk from the previously created. It will work for this group for outgoing calls to mobile numbers. Users of this group will use the assigned trunk when calling mobile numbers.
Only one trunk can be assigned to a group. Different trunks may be assigned to subgroups.
Add a description, if necessary.
Select users from the previously added in the Users tab.
Users must be added before devices. Otherwise, the system won’t generate correct forwarding rules.
If you skip this step and add devices before adding a user to a group, a feature of automatic creation of forward rules will not work correctly. This is especially important for apartment groups and monitors. If you add a device to a group without a user, device virtual number applies to an administrator, but not to the group user. So, the created forwarding queue will include the administrator instead of the user.
8. Open the Licenses tab:
Enable Enable restrictions if you want to limit the number of licenses;
Click Add new license and select a type: Basic or Plus;
(Optional) Set validity period, enable reminders before expiration, and define notification frequency.
Open the Access Restrictions tab and create new or select existing restrictions to link users with devices and groups.
Open the Devices tab and select devices installed at this group location.
If applicable, open the Elevators tab and select elevator controllers.
In the Notifications tab, select users with the “Object Administrator” role who should receive email alerts.
In the Guest Access Limits tab, define max duration and quantity of guest passes issued by this group.
In the Whitelabel tab:
Enable Apple Wallet and configure guest pass appearance: QR text, colors, developer name, back info;
Enable Management company assignment if needed.
In the Mail Templates tab:
Click to create a new template;
Select the Mail type, then edit the subject and body. HTML is supported for formatting;
Use required markers such as
:email,:link,:token, etc., depending on the mail type.
For example, the:code_life_timemarker shows the validity period of the code — typically 7 days, automatically set by the system;Preview or send test mail, then Confirm.
The system marks mandatory fields — they turn red if not included.
Custom templates override the default system emails for that mail type.
To restore the default version, delete your custom template.
In the Integrations tab:
Click and select Integration type — Axxon One;
Enter integration name, server URL, port, login, and password;
(Optional) Upload a self-signed certificate;
Assign groups whose users can use this integration for devices;
Click 💾 Save icon in the lower-right corner.
The integration works by subscribing to macros (event rules) created in Axxon One.
After adding the integration, open the Devices tab and click the icon to add a new device. Select the Barrier type, model AXXONONE, choose a corresponding camera from the Axxon One server, assign the checkpoint direction (entry or exit), and link the macros used to trigger the barrier.
How to generate groups of objects
Use this option for bulk creation of groups and subgroups in complex projects:
Go to User management → Object groups.
Click ADD OBJECT and select Generate groups of objects.
Click to add a new group level. Specify: Type (building, unit, floor, apartment, or custom); Group name; Amount to generate; Starting number for enumeration.
Use next to a group to insert sublevels and define their settings the same way.
Expand advanced options if needed — click the ˅ icon to unfold the settings::
Enable Start numbering to define the Logical address for the group;
Add Exceptions to skip specific numbers.
Click GENERATE to preview results.
Switch to the RESULT tab and review the generated structure.
Click SAVE to confirm.
Add users, devices, and restrictions manually after generation.