Users and Roles | Systembaker

Security Steps - Define User Rights

Users typically access the system through their username and password. However, what a user can see and do depends on the role they belong to.

Systembaker allows for managing highly complex access rights for users (ACL) based on defined roles.

For example, in the notification system, a user in the role of a notifier sees the form for sending notifications and only has access to their own notifications. A user responsible for managing notifications, on the other hand, sees all notifications assigned to them for resolution and can change their status. The company executive sees all notifications.

Systembaker enables the management of comprehensive user access control to user-defined features and datasets.
Systembaker allows dynamically creating user rights to different parts of the system, even at the level of individual records in the data.
In the example above, in the table of all notifications, a user processing notifications sees only those assigned to them, but a user with the role of an executive in the same table sees all notifications.
Rights can be assigned to trigger processes and display screens.
When setting rights, it's possible to use the concept of inheritance from individual roles.
For example, the role "administrative worker" can have a sub-role "intern". The sub-role automatically inherits all rights assigned to the "administrative worker" role, and then specific permissions can be manually removed without affecting the parent role.
Therefore, it is possible to finely adjust what a specific role can and cannot see, what operations it can perform, which screens, buttons will be displayed to that role, which processes it can trigger, etc.