Setting the display/access settings of the elements in the application according to user roles.
For example, let's create two users in the Admin and Staff roles. To create the roles, first click on an element in the application. From the Authorization field opened in the Properties panel, disable the All Roles Access Switch if it is active. Then click +NEW ROLE under the Roles heading.
Name it as Staff and click the CREATE button. This process is also done for the Administrator.
The created roles are saved in the KRole table in the Tables field in Datasources view mode. In the KUserRole table, you can view which role the users are in by writing SQL queries.
You can use Authorization system actions to invoke registered roles in UI Design view mode or to provide role authorization operations such as assigning user roles. For example, an Administrator is also in an employee role. You can remove one of the Administrator's roles with the OnClick→Authorization→Remove User From Role system action.
With the user roles created, it is possible to set which role can view which element for each element in the application.
For example, if Administrator is selected in the Authorization settings field for the Row in the application, a user in the Administrator role can view this Row, while a user in the Staff role cannot view this Row.
In the same situation, when only Personnel is selected, only users logged in with the Personnel role can see the row.
You can also make the Row only visible to the user in authorization processes. The user cannot make any changes on this Row.
In order to do this, you need to select which role you don't want to make changes on which element, and then select that role in that element and disable the Hide Switch.
You can select the start screen when the application is run according to the added role. For example, when the application is run, you can set the start screen that comes to the Administrator screen and the start screen that comes to the Staff screen differently.
The only thing you need to do is to select the screen you want the user to come as the start screen from the Selectbox and click the CREATE button.
You need to activate the All Roles Access Switch so that all elements can be viewed by the user with each role.
In order to view the elements in the application without the need for any role, the Anonymous Access Switch must be active.
Providing authorization across screens in an application development process is a critical step to ensure that users have the right level of access to the application and that their privacy is protected.
You can easily authorize the screens you create during the application development process from the Authorization field in the Properties panel. Thus, you can adjust the visibility of the screens according to the roles your users have.
For example, for users who are Admin and Staff, you can make the Department page viewable only for the user with the Admin role, while the user with the Staff role cannot view the Department page.
In order for these operations to take place, you need to create roles as in the Elements authorization operations. You need to select the screens and specify the roles within the screens.
In addition, when you Preview the application you have developed, you need to activate the All Roles Access Switch so that users who are logged in to the application and users with each role can view the screens.
This way, the user will need to enter their e-mail and password when they preview the app.
In order to view the screens without any login process and without any role requirement, the Anonymous Access Switch must be active.
Authorizing screens and elements in the application is that easy!