Visit settings and return to the preceding work

Purpose

Administrative navigation lets staff move into settings without losing their previous working destination.

How It Works

An administrator opens an available settings area from the account menu. The address selects a focused menu for that area. The sidebar retains the last working path so the administrator has a return destination. A direct arrival in settings has no preceding working page and returns home. Area visibility and individual page authority are separate checks. The product should test the complete return journey and refused destinations in a browser.

Relationships

Main navigation records the work destination used by Back to app.
The record-owning module governs each settings screen.

Show evidence (sources, provenance, origins, pinned commits)

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Outcomes: Administrative areas have focused navigation.Staff have a direct route back to their preceding work.
Surfaces: console
Intent sources: react-console:docs/url-architecture.md#3. Workspaces (decided by Andrew 2026-10-14; final acceptance 2026-10-15)

Controls

25 controls apply, from the corpus control catalogue.

TC-AVL-001 TC-AVL-004 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-DAT-001 TC-DAT-003 TC-IAM-001 TC-IAM-006 TC-LOG-004 TC-LOG-005 TC-MON-001 TC-MON-003 TC-PI-002 TC-PI-004 TC-PI-005 TC-PRV-001 TC-PRV-002 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-VEN-001 TC-VEN-002 TC-VEN-003

Permissions

Key	Checked at	Scope
`configuration.access`	console	tenant
`maintenance.access`	console	tenant
`security.access`	console	tenant
`data.jobs.view`	console	tenant
`configuration.responsibilities.view`	console	tenant
`platform.notifications.manage`	console	tenant
`platform.application.access`	api	tenant

Business Rules

10 rules, 5 to be proved before approval. A rule's product intent is derived from its origin: 0 confirmed by a product decision, the rest inheriting this capability's proposed.

Id	Rule	Kind	Enforced at	Provenance
`01` Proposed	The registered settings areas are Configuration, Maintenance, Data Management, Security, Responsibilities and Notifications, each with its own root and revealing permission. proved by `ATS-PFM-CSH-007-07`	policy	console	observed react-console:components/console/nav-config.ts:settingsAreas
`02`must prove Proposed	In workspace mode an area appears in the user menu only when its permission passes and at least one destination in its navigation is visible. proved by `ATS-PFM-CSH-007-01`, `TST-PFM-CSH-022`	permission	console	test react-console:lib/console/__tests__/settings-area-menu.test.ts#does not offer Security or Maintenance to a person who holds only the areas' access keys
`03`must prove Proposed	A settings address replaces main navigation with that area’s menu and Back to app targets the last non-settings path, or home after direct entry. proved by `ATS-PFM-CSH-003-05`, `ATS-PFM-CSH-007-02`	lifecycle	console	observed react-console:components/console/app-sidebar.tsx:AppSidebar, SettingsNavigation
`04`must prove Proposed	The recorded root destinations are Users for Security, Scheduled Jobs for Maintenance and Data Imports for Data Management. origin: react-console:docs/url-architecture.md#4.1 Tenant console (decided by Andrew 2026-10-14; final acceptance 2026-10-15) proved by `ATS-PFM-CSH-007-03`	lifecycle	console	documented react-console:docs/url-architecture.md#4.1 Tenant console
`05` Proposed	Configuration groups Data, Presentation, Workflows, Accounting, Billing and Connections before application settings, with All Applications first among its application links when permitted.	policy	console	observed react-console:components/console/nav-config.ts:configurationArea
`06`must prove Proposed	Maintenance contains Scheduled Jobs, while duplicate rules and integrations belong in Configuration and their old Maintenance paths preserve views and queries on redirect. origin: react-console:docs/url-architecture.md#3. Workspaces (Andrew, 2026-10-16: Maintenance holds Scheduled Jobs alone) (decided by Andrew 2026-10-14; final acceptance 2026-10-15) proved by `ATS-PFM-CSH-007-04`	policy	console	documented react-console:docs/url-architecture.md#3. Workspaces
`07` Proposed	Security lists Users, Roles, Policies and Rhythm Access, each with a separate entry permission. proved by `ATS-PFM-CSH-007-05`, `TST-PFM-CSH-015`	policy	console	observed react-console:components/console/nav-config.ts:securityArea
`08` Proposed	Data Management’s revealing key maps to bulk-record authority rather than application availability.	permission	console	observed react-console:components/console/nav-config.ts:dataManagementArea
`09` Proposed	Each settings area provides its own filter using the same matching behavior as main navigation.	policy	console	observed react-console:components/console/app-sidebar.tsx:SettingsNavigation
`10`must prove Proposed	Orders & Inventory configuration registers Stores with its own view key and omits Price Schedules from both the configuration-area catalogue and menu. proved by `ATS-PFM-CSH-007-06`, `TST-PFM-CSH-019`	permission	console	test react-console:lib/console/__tests__/orders-nav.test.ts#lists Stores with its own view permission; lib/console/__tests__/orders-nav.test.ts#does not list Price Schedules: a schedule belongs to the event that sells the product (ruling R5, 2026-10-22)

Scenarios

Id	Given	When	Then	Provenance
`01`	A contact page is the administrator’s current work.	They enter Configuration and later use Back to app.	The contact path is restored.	observed react-console:components/console/app-sidebar.tsx:AppSidebar
`02`	The person holds Security’s area key but no visible Security entry key.	The account menu is generated.	Security is not offered.	observed react-console:components/console/app-sidebar.tsx:AppSidebar

Planning

Implementation

Visit settings and return to the preceding work ​

Purpose ​

How It Works ​

Relationships ​