---
id: CON-PFM-CSH-002
name: Navigation
feature: FEAT-PFM-CSH-02
product_area: platform
module: console-shell
revision: 2
status: draft
product_intent: proposed
implementation_evidence: observed
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
definition: >-
  Navigation organizes the destinations a console user can reach. It brings applications, shared
  tools, settings and customer-defined record types into a visible map of work.
owned_by: MOD-PFM-CSH
synonyms:
  - console menu
  - navigation menu
not_to_be_confused_with:
  - Authority to read or change data
  - Search results for records and pages
  - The metadata records that define custom applications
facets:
  - name: Application section
    meaning: A group presents destinations associated with one application.
    used_for: Organizing daily work by product area.
  - name: Menu item
    meaning: A named destination carries the information needed to display and select it.
    used_for: Offering a recognizable route to a task.
  - name: Tools and application links
    meaning: Shared tools and related services appear alongside application work.
    used_for: Reaching tasks that cross application boundaries.
  - name: Settings area
    meaning: Administrative destinations have a distinct navigation context.
    used_for: Keeping workspace administration understandable.
  - name: Rhythm HQ links
    meaning: Staff destinations represent work carried out for Rhythm.
    used_for: Separating Rhythm operations from customer work.
  - name: Custom placements
    meaning: Customer-defined record types extend the navigation in chosen groups.
    used_for: Placing an organization’s own work in familiar surroundings.
  - name: Menu filter
    meaning: A text filter helps locate destinations in a long menu.
    used_for: Reducing the effort of scanning many entries.
  - name: Active place
    meaning: The current address supplies the position represented in the menu.
    used_for: Helping the person understand where they are.
relationships:
  - to: CON-PFM-CSH-001
    statement: The shared frame supplies the space in which navigation appears.
    provenance: observed
    source: 'react-console:components/console/app-sidebar.tsx:AppSidebar'
  - to: CON-PFM-CSH-003
    statement: Console destinations and address matching connect selection with the current page.
    provenance: observed
    source: 'react-console:components/console/nav-config.ts:findNav'
  - to: CON-PFM-CSH-004
    statement: The enabled application list helps determine the sections offered to a person.
    provenance: observed
    source: 'react-console:lib/console/use-visible-nav.ts:visibleSections'
acted_on_by:
  - CAP-PFM-CSH-006
  - CAP-PFM-CSH-007
  - CAP-PFM-CSH-008
  - CAP-PFM-CSH-013
  - CAP-PFM-CSH-014
  - CAP-PFM-CSH-016
visible_to:
  - ACT-PFM-001
  - ACT-PFM-002
  - ACT-PFM-004
  - ACT-PFM-005
evidence:
  - >-
    react-console at baf6dae: components/console/{nav-config.ts,app-sidebar.tsx},
    lib/console/{domains.ts,use-visible-nav.ts},
    lib/custom-objects/{navigation.ts,use-custom-navigation.ts}, lib/authz/evaluate.ts,
    docs/migration/02-information-architecture.md §1 to §6, docs/url-architecture.md §3 and §5,
    e2e/mock/custom-object-navigation.mock.spec.ts, e2e/security/navigation.spec.ts.
  - >-
    services-platform at ad3f6a6: modules/custom-objects/aws/api/custom-apps.routes.ts (the custom
    app records the menu reads; owned by MOD-PFM-MTD).
supersedes: []
---

# Navigation

## What It Is

Navigation is the console's visible map of work. It organizes destinations so that people can move among applications, shared tools and workspace administration without learning a separate interface for each product. The map also accommodates an organization's own record types, making custom work part of the same console experience.

The menu represents destinations rather than business records themselves. A destination has a recognizable name and a place in a group. Its presentation draws on shared catalogues and the person's current context. This gives the product a consistent basis for menu entries, current-position highlighting and planned destinations, while leaving each destination's actual task to its owning module.

## What It Is Not

A menu is not a grant of authority. Showing an entry helps a person find work; hiding one reduces confusion. Page and service checks still determine whether the requested work can proceed. A saved address can reach a page without passing through the menu at all.

Navigation is distinct from search and breadcrumbs. Search helps locate a record or page by what the person knows about it. Breadcrumbs explain a position in a hierarchy. Navigation gives a broader set of destinations from which to choose. Custom application records are also separate: metadata defines those records, while navigation presents their placements.

## How It Is Used

Customer staff usually begin with the applications relevant to their work and move to a list or tool from there. Administrators enter a settings area when they need to change the workspace rather than operate within it. Rhythm staff have their own destinations when carrying out Rhythm's work and the customer's navigation when entering a customer workspace.

A long menu makes recognition harder, so filtering supports finding a destination by name. The current position helps someone return their attention to the group they are already using. Returning from settings also has a navigation purpose: the person should be able to resume their work with a clear understanding of the destination that is restored.

## Its Facets

**Groups and destinations.** Application sections organize related work, while menu items name individual tasks. Shared tools and links to related services occupy their own positions in that organization.

**Administrative and staff contexts.** Settings areas replace the daily-work map with an administrative one. Rhythm HQ has a staff map for work outside a customer's workspace. These contexts make the purpose of a destination easier to recognize.

**Customer extensions.** Custom placements make the organization's own record types visible within an application or a custom grouping. Their labels and grouping are presentation choices supplied by metadata.

**Finding and orientation.** The filter narrows what a person needs to scan. The active position connects the address being viewed with the destination represented in the menu. These facets serve different needs: choosing somewhere new and understanding the current place.

## How It Relates

The console shell provides the space for navigation. Console addresses provide destinations and a way to recognize the current page. Application access determines which product sections are relevant to the workspace and person. Security provides permission answers used in presenting entries.

Metadata owns customer-defined applications and record types. Navigation consumes their placements without taking ownership of their creation or administration. The service behind a destination remains responsible for its data and refusals.

## What It Could Become

The product should decide how unfinished destinations appear during customer use. The product should also review the broader information architecture before adding new administrative groups or shared tools. Personal favourites and pinned destinations could reduce repeated navigation, but their persistence and relationship to changing access need an explicit product decision.
