1. Log in to the Kuika platform.
2. Open your project from the Apps screen.
3. Go to the UI Design module.
4. Open the Properties section in the right panel.

5. Select the relevant component and add the Authorisation > Save Role Access action from the + ADD ACTION menu according to the desired trigger event (Initial Actions, OnClick, OnBlur, etc.).

Parameter Definitions

• Is Authorized (Boolean - Required): Specifies whether a role is granted or denied access permission. true → permission is granted, false → permission is denied.
• Role ID (String - Required): The unique ID number of the role to which access permission will be assigned in the system.
• Action ID (String - Required): The unique ID of the function or screen to which the role will be granted access.

Each parameter can be entered as a fixed value or linked to data from sources such as Action Result, Method Input, Screen Input, Current, and Component. These links can be easily configured using the Symbol Picker.

In an administration panel, only users with the analyst role are allowed to access the ‘Reports’ screen. The administrator uses the ‘Save Access’ button to grant the analyst role permission for this page.

Application Steps:

• Element: Save Access button
• Trigger: OnClick
• Action: Authorisation → Save Role Access

Parameter Assignments:

• Is Authorised → true
• Role ID → selectedRole.id
• Action ID → ‘reportScreenAccess’

When the administrator clicks the Save Access button, the analyst role is granted access to the ‘Reports’ page in the system. Users with this role can then only log in to this page.

• Dynamic Authorisation:
  
  • Role ID and Action ID values can be dynamically changed by selecting them from a list.
  • Multiple record updates can be made in a loop.
• Conditional Authorisation Records:
  
  • Access control can be provided with If Then Else based on a condition such as the user's role or user type.
• Bulk Permission Updates:
  
  • Access can be granted to the same role for multiple actions. For example, access permission can be defined for both the ‘Reports’ and ‘Statistics’ screens at the same time.

Technical Risks and Controls

• Invalid Role ID: If the role is not defined in the system, access rights cannot be defined.
• Missing Permission List: If the Action ID is entered incorrectly, the relevant screen or component will not be affected.
• Incorrect Authorisation: If the Is Authorised value is assigned incorrectly, the user may be granted unwanted access.
• Unauthorised Action Use: The user defining the action must be authorised.

Save Role Access is a powerful tool for enhancing application security and customising the user experience based on roles. It permanently stores role-specific access definitions in the system and lays the foundation for flexible authorisation structures. It is an indispensable action for access control, especially in enterprise applications.