Navigation

Every app has a sidebar navigation tree that you shape in the navigation editor: groups organize, pages link to the pages you've built. The tree is role-aware — each user sees only the items their roles allow, and the filtering happens on the server.

How the tree works

• Groups are containers: give one a label and an icon, and nest pages (or more groups) beneath it.
• Pages link to a page from the UI designer. Each item contributes a URL segment, and the full address composes down the chain — a group Sales (sales) containing Pipeline (pipeline) yields /sales/pipeline. A group can also have an empty segment when you want visual grouping without deeper URLs.
• Parameters — a page's segment can include a placeholder (like an order id), which the page's widgets receive and can filter by, enabling record-detail pages.

Editing navigation

Open Navigation in the app's admin area:

1. Add groups and pages, drag to reorder or re-nest.
2. Pick an icon and label for each item.
3. Set the item's audience: which roles can see it. App items also require the app's membership role automatically, so navigation for an app is only ever visible to that app's users.

Changes are captured into your update set and take effect immediately.

Who can edit

• Instance administrators manage all navigation.
• App managers manage their own app's items (platform items stay read-only for them).
• Everyone else simply sees their filtered tree — items they can't access are never sent to their browser.

Navigation item options and the underlying structure are covered in the UI builder reference.