• Log in to the Kuika platform.
• Open the project you want to work on from the Apps screen.
• Go to the UI Design module.
• Select the relevant screen or component.
• Open the Properties area in the right panel.

• From the + ADD ACTION menu, add the Authorisation > Is Logged action according to the trigger event you want (Initial Actions, OnClick, OnBlur, etc.).
• Click the SAVE button to complete the configuration.

‍

Ensure that only logged-in users can leave comments in the application. Users who are not logged in cannot see the comment form and are shown an informational message instead.

• Element: Comment Form component
• Trigger: Runs automatically when the page is loaded or when the comment form needs to be displayed.
• Action: Authorisation → Is Logged In

Process

If the user is logged in:

The comment form is displayed.The user's name, email address, and other information can be automatically populated in the form.The fields required to submit a comment (text box, submit button, etc.) become active.

1. If the user is not logged in:
   
   • The following message is displayed instead of the comment form:
   • ‘Please log in to post a comment.’
   • (Optional) A ‘Log In’ button or redirect link can be displayed immediately below.
   • When the user returns to the page after logging in, the form appears automatically.

This scenario is an example of using the Is Logged In action for content visibility control, other than page redirection. Unauthorised users are not redirected directly; they are informed and encouraged to log in. This approach allows redirection without interrupting the user experience, especially for public content.

‍

• Integrated Use with If Then Else: The Is Logged In result can be used as a condition. If the user is not logged in, they are redirected to another page.
• Dashboard Access: The management screen can be made visible only to logged-in users.
• Mobile User Control: A warning can be displayed or offline mode can be initiated for mobile users who are not logged in.

Technical Risks and Controls

• Independent Operation of the Action: Is Logged In only retrieves session information; a separate action is required for redirection or warnings.
• Security Vulnerability: Control mechanisms must be established to prevent users who are not logged in from accessing authorised pages.
• Misuse: This action only provides session control; it does not retrieve user data. If user details are required, Get User By ID should be used.

The Is Logged In action is a basic control for enhancing application security and managing the user experience. Flow design can be based on whether the user session is active, allowing you to create user-specific screens or redirection scenarios.

‍