Navigation

Your app's menu lists its collections. On a laptop that's a sidebar down the left. On a phone it's a menu behind the hamburger button, plus an optional tab bar along the bottom. The Navigation designer lets you choose which collections appear in each, and in what order, separately for each device.

Open it from Build → Navigation in the app admin.

The three lists

List	Where it shows	Notes
Sidebar	The left menu on a laptop or desktop	Everything you want reachable on a big screen
Bottom bar	Tabs along the bottom of a phone	Up to 5. Keep it to the things people use most
Menu	The list behind the hamburger button on a phone	Usually everything, including what didn't fit in the bottom bar

The designer has two tabs, Laptop and Phone. Laptop shows the sidebar list next to a laptop mockup. Phone shows the bottom bar and menu lists next to a phone mockup.

Arranging

• Drag a row by its handle to reorder it, or use the up and down arrows.
• Remove a collection from a list with the ✕ button. It stays in the app; it just isn't in that menu.
• Add a collection back with Add collection under the list.
• A collection can be in more than one list. The bottom bar shows n / 5 and stops accepting more when it's full.

The mockup updates as you arrange, before you save. Click Save to apply your changes to the app. The Live preview phone in the header shows the saved app, so save first, then look at it.

What still applies

The designer decides where things appear and in what order. It doesn't override who is allowed to see them:

• A person whose role has no View access to a collection never sees it, even if it's in a list.
• A collection's Show only if formula still hides it when it's false.

Each collection's display label, icon and Show only if rule are still edited in that collection's own settings (the edit button in the Schema Builder). Only placement and order live in the Navigation designer.

If you never open it

Nothing changes. Until you save a layout, the phone menu simply follows the sidebar, and the bottom bar shows the collections you'd marked for it, exactly as before.

In your schema

The arrangement is stored on each collection's nav settings, so it travels with the schema and comes along when an app is created from a template. See the nav property in the Schema Reference.