If your company is growing 📈, that's wonderful, we're only happy about that. But with growth comes the need to delegate responsibilities to new employees. In small organizations, there is no need to segment access; everyone does everything and everyone knows everything. As the company grows, it becomes necessary to restrict employees from information they don't need. Furthermore, if you have a multi-branch network, the same employee in different branches can perform different functions, roles, or even positions. This makes it necessary to approach the formation of access rights to application sections extremely flexibly.

If circumstances change, you can easily remove access rights completely or partially. Moreover, if you need to, you can regulate access rights at the level of each group, list, or project. By going into the employee's profile, you can see all the access rights that have been delegated to them 👨🏫.

Example 🤦‍♂️

An employee should have the ability to receive information about the groups they work with in one branch. At the same time, this same employee can act as an administrator in another branch. Therefore, in the first branch, they act as a teacher (trainer) who only has access to the current information of the branch and only to the groups they lead. In the second branch, as an administrator, they have additional access to financial information, etc. Configurable permissions allow you to create a mosaic picture of access rights to various entities in the system. For more details, see the guide on teams and permissions.

P.s. 🧩🏆

Configurable access rights are necessary to implement a mosaic system of individual rights for each employee.