How to configure access rights for separate projects?
When hosting multiple projects on a single server, it's important to separate data and limit visibility so that administrators can only access information relevant to their own project. To achieve this, each project should be assigned its own visibility zone.
By configuring the server this way, administrators are added to the top level of their project hierarchy. This ensures they can only manage their assigned groups, users, and devices, without accessing data from other projects.
This approach keeps data secure, reduces management complexity, and gives each administrator a clear view of their own project resources.
Configuring access rights for separate projects
If you need to separate users and resources across multiple entities such as buildings or departments, you can isolate each project on the same server using dedicated groups and role-based profiles. This ensures secure access and clear responsibility boundaries between administrators, concierges, and users.
Creating groups
Create the required number of groups on the server that you will interact with. For example, Project A and Project B, as shown in the screenshot below.
Navigate to Object groups.
Click Add Group and create a new group for each project.
Repeat this for as many projects as needed.
View your project groups in the Object Groups list once they are created.
Adding users with roles for projects
Once you have created the groups for your projects, add users with the required roles.
Go to the Users section.
Click the ➕ icon in the lower-right corner to create new users.
Assign appropriate roles: Administrator, Concierge, or User.
Apply the correct role profile to each user.
While configuring the Root Group Administrator, specify which roles they can manage in the Available profiles section. For example, Concierge and User.
Discover how to create users and assign roles to manage access more efficiently.
After you create users with assigned roles for the first project, those users will automatically appear in the Users section.
Assigning users to projects
Assign roles to the groups within your project to make each role responsible for its designated area.
Let’s assign each role step-by-step within the project structure:
Adding an Administrator
Go to the Object Groups section.
Select the top-level group with users and roles you created earlier.
Expand the group, click the ••• next to its name, and select Edit to open the group settings. This gives the Administrator full control over all subgroups.
In the edit window, go to the Users tab.
Click the
icon and select the Administrator.
After selecting the user, click the green Confirm button in the lower-right corner.
Click Confirm, then click the
Save icon in the lower-right corner.
Adding a Concierge
Refer to your earlier experience adding the Administrator — the steps for the Concierge are similar, but you will assign them to a different subgroup.
Go to the Object Groups section and click the ▶ to the left of the subgroup name: Building → Unit.
Click the ••• next to the desired group and select Edit.
In the edit window, go to the Users tab.
Click the
, select the Concierge, and click Confirm.
Click the
Save icon in the lower-right corner.
Adding a User
The process of adding a user is similar to adding a concierge, except the user should be assigned to their apartment at a lower level of the hierarchy.
Go to the Object Groups section and expand the hierarchy: Floor → Apartment.
Click the ••• next to the apartment group and select Edit.
In the Users tab, click the
, select the user, and click Confirm.
Click the
Save icon in the lower-right corner to complete.
Once all users with their roles have been added, their permissions will be restricted to the assigned project. Administrators can only manage users and devices within their assigned project.
Setting up additional projects
Repeat the same setup for any other project:
create new groups;
add new users;
asssign roles and place them correctly within the hierarchy.
This ensures each project remains isolated and invisible to users from other projects.