Define authorization to a screen and elements

1. Authorization in Elements

It is the setting of the display/access settings of the elements in the application according to the user roles.

1.1. Role Creation

For example, let's create two users in the Admin and employee 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 an employee 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 provide role authorization operations such as calling the registered roles to UI Design view mode or assigning user roles with Authorization system actions. For example, an Administrator is also an employee role. You can remove one of the roles of the Administrator with 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 employee role cannot view this Row.

In the same situation, when only Personnel is selected, only users logged in with the Personnel role can view the Row.

In authorization processes, you can also make the Row only visible to the user. The user cannot make any changes on this Row.

In order to perform this operation, if you do not want which role to make changes on which element, you should select that role in that element and disable the Hide Switch.

1.2. Assigning Start Screen According to Roles

You can select the start screen when the application is run according to the added role. For example, when the application is run, the start screen that comes to the Administrator screen and the start screen that comes to the employee screen you can set the start screen differently.

The only thing you need to do is to select the screen you want the user to see 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 users with every role.

In order to view the elements in the application without the need for any role, the Anonymous Access Switch must be active.

2. Authorization on Screens:

Providing authorization on screens during 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 Administrator and employee, you can make the Department page visible only to the user with the Administrator role, while the user with the employee 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.

Thus, the user will need to enter their e-mail and password when they preview the application.

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!

Last updated