Skip to main content

​
Navigation

Navigation is the route tree end users see: which destinations appear in the portal sidebar (or tabs), how they are grouped, and how breadcrumbs work on detail routes. You describe who should see which destinations; GenieForge configures the tree. Good navigation makes the product feel finished: people click where they need to go instead of only chatting.

​
Where it lives

Configure navigation in Build or the navigation UI your app uses. Align it with App Blueprint → Access and each page’s roles. Navigation is a route tree, not only a flat menu:
  • Groups organize sidebar items (optionally collapsible).
  • Dividers separate top-level sections.
  • Detail routes can stay out of the sidebar but still drive breadcrumbs when someone drills in (for example Clients → a specific client → Posts).
  • Breadcrumb links keep the right filters and IDs so going back lands on the same record.
  • Roles on navigation and on pages are both required. A nav item that a role can see but cannot open is hidden for that role. Hiding a nav item does not revoke page access by itself. A non-empty role list is exclusive: Owner and Admin must be named to see that item. "*" is every custom role and does not include them. Empty lists stay Owner/Admin only (nested empty items still inherit the parent).
  • The portal sidebar shows pages and forms. Views stay in the builder today (Preview can still open views from the builder nav).
  • Icons on nav items (and groups) are supported when GenieForge sets them.
A page that is still in this tree cannot be deleted until you remove that nav item.

​
How to verify

  1. Open navigation configuration for the app.
  2. Preview as each role: correct items, no staff destinations for clients.
  3. Open a detail record and confirm breadcrumbs keep filters and IDs.
  4. Confirm hiding a nav item did not accidentally leave page access open (check Access).

​
App chrome: drawer or tabs

By default the portal uses a drawer (hamburger sidebar) on phones. For a client-facing app shell (brand header + bottom tabs), open App Settings → Appearance → Portal chrome, choose Tabs (brand header + bottom tabs), and click Save portal chrome. In tabs mode:
  • The top bar shows your app name (and logo when set). Tapping the brand goes to the first sidebar page.
  • Bottom tabs come from every sidebar-visible page or form, including pages inside a group. Hidden detail routes and views stay out. When there are more than fit on screen, the bar scrolls horizontally and fades/chevrons show that more tabs are available.
  • Account tools that used to live on the sidebar (Notifications, Work, My Chats, My Files, My Memories, People, Activity, Billing, Usage) open from the brand header profile menu. The notification bell also sits in the header. Clicking the bell opens a dropdown: in-app rows follow their page, and emails open the message. View all still opens the full Notifications list. Items only appear when that role can use them. Work appears only after you grant that role access.
  • On phones, the AI chat control sits in the brand header next to Search (not as a floating button over the bottom tabs). Wider screens still use the slim chat strip on the right.
  • The same chrome applies to real end users and Preview as a role.
In drawer mode, those same account tools sit in a collapsed More section at the bottom of the sidebar, so the page list stays the focus. Profile and sign out stay visible under More. On phones, AI chat opens from the top bar next to Search.