1. Define the Action in UI Design

• Log in to the Kuika platform.
• Open your project from the Apps screen.
• Go to the UI Design module.
• Select the button or item that will trigger the disabling process.

• Select the button and add the Authorisation > Disable User action from the + ADD ACTION menu according to the desired trigger event (Initial Actions, OnClick, OnBlur, etc.).

2. Configuring Disable User Parameters

• User Name (String- Required): The email address of the user to be disabled. It is usually defined using data sources such as Action Result, Current, Form Component, Screen Input or Fixed, and can be linked via the Symbol Picker.

In an admin panel, you want to temporarily disable access for a user who has performed inappropriate actions in the system. The user should not be completely deleted; only their system access should be restricted.

Applying the Disable User Action

• Element: ‘Disable User’ button
• Trigger: OnClick
• Action: Authorisation → Disable User
• User Name: Using Current.email as the user email address is more appropriate for securely and accurately obtaining the identity of the logged-in user.

After this process:

• The user cannot log back into the application.
• Current roles are disabled.
• The administrator can reactivate the user (e.g. with the Enable User action).

• Dynamic Data Source: Email information can be dynamically transferred by selecting the user from the list screen.
• Action Chain: A notification message can be displayed to the system administrator with a Notify action after the Disable User action.
• Logging: A record can be created to monitor user actions after the disable process (for example, by sending a log record to a data table).

Technical Risks and Precautions

• Disabling the Wrong User: Make sure that the User Name parameter points to the correct user.
• Planning for the Rollback Process: The processes for reactivating disabled users must be clear.
• Action Triggered by Unauthorised Users: This action should only be performed by authorised roles such as system administrators.
• Lack of Notification: If the disabled user is not notified, they may not realise that they have been locked out of the system. It is recommended to add a warning via a notification or email action.

The Disable User action provides a secure and effective method for temporarily restricting user access in Kuika applications. System user control can be maintained without permanently deleting the user. This action is particularly recommended for security, access violations, or temporary usage restrictions.