What Is App Navigation?

App navigation is the persistent menu rendered on every page of your application. It is configured once and automatically applied everywhere — you do not add navigation blocks to individual pages. Navigation controls:

• Which pages, modules, external links, and utilities users can reach

• What page the app opens on (the default page)

• How the menu looks and behaves at different screen sizes

• Whether user profile, notifications, and language/theme controls are exposed

Note: Modules, copilot apps, walkthroughs, and template components do not have app navigation. Navigation applies only to standard web and mobile applications with pages.

Where to Configure Navigation

Navigation is configured in Settings → Development → Navigation. The settings panel has two tabs:

Content Tab: Menu Items

The Content tab has two lists: Menu Items (primary navigation) and Secondary Menu Items (web-only, shown separately — typically at the bottom of a sidebar or end of a top bar).

Primary Menu Items

Use the Add button on the primary list to add items. The following types are available:

Secondary Menu Items (Web Only)

Secondary items appear in a dedicated area of the navigation (for example, at the bottom of a sidebar). Available types:

Profile Menu

The Profile item expands into a user-contextual menu. Inside it, you can add:

• Page links — navigate to a profile or settings page

• URL links — open external resources

• Buttons — run custom interactions (for example, sign out via an action sequence)

• Change Language — lists all supported languages and lets the user switch

• Change Color Scheme — flips between light and dark mode

Note: If the app is configured as public (no authentication required), the user menu (Profile and Notifications) is automatically removed from the navigation. You cannot have a user menu on a fully public app.

Default Page

The Default Page section in the Content tab controls which page the app opens on. There are two slots:

For public apps (no authentication), the app always uses the main default page regardless of sign-in state.

Warning: If the page set as the default is deleted, the app is left pointing at nothing — it does not automatically reset to another page. After deleting any page, check whether it was the default and update the Default Page setting if necessary.

Conditional Defaults for Logged-In Users

The logged-in default page slot supports conditions. This lets different user roles or groups land on different pages when they open the app. Each condition is evaluated in order; the first matching condition determines the landing page. If no condition matches, the configured default page is used as the fallback.

Example — Role-based default page

Condition 1: {{ currentUser.role === "admin" }} → Admin Dashboard Condition 2: {{ currentUser.role === "manager" }} → Manager Overview Default (fallback): → Employee Home

Admins land on the Admin Dashboard, managers on the Manager Overview, and all other users on Employee Home.

Appearance Tab: Per-Breakpoint Layout

The Appearance tab lets you configure a different menu layout for each screen-size breakpoint. Each breakpoint is configured independently — the menu can look completely different on desktop vs mobile.

Breakpoints

Mobile applications use the SM breakpoint only.

Navigation Styles

Per-Breakpoint Appearance Settings

Item-Level Breakpoint Visibility

Each individual navigation item has its own breakpoint visibility toggles: Desktop, Tablet Horizontal, Tablet Vertical, Mobile. This is an allow-list system:

• If no toggles are changed, the item appears at every breakpoint.

• Once you enable at least one toggle, the item appears only at the selected breakpoints and is hidden at all others.

Mobile-Specific Behavior

Permission-Restricted Items

Navigation items can be restricted by role or permission. When a user does not have access to a restricted item:

• The item is silently removed from the menu — it does not appear as greyed out or locked.

• This behavior applies only in the published app. In the builder and preview, all items are shown regardless of permissions so you can design and test freely.

Quick Setup Guide

1. Open Navigation settings: Go to Settings → Development → Navigation.

2. Add primary menu items: On the Content tab, click Add in the primary list. Add a Nav Item for each page users should reach from the menu. Set the label and icon for each item.

3. Add secondary items (optional): Add a Profile item and/or Notifications item to the secondary list if your app supports user accounts. Configure the profile menu's sub-items including Change Language and Change Color Scheme as needed.

4. Set the default page: In the Default Page section, select the page the app should open on for logged-in users. Optionally configure conditions for role-based routing. If needed, set a separate default for logged-out users.

5. Configure appearance per breakpoint: Switch to the Appearance tab. For each breakpoint, set the navigation style, position, label behavior, and visual styling. Test the layout at each breakpoint using the builder's responsive preview.

6. Review in preview: Use the builder's preview mode and toggle between breakpoints to confirm the menu looks and behaves correctly before publishing.