User Manual

Defining Authorization for Screens and Elements

30/7/25
Defining Authorization for Screens and Elements

Kuika offers flexible and secure authorization solutions in application development processes. Providing access control over screens and elements based on user roles ensures that the right users have access to the right data while increasing the security of your application.

SystemAdmin Role and Authorizations

The SystemAdmin role represents the user with the highest privileges on the application. This role has the following authorizations:

  • Access to all screens: Can view and edit all screens of the application.
  • Access to all elements: Can manage all components on the UI (buttons, input fields, tables, etc.).
  • User and role management: Create and delete user accounts and change their roles.
  • Access to data sources: Manage database tables and run SQL queries.
  • Change authorization settings: Specify user roles and edit authorization policies.
  • Manage application settings: Change general application configurations.
  • Control development and testing processes: Test how authorizations work in Preview mode of the application.

1. Authorization on Elements

In the Kuika platform, users can be associated with specific roles to limit their access to screens and elements.

1.1. Role Creation

  1. Log in to the Kuika platform and select your project from the Apps screen.
  2. In the UI Design module, add and select an element from the Elements panel.
  3. In the Authorization field in the Properties panel, disable the All Roles Access Switch option.
  4. Click the +NEW ROLE button under the Roles heading.
  1. Enter the role name and save it by clicking the CREATE button.
  2. The roles you created are stored in the KRole table in the Datasources module.
  3. You can write SQL queries over the KUserRole table to find out which role the users are in.

1.2. Element Authorization by Roles

  • To make an element viewable only by a specific role, add that role in the Authorization field.
  • If you want the element to be viewable only, disable the Hide Switch property.

1.3. Start Screen Assignment by Roles

  • To set the start screen depending on the user's role, select the role in the Select Box.
  • Complete the setting by clicking the CREATE button.
  • If all roles need to view the same elements, activate the All Roles Access Switch option.
  • You can use the Anonymous Access Switch option to provide access without requiring login.

2. Authorization on Screens

Screen-based authorization allows users to access only the screens assigned to specified roles.

2.1. Role Based Authorization on Screens

  1. Select the screen you want to authorize.
  1. Navigate to the Authorization field in the Properties panel.
  2. Add the relevant role so that the screen can only be viewed by a specific role.

2.2. Authorization in Preview Mode

  • When testing the application in Preview mode, enable the All Roles Access Switch option so that users can log in.
  • You can use the Anonymous Access Switch option so that users can view screens without logging in.

These authorizations increase the security and functionality of the application by ensuring that users only access areas appropriate to their role. TheSystemAdmin role is authorized to manage all these settings. With role-based access controls, your application's user experience and data security can be maximized.

Other Related Content

No items found.

Glossary

No items found.

Alt Başlıklar