You can use Kuika’s Config Manager module to configure the settings that will be used during the creation of your app, as well as to preview, test, and publish the app. In this tutorial, you’ll learn how to configure the settings that will be used during the creation of your app using the Config Manager module.
Add Configuration to Your Application
To create a new configuration:
Log in to the Kuika platform.
Open the project you’ll be working on from the Apps screen.
Click the Config Manager module in the top menu.
Click the Create a blank configuration card.
Give the configuration a name and complete the creation process.
You’ve now added a new configuration to your app.
Anatomy of the Configuration Manager Module
When you navigate to the Config Manager module from the top menu on the Kuika platform, you’ll see the main screen where you can list your configurations and create new ones.
1. Configuration Creation Area
Create a blank configuration: Allows you to create a new, blank configuration for different environments such as test, staging, or production.
2. Filtering and Search Area
Recently modified: Lists the most recently modified configurations.
Project: Lists configurations created specifically for the currently open app.
Global: Lists configurations available across the entire workspace.
Search: Allows you to search for configurations by name.
3. Configuration List
Created configurations are listed with the following information:
Name: The name of the configuration.
Platforms: The platforms supported by the configuration (e.g., Web).
Scope: The scope of the configuration (Project or Global).
Status: The configuration’s status.
Last modified: The user who last edited the configuration and the time of the edit.
If no configuration has been added yet, the message No configurations have been added yet. appears in the list. To edit a configuration, simply click its name in the list.
Anatomy of the Configuration Screen
You need a configuration to preview and publish an app developed in Kuika. When you open a configuration, the configuration screen appears, consisting of the following sections.
Top Bar
Back arrow: Takes you back to the Config Manager main screen.
Name field: Displays the configuration’s name. You can change the name using the edit (pencil) icon next to it.
Tabs: Groups settings by platform: App Settings, Web, iOS, Android, and Desktop App. The iOS and Android tabs are displayed in mobile app projects.
Save: Saves the configuration settings. In an existing configuration, this button appears as Update.
Left Panel
Search settings: Allows you to search among settings (shortcut: ⌘F).
Settings menu: Lists the settings for the selected tab by category.
Middle Panel
Contains the fields for the setting selected from the left menu. In many settings, saved configurations are selected from the Choose Configuration dropdown menu; a new configuration is added using the Add New link below the menu. The number next to the link indicates the number of saved configurations.
Right Panel
In the App Settings tab: It contains the Description field, where you can add a note to the configuration, and the About field, which provides information about the selected setting.
In the Platform tabs: It contains the Platform field, where you can enable or disable platform support, as well as platform-specific options such as icons and splash screens.
Anatomy of App Settings Module
The App Settings tab contains settings common to your app across all platforms. The settings are grouped under the following categories in the left menu.
CONNECTIVITY
Connection Settings: Contains your app’s database and backend connection settings.
DB connection string: A string containing the information required to connect to your app’s database. It typically includes the server address, database name, username, and password.
Backend URL: The URL used to access your app’s backend services.
Backend URL settings accept “IP” and “Port” information.
File Upload Path: Specifies the directory on the server where uploaded files will be stored. For example, a path such as /upload/user_documents/ can be specified for uploaded documents.
SAP Service Base URL: This is the base URL your application uses to connect to SAP services.
Data Source Configurations: Allows you to configure the connection settings for the data sources used by your application.
Rate Limiting: Allows you to limit the number of requests that can be made to your application within a specific time period.
STORAGE & SEARCH
Document Management: Contains the document management settings for your application.
Full-Text Search Engine: Contains the search engine settings used to enable full-text search in your application.
Bucket Upload: Ensures that files uploaded by the application are stored in the cloud.
Name: The name assigned to the bucket.
Type: The cloud provider to be used (AWS or Google).
Encryption Key: The key used to encrypt files.
Encryption IV: The initialization vector (IV) used during encryption.
Cache Settings: Improves the application’s data performance by enabling data caching and fast access.
Name: The name assigned to the cache configuration.
Type: The type of data provider to be used:
Redis: A memory-based system that provides fast data access and caching.
Mongo: A NoSQL, document-based database. It is flexible and scalable.
SQL: A relational database; it offers powerful querying and a table structure.
Memory: Stores data in temporary memory; data is deleted when the application is closed.
Connection Settings: The server and authentication credentials the cache will connect to.
Search Service: Used for data search and management operations in your applications.
Name: The name assigned to the created configuration.
Base URL: The base URL used to establish a connection with the search service. It enables the application to send search queries and receive results via the Search Service API.
Vector Database Service Port: The port number used by the vector-based database service. It is used to perform similarity-based searches (e.g., text-based searches) on large and complex datasets.
Python Service Port: The port number used by the Python service that facilitates communication between the Search Service and the vector database. It enables operations such as adding sources and performing searches.
Storage Path: Specifies the directory where the Search Service’s data, indexes, and results are stored.
IDENTITY & ACCESS
Authentication & Authorization: Includes authentication and authorization settings.
Password Policy: Allows you to specify the password length, complexity, and change frequency. Incorrect login attempts on this screen are displayed as warning notifications; this alerts the user without interrupting the workflow.
Google: Enables users to sign in to your app using their Google accounts.
Facebook: Enables users to sign in to your app using their Facebook accounts.
MSAL: Enables authentication using Microsoft accounts.
OTP: A one-time password used in two-factor authentication processes.
2F Auth: When enabled, the authentication process becomes two-step. The first step is typically a password, while the second step is an OTP security code.
2 Auth Duration: This is the validity period of the OTP or security code, which constitutes the second step in the two-factor authentication process.
Expire Old Sessions Upon New Login: This is a security feature that automatically terminates old sessions associated with an account when a user logs in with the same account.
Authentication Cookies: Contains the cookie settings used in the authentication process.
INTEGRATIONS
Mail: Provides services for sending, receiving, and managing email. By configuring different email providers, you can set up a secure and manageable email infrastructure in your application. Supported providers:
SMTP: Enables sending via the standard email protocol.
AWS (Amazon Web Services SES): Enables sending via AWS Simple Email Service.
Exchange Server: Provides sending, receiving, and management services via a Microsoft Exchange server.
AI: Contains settings for the services to be used for artificial intelligence functions in your application. OpenAI, Azure OpenAI, Gemini, and Serper Tool configurations are defined in this section.
Payment Method: Contains payment methods.
Stripe: An international payment platform you can use for online payment transactions.
Iyzico: A Turkey-based payment platform that makes it easy to manage online payments.
Param: Offers various payment methods for e-commerce sites, mobile apps, and other digital platforms.
WhatsApp Business: Contains WhatsApp Business API integration information. The WhatsApp Business API is a service that enables businesses to communicate more efficiently with their customers. You can access the necessary information via the Meta for Developers (Facebook for Developers) platform.
For WhatsApp Business account and app information:
Create a WhatsApp Business account.
Create an app via Meta for Developers.
Open the WhatsApp Business setting in Config Manager and enter the following information using the Add New link:
Name: The descriptive name given to the configuration.
Account Id: The unique identifier for your WhatsApp Business account. It must be the same across all WhatsApp configurations.
App Id: The unique identifier of the app created via Meta for Developers; it is used to access the API.
App Secret: This is the secret key used to secure your app.
Access Token: This is the authentication token used to access the WhatsApp API. It can be obtained with or without an expiration date. If obtained with an expiration date, messages cannot be sent via the app created with Kuika once it expires.
Phone Number Id: This is the unique identifier of the phone number linked to your WhatsApp Business account.
Version Number: Specifies the version of the WhatsApp Business API being used. The default value is v21.0.
Sending messages and using templates:
A message template is created via the WhatsApp dashboard, and WhatsApp approval is obtained.
Template example:
Subject: Regarding the Status of Your Offer
Message: Congratulations! Your application has been approved. Please select one of the buttons below to indicate whether you accept or reject our offer.
Buttons: Accept, Reject
Approved templates are sent via the Send WhatsApp Business Message action on Kuika. For more information, please review our related content.
Template types: Parameters in WhatsApp message templates are selected when the template is created in Meta. These parameters are automatically imported into Kuika, where they can be configured to send messages.
Templates with buttons: Can only be used in steps with external assignments.
Templates without buttons: Can be used at any stage of the process.
Kuika currently supports only Quick Reply buttons. Other button types cannot be used.
Using Quick Reply:
Buttons used to advance the process must be of the Quick Reply (custom) type.
Each button must be paired with a mail interaction.
Invers CloudBoxx: Contains the necessary settings for the Invers CloudBoxx integration.
Google reCAPTCHA: Used to prevent activities such as spam and abuse.
Name: The name specified for the reCAPTCHA configuration.
Site Key: The public key that enables reCAPTCHA to work in your application.
Secret Key: The secret key used on the server side during reCAPTCHA verification processes.
MCP: Contains the settings for the MCP (Model Context Protocol) servers your application will use.
OPERATIONS
Swagger UI: Contains settings for the Swagger UI interface, where you can view and test your application’s APIs.
Elastic APM: Used to monitor the application’s runtime performance, transaction durations, and error and exception logs. With Elastic APM (Application Performance Monitoring) settings, operations within the application can be tracked on a per-service basis, performance bottlenecks can be analyzed, and monitoring can be segmented by environment (production, development, etc.). These settings become active when the application is set to Preview or Run, and by integrating with the Elastic APM Server, they enable the centralized collection of the application’s real-time performance data.
Notify Actions: Manages notifications and alerts in your application.
Name: The name assigned for the notification configuration.
Default Duration: Determines how long notifications will be displayed on the screen by default.
Success Duration: Specifies how long notifications displayed after successfully completed operations remain on the screen.
Info Duration: Specifies the duration of notifications displayed for informational purposes.
Warning Duration: Determines how long warning messages will be visible.
Error Duration: Specifies the duration for which error messages will be displayed.
Deeplink Setting: Contains the settings required to allow direct access (deep link) to a specific screen in your app.
Date & Time Formats: Determines the format in which date and time information is displayed in the app.
Date Format: Determines the date format. Example formats:
MM/DD/YYYY (07/09/2025)
DD-MM-YYYY (09-07-2025)
YYYY.MM.DD (2025.07.09)
Time Format: Allows you to choose whether the time is displayed in 24-hour or 12-hour (AM/PM) format. Example formats:
HH:MM (14:30)
HH:MM AM/PM (02:30 PM)
Configure Your Application Using the Platform Tabs
Configure Your Web Applications
Create a configuration in the Config Manager module or open an existing configuration.
Click the Web tab at the top.
In the Platform section of the right panel, make sure the Support Web UI option is enabled.
Configure the settings under the WEB APP heading in the left menu:
Host Settings: If the application’s frontend is hosted at a different location, you can enter the URL of the hosting server in the Frontend URL field. This field is optional.
Sessions: Allows you to set the session timeout duration for your application’s end users.
Maps: If your web app uses maps, you can configure the map settings and enter the necessary information for the map.
Push Notifications: Contains the settings required to use push notifications in your web app.
KuikAgents Integration: Contains the integration settings for your web app with KuikAgents.
Configure the following fields in the right panel:
Title: The title displayed in the browser tab for the app.
Meta Description: The description used in SEO and social media previews.
Favicon: The app icon displayed in the browser tab and bookmarks. You can upload a JPG, JPEG, PNG, or ICO file with a size of 32x32 px.
PWA Install: When the Enable installable PWA option is enabled, users can install the app on their devices as a Progressive Web App.
Click the Save button to save your settings.
Configure Your iOS Apps
Create a configuration or open an existing one in the Config Manager module.
Click the iOS tab at the top.
In the Platform section of the right panel, enable the Support iOS UI option.
Configure the settings in the left menu:
APP
Mobile App Settings: This is where you enter the app name (App Name), Bundle ID, and app version (Version) you’ll use in the Apple App Store. You can enable haptic feedback in the app using the Haptic Enabled option.
Apple Sign In Settings: Contains the settings required to allow users to sign in with Apple accounts in your app.
App Store Settings: Contains the settings required to connect your app to the App Store.
Firebase Settings: Allows you to integrate the services and features offered by the Firebase platform into your app.
DEVICE
Geolocation: You can define the location permission to be used in your app.
Camera: You can define the camera permission text to be displayed to end users.
Bluetooth: You can define the Bluetooth permission text to be displayed to end users.
GPS Tracker: You can configure the settings for the GPS tracking feature used in your app.
SERVICES
Push Notification: You can define the permission text to be displayed to end users for sending push notifications.
Google reCAPTCHA: Contains the reCAPTCHA settings to be used in your iOS app.
Edit the following fields in the right panel:
Options
Orientation: Sets the app’s screen orientation. The options “All orientations,” “Landscape,” and “Portrait” are available.
Devices: Specifies the device types on which the app will run. The options “All,” “Phones,” and “Tablets” are available.
App Icons: This is the app’s main icon image. You can upload a JPG or PNG file that is 32x32 px in size.
Splash
Image: This is the image that will be displayed when the app opens.
Fitting: Determines how the image used on the splash screen will be adjusted to fit the screen size. The “Default” and “Stretch” options are available.
Color: This is the background color to be used on the splash screen.
Click the Save button to save your settings.
Configure Your Android Apps
The Kuika platform has been made compatible with Android 16. Additionally, Android apps must now meet the 16 KB page size requirement.
Create a configuration or open an existing one in the Config Manager module.
Click the Android tab at the top.
In the Platform section of the right panel, enable the Support Android UI option.
Configure the settings in the left menu:
APP
Mobile App Settings: This is where you enter the information about the app you’ll use on the Google Play Store:
App Name: The name of the app.
Bundle ID: The app’s unique bundle ID.
Version: The app’s version number (e.g., 1.0.0).
App Version Code: The numerical version code that must be incremented with each new release.
Minimum Android Version: The lowest Android version supported by the app.
Use Cleartext Traffic: Determines whether the app allows unencrypted (HTTP) traffic.
Trust All Certificates: Determines whether the app trusts all SSL certificates.
Secure Screen Mode: When enabled, prevents screenshots from being taken and saved of the app’s screens.
Haptic Enabled: Enables haptic feedback in the app.
Play Store Settings: Contains the settings required to connect your app to the Play Store.
DEVICE
Geolocation: You can define the location permission to be used in your app.
Camera: You can define the camera permission text to be displayed to end users.
Bluetooth: You can define the Bluetooth permission text to be displayed to end users.
GPS Tracker: You can configure the settings for the GPS tracking feature used in your app.
SERVICES
Maps: If your Android app uses maps, you can configure the map settings and enter the necessary information.
Push Notification: You can define the permission text to be displayed to end users for sending push notifications.
Google reCAPTCHA: Contains the reCAPTCHA settings to be used in your Android app.
Edit the following fields in the right panel:
Options
Orientation: Determines the app’s screen orientation. The options “All orientations,” “Landscape,” and “Portrait” are available.
Devices: Determines the device types on which the app will run. The options “All,” “Phones,” and “Tablets” are available.
App Icons: Uploaded as a 32x32 px PNG file. You can define two icons: Square and Round.
Splash
Image: The image displayed when the app launches.
Fitting: Determines how the image used on the splash screen will be scaled to fit the screen size. The “Default” and “Stretch” options are available.
Color: This is the background color to be used on the splash screen.
Click the Save button to save your settings.
Configure Your Desktop Apps
Create a configuration or open an existing one in the Config Manager module.
Click the Desktop App tab at the top.
In the Platform section of the right panel, enable the Support Desktop App option. This option allows you to build cross-platform desktop applications for Windows, macOS, and Linux.
Configure the settings under the DESKTOP APP heading in the left menu:
Desktop App Settings: This is where you enter the application name (App Name), application ID (App ID, e.g., com.company.myapp), and version (Version) for your desktop application.
Target Platforms: This allows you to specify which operating systems the app will be compiled for. Windows, macOS, and Linux options are available.
Architectures: This allows you to specify the processor architecture on which the app will run. x64 (Intel/AMD 64-bit) and arm64 (ARM 64-bit) options are available.
Upload the main icon image to be used in your desktop application from the App Icon field in the right panel. It is recommended to upload an image that is 512x512 px in size and in PNG format. The uploaded icon is automatically converted to formats suitable for the target platforms.
