1. Log in to the Kuika platform.
2. Select your project from the Apps screen.
3. Go to the UI Design module.
4. Open the relevant user settings or security screen.
5. Create an element (e.g. Select Box) that will allow the user to select the 2FA type.

6. Click the + ADD ACTION button in the Properties panel.
7. Select the Select Box element and add the Authorisation > Change Two Factor Authentication Type action from the + ADD ACTION menu according to the desired trigger event (Initial Actions, OnClick, OnBlur, etc.).

Configuring Action Parameters

• Authentication Type (Int32-One): The authentication method the user wants to switch to. Accepted values: ‘sms’, ‘email’, ‘authenticator’, etc., which are types defined in the system.
  
  • The parameter value can be dynamically retrieved from sources such as Action Result, Current, Screen Input, Fixed, Component, and linked via the Symbol Picker.

A user wants to change the default SMS authentication method in the account settings screen to the Authenticator app, which they consider more secure.

1. In the UI Design module, create an area titled ‘Change Authentication Method’.
2. Add a Select Box element (example: ddl2FAType) → options: SMS, Email, Authenticator.

3. Create a button: ‘Update Verification Method’.
4. Add an action to this button:
   
   • ADD ACTION → OnClick → Authorisation → Change Two Factor Authentication Type
5. Configure the parameters:
   
   • Authentication Type: Links to the value selected from the Content Menu

• Dynamic Method Determination: The recommended authentication type can be pre-selected based on the user's system history or security level.
• Conditional Action Chains: The user can be notified after the authentication type is changed (e.g., by adding a Notify action to display ‘Authentication method successfully updated’).
• Registration Confirmation: Registration confirmation processes can be provided with the confirmation feature of the relevant action; for conditional processes, different scenarios can be defined using the If Then Else action.

Technical Risks and Precautions

• Invalid Method Definition: Only authentication methods defined in the system should be entered in the Authentication Type field. Otherwise, an error may occur.
• Unauthorised Use: This action should only be available to the logged-in user or authorised administrators.
• Method Incompatibility: For authentication applications used in mobile applications, device support should be checked.
• Data Consistency: After changing the 2FA type, it should be synchronised with the system login logic and tested.

The Change Two Factor Authentication Type action is used to enhance security and provide users with more control in Kuika applications. Users can switch to their preferred two-factor authentication method to access the application more securely. With flexible configuration, web/mobile compatibility, and strong integration capabilities, it adapts to modern security needs.