Page History
...
Table navigation is commonly provided as row actions, placed in the last column. It typically routes users to a drilldown page (for example, a details view), representing vertical navigation to the next layer in the breadcrumb structure. The destination screen should provide a clear “Back” option to return to the prior context.
Table navigation is commonly provided as part of row actions, placed in the last column. It typically routes users to a drilldown page (for example, a details view). This represents vertical navigation to the next layer in the breadcrumb structure.
The destination screen should provide a clear “Back” option. Users should be able to return to the table with minimal loss of context (for example, preserving filters or selection where feasible).
Buttons and Links
Navigation can happen through buttons or links placed within Buttons and links inside the dashboard content , often to support process flows. They are commonly used for horizontal navigation through a sequence of steps. Typical examples include , such as “Next” and “Back.”
These actions usually appear in toolbars, footer bars, or at the bottom of the content and should be used . Use them sparingly to avoid clutter and conflicting navigation paths.
...
Dialog navigation is usually implemented through footer bar actions. It typically includes two directions:
- An option to return to the current page (“Back” or cancel/close).
- An option to move forward by initiating a process or confirming an action (for example, accept, submit, or continue), which often leads to a new page.
Depending on the action performed, dialog -based navigation can represent vertical navigation (to a deeper level) or horizontal navigation (to the next step in a flow).
Best Practices
Balance
...
flexibility with predictability
Local Navigation should reflect the user’s current dashboard, task, and information architecture. Avoid reusing navigation structures that don’t match the local workflow, and keep the available Keep options relevant to what users can do from this area., and avoid exposing unrelated destinations.
Variation is expected across dashboards. Within While Local Navigation can vary between dashboards, patterns should remain consistent within the same application area, however, behavior should stay predictable. Use the same consistent placement, interaction modelmodels, and naming conventions so users can predict how navigation worksbuild reliable habits.
Keep
...
structures easy to scan
Prefer clear groupings over long flat lists, and avoid . Avoid deep trees, especially when they require repeated expand/collapse to reach common destinations. If a structure navigation becomes hard to scan, add groupingreduce nesting, shorten labels, and consider adding shortcuts or introduce search and shortcuts instead of adding more nesting.
...
Choose the right surface
...
Use a Navigation Boardlet for persistent cross-section navigation within when users need persistent navigation across sections of an area. Use breadcrumbs primarily for orientation and moving up a hierarchy. Use in-content navigation actions for step-based flows or and drilldowns where users need to act and then move forward.
Navigation inside
...
a process
Local Navigation should not route users Do not navigate users directly into the middle of a process or conditional content. Local navigation should route Link to a process entry points or overviews. Steppoint or overview instead, and let step-to-step movement belongs happen inside the process UI (for example, Next/Back actions).
Drilldown destinations should include a reliable “Back” option or a clear breadcrumb path. Dialog-based navigation should always include an explicit way to return to the current page without progressing.
...
clear path back. Breadcrumbs, a visible “Back” action, or both can work, as long as the behavior is consistent.
Always communicate “where I am” and “what will happen next.” Highlight the current destination in the boardlet. If a group is collapsible, its expanded/collapsed state should be clearly visible.
Language and labeling
Use user-facing language, keep titles concise, and match labels . Keep labels concise and aligned with page titles. Avoid , and avoid internal jargon, and ensure similar destinations . Similar destinations must have distinguishable names.
If local navigation can link to external destinations, label them clearly so users understand they are leaving the current context.
