Applications
Application > Portal. The list of applications this gateway offers, in the order you choose, and how it is offered. Each visitor sees only the entries their access allows.
It is a global setting, like the theme: one catalogue for the installation, edited here.

The three-state control
| What is drawn | |
|---|---|
| None | nothing. The user button and the built-in pages carry your brand's name, with nothing to click |
| Links | the list, in the user button's Applications submenu and on the data-plane pages |
| Portal | a navigation bar on every page of every application; the built-in pages then offer one way back in |
Changing mode does not cost the list. You can build a menu, promote it to a bar, come back: the entries stay.
What you do here
- Pick the mode. Nothing below shows in None.
- Add an application for each UI the list should offer. In Links they stack in a numbered list with two arrows for the order. In Portal they are built on the canvas, which is the real bar in edit mode: clicking an entry opens it in the drawer.
- Choose the arrangement (Portal mode): header mode or rail mode, which side the rail takes, whether header entries show the icon, the label or both, and whether the application name sits beside the logo.
- Check it narrow (Portal mode). The three width buttons put the preview in tablet and phone, to watch the overflow chevrons and the waffle launcher appear when the tabs no longer fit. In the rail layout, a container's modules fold into one button that names the module you are on and opens them as a menu - on a phone, or as soon as they do not fit on one line. Only full width is editable, and the width is never saved.
An entry
Add a module for an application, Add a container to group modules.
- Application (route) - a module's UI route. Only UI routes are offered, those turned off included, marked (turned off). The module inherits the route's access, and that is what makes the list differ per visitor: the payload carries no access rule. A container has no route.
- Label - required on a container; on a module, empty takes the route's name.
- Description - the tooltip.
- Icon (Portal mode) - search the embedded icon set, or give an SVG: paste it, drop its file, or choose the file.
A container opens its first sub-module the visitor may open, and is not shown to a visitor who may open none of them.
The quick actions at the top of the drawer move an entry up or down, disable it without removing it, or take it out. For a module, Move under puts it in a container or back at the top level: its list is the top level first, then the containers. On a container, + adds a module inside it.
Pitfalls
- A new UI route does not show up on its own. It is offered only if it is in this list: that is what replaces the route editor's old Link field.
- No UI route, no catalogue. An entry needs a route marked UI in Routes.
- A route turned off keeps its entry. The bar shows it in its place, greyed out and leading nowhere, until the route is back on; a container whose modules are all turned off is greyed out too. To take an entry out of the bar whatever its route does, disable the entry itself. A route deleted, or no longer UI, is skipped by the bar, and the list names it so the entry can be removed.
- A visitor sees fewer entries than you do, deliberately: the list is filtered by each entry's route access.
- The bar never shows in an iframe. A page embedded in another is not the place for a navigation bar.
- **Switching to Portal changes every UI route at once.** The per-route user buttons lose their Applications submenu to the bar.