App Configuration

Builder Settings Panel

The Builder Settings panel is accessed from within the Application Builder — typically via the gear icon or the Settings option in the builder's top bar. It is distinct from the Settings tab on the app's management screen in the Applications Manager, which governs access control and governance.

Note: Builder Settings vs the Settings tab: Builder Settings (inside the builder) controls the app's identity, design, code, integrations and security. The Settings tab in the Applications Manager controls who can access the app (Governance, Privacy Settings, Password Policy). Content Security Policy and Device Permissions appear in both places, under Security — see App Settings & Privacy.

The panel is searchable — type in the search field at the top to jump directly to any setting by name. Settings are organised into the following top-level sections:

General

The General section covers the app's core identity and visual brand assets.

Identity

Brand Assets

Brand assets are visual identifiers displayed in the app's navigation header, browser tab, and (for mobile) on device home screens and loading screens.

• Logo — Full-width wordmark or logotype shown in the app's primary navigation bar. Use an image with a transparent background. Size: 252×32 px. Accepts SVG, PNG, JPG or WEBP.

• Symbol — Icon-only version of the brand mark, used in compact navigation states (collapsed sidebar) or as a standalone icon. Size: 32×32 px. Accepts SVG, PNG, JPG or WEBP.

• Fav Icon — The icon displayed in the browser tab and bookmarks bar. Size: 16×16 px. Accepts PNG, SVG or ICO. Displayed small, so avoid complex detail.

Mobile apps have richer branding options including Android and iOS-specific assets (launcher icons, adaptive icon layers, notification icon and colour), configured in General → Brand Assets — mobile apps show extra fields there.

Splash Screen (Mobile)

The splash screen is the loading screen displayed while a mobile app initialises. You can configure:

• Light logo — Logo to display when the system is in light mode.

• Dark logo — Logo to display when the system is in dark mode.

• Background colour — The solid background fill behind the logo.

• Image fit — How the logo image is scaled within the splash screen bounds (contain, cover, fill, etc.).

Design System

The Design System section controls the visual language applied across all components in the app.

• Theme — Pick a base theme. Themes define a complete set of colour tokens, typography scales, and border-radius presets. The same theme picker available at app creation is accessible here, with the same filter options (All / Light / Dark / Both / Recent / Presets).

• Colors — Override individual colour tokens from the selected theme — primary, secondary, surface, background, error, warning, success, and semantic variants.

• Typography — Set font family, weights, and size scale for headings, body text, labels, and captions.

• Border Styles — Configure default border radius and border width used by components such as cards, inputs, and buttons.

• Custom Icons — Upload SVG icon sets to make them available in the icon picker throughout the builder. Custom icons are scoped to the app.

Development

The Development section contains settings that control navigation, the Copilot launcher and custom scripting. For mobile apps in developer mode, it also shows App Build Config (Developer Only).

Navigation

Configure the app's navigation menu — the primary sidebar or top-bar menu that links to pages within the app.

• Content — Add, remove, reorder, and nest menu items. Each item links to a page, an external URL, or a custom action.

• Appearance — Choose the navigation style (sidebar, top bar, or bottom bar for mobile), set icon display options, and control header/footer slots.

Launcher (Copilot Apps)

For Copilot app types, the Launcher subsection controls the floating chat button that appears on the host page where the Copilot is embedded.

• Text — Label displayed on or beside the launcher button.

• Icon — The icon or avatar shown on the launcher button.

• Position — Where on the host page the launcher appears (bottom-right, bottom-left, etc.).

• Events — Actions triggered when the launcher is opened, closed, or first rendered.

Custom Code

Inject arbitrary HTML or JavaScript into the app's document.

• Head Code — Injected into the <head> of the rendered page. Use for third-party analytics scripts, meta tags, font preloads, or CSS custom properties.

• Footer Code — Injected just before the closing </body> tag. Use for deferred scripts, chat widgets, or initialisation code that must run after the DOM is ready.

Web apps also have an HTML Attributes group in this panel for adding attributes to the app's container element. On mobile apps, custom code support may be limited to the web-view layer — verify compatibility with your target mobile platform.

Advanced Settings

The Advanced Settings section holds app variants, analytics, realtime events, location tracking, file management and the developer-only panels.

App Variants (Mobile)

For mobile apps, you can define named variants of the app — for example, a Primary consumer-facing variant and a Secondary internal-tools variant built from the same application record but distributed separately. Variants can have different build configurations, icons, and splash screens.

Analytics

• Enable Analytics — Toggle to start collecting page view, component interaction, and session data. Required for the Insights tab to appear in the Applications Manager.

• Custom events — Define named custom events that your page actions can fire. Custom events appear in the Insights dashboard alongside automatically collected events, allowing you to track app-specific interactions (e.g., "Form Submitted", "Report Exported").

Realtime Events

Enable real-time data synchronisation across all active sessions of the app using named topics. When one user's action triggers a topic event, all other users with the app open receive the update without needing to refresh.

• Define topic names and the payload shape for each topic.

• Wire topics to actions and component bindings in the builder.

Note: Realtime Events is not available for module app types.

File Management

Initial file visibility — Set the default visibility applied to files uploaded through file-upload components. The default is Restricted. Options:

• Only me — Accessible to the uploading user only.

• Only this app — Accessible to users of this app.

• Restricted — Accessible to all authenticated users.

• Public — Accessible to anyone.

Note: Setting the default visibility to Public means uploaded files are readable by anyone with the file URL — including people outside your organisation. Choose this setting carefully and only when the uploaded content is intentionally public.

Location Tracking

Enable the browser or device location API for this app. When enabled, page actions and components can request the user's current coordinates. Users are prompted for permission by the browser or OS before any location data is accessed.

Developer Panels (Dev Mode Only)

Two additional subsections appear only when the builder is in developer mode:

• Theme (Developer only) — Exposes low-level design token overrides not available in the standard Design System UI.

• Developer Options — Debug and diagnostic settings, including verbose logging and experimental feature flags.

Security

The Security section is available for apps (not modules).

Content Security Policy

Restrict what this app may load from elsewhere, and who may embed it. Turn on Enable Content Security Policy, then add URLs under:

• Allowed sources — the sites this app may load content from. With no sources, the app can only load from itself.

• Who can embed this app — the sites allowed to embed this app. With no sites, nobody can embed it.

Without a policy, the app can load from anywhere and be embedded by anyone. The same policy is also shown in the app's Settings tab → Security → Content Security Policy, where the two lists are labelled Resource Control and Frame-ancestors. See App Settings & Privacy.

Device Permissions

Choose what this app, and the sites it embeds, may use in a web browser — such as the camera, microphone and location. Mobile app builds ask the device for permission instead and ignore this setting.

Mobile

The Mobile section is available for mobile apps only and holds Secure View Mode. Turn on Enable Protection to block screenshots and screen recordings: a privacy screen appears when users try to capture the screen or switch apps. It applies to every page of the app. For the privacy-screen options and platform differences, see Mobile Security.

Apps & Integrations

Connect the app to third-party services and embedded assistants. Each integration is toggled independently; enabling one does not affect others.

Yellow.ai Configuration

Yellow.ai embeds a Yellow.ai chatbot in your mobile app. Open Settings → Apps & Integrations → Yellow.ai, turn on Enable Yellow.ai, and paste your Bot ID from the Yellow.ai dashboard. Optionally set a Bot name, a Bot icon, and User context — key–value pairs, bound to the signed-in user, that the bot receives when the chat opens. The builder saves your changes automatically; publish the app to apply them.

Turning Yellow.ai on doesn't add a chat launcher. Add the Control Yellow.ai action to a button or another interaction to open or close the chat. For the full setup and the action's options, see Control Yellow.ai Action.