[Feature] Configurable side rail ordering by system, tenant, and user preference #266

New Issue

2026-07-14T20:08:43+02:00

zemion commented

2026-07-14 20:08:43 +02:00

Problem / User Need

The side rail icon order should be checked and made configurable. Admins, tenants, and individual users may need different ordering preferences.

Acceptance Criteria

Current side rail sorting is reviewed for predictable default ordering.
System/admin-level ordering can be configured where appropriate.
Tenant-level overrides can be considered without breaking module-provided nav metadata.
User-level ordering/preferences can be considered for personal ergonomics.
The final precedence model is documented.

Notes / Decisions

Needs design decision for precedence: module default order, system override, tenant override, user override.

## Problem / User Need The side rail icon order should be checked and made configurable. Admins, tenants, and individual users may need different ordering preferences. ## Acceptance Criteria - Current side rail sorting is reviewed for predictable default ordering. - System/admin-level ordering can be configured where appropriate. - Tenant-level overrides can be considered without breaking module-provided nav metadata. - User-level ordering/preferences can be considered for personal ergonomics. - The final precedence model is documented. ## Notes / Decisions Needs design decision for precedence: module default order, system override, tenant override, user override.

zemion commented

2026-07-20 14:43:15 +02:00

Campaign #42 was closed as a shell-owned duplicate. Keep this issue for configurable rail order; focused task/view composition is tracked by the broader interface program add-ideas/govoplan#11 and remains a separate contract.

zemion added the area/tenancy area/webui codex/ready module/core

labels 2026-07-29 14:15:04 +02:00

zemion closed this issue

2026-08-20 01:49:24 +02:00

zemion commented

2026-08-20 01:50:51 +02:00

Implemented and verified the configurable side-rail preference stack.

Precedence is module default → system → tenant → user. System and tenant scopes may lock entries visible; lower scopes may reorder locked entries but cannot hide them, and personal lock attempts are rejected. The platform response now exposes each inherited layer separately so an administrator's personal order cannot be promoted accidentally.

Delivered in:

Core cf16a7b — resolver/contract, effective platform metadata, shared editor, personal settings UI, documentation, API and unit coverage
Admin a1d7b64 — system baseline/order/visibility/locks
Tenancy 56f0661 — tenant overrides and locks
Access 5c6f446 — personal persistence and lock rejection

Verification: Core WebUI production build, 7/7 Playwright conformance tests, navigation resolver tests, profile/system/tenant API round trips, Admin/Tenancy/Access suites, Ruff, and the 68/68 manifest registry check.

Implemented and verified the configurable side-rail preference stack. Precedence is module default → system → tenant → user. System and tenant scopes may lock entries visible; lower scopes may reorder locked entries but cannot hide them, and personal lock attempts are rejected. The platform response now exposes each inherited layer separately so an administrator's personal order cannot be promoted accidentally. Delivered in: - Core `cf16a7b` — resolver/contract, effective platform metadata, shared editor, personal settings UI, documentation, API and unit coverage - Admin `a1d7b64` — system baseline/order/visibility/locks - Tenancy `56f0661` — tenant overrides and locks - Access `5c6f446` — personal persistence and lock rejection Verification: Core WebUI production build, 7/7 Playwright conformance tests, navigation resolver tests, profile/system/tenant API round trips, Admin/Tenancy/Access suites, Ruff, and the 68/68 manifest registry check.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-core#266