Epic: Consolidated Administration settings (single entry → grouped rail → tabs)

Cordy commented

2026-08-16 17:06:22 +00:00

Owner

Problem

Admin configuration has grown past what a single modal can hold: basic settings, storage/quotas, retention, auto-purge, legal holds, audit logging, sharing policy, spaces backend, encryption/key custody, peering (relationships + inbound keys + settings), licensing (license + seats + billing), updates. Today these are scattered across a Settings modal and a few purpose dialogs. It deserves a dedicated location, the way Keycloak, Nextcloud, and Paddle give admin config its own shell.

Decision (mockups reviewed 2026-08-16)

Chosen layout: Option A — grouped rail + tabs. One Administration entry → a left rail of topics grouped into sections → a content pane with a topic header, a tab strip for the topic's parallel views (the Paddle "API keys / Client-side tokens" pattern), and setting rows. Rejected: a three-pane Keycloak-style console (B, extra chrome, only worth it at ~2x the topic count) and a rail-plus-sticky-anchors scroll (C, mixes idioms). A is the lowest-friction and maps cleanly onto what already exists.

Interaction model:

Single admin entry point (account menu → Administration), admin-gated exactly as today (auth.admins / auth.adminGroups).
Deep-linkable: #/admin/<topic> and #/admin/<topic>/<tab>, so docs and support can link straight to a tab.
Keyboard-navigable rail and tabs; in-memory session unaffected.
Wears Cairn's skin — glacier-teal active states, amber for keys/warnings, mono for fingerprints/IDs — reusing the existing peering-card component styles, not a new visual language. (Mockups were neutral wireframes for layout selection only.)

Topic inventory + tabs

Section	Topic	Tabs
Instance	Basic settings	General (instance name, default share expiry, email server)
Instance	Storage & quotas	Usage · Limits
Instance	Retention & holds	Retention · Auto-purge · Legal holds
Instance	Audit log	Settings · Query
Instance	Updates	Version (running version + upstream check)
Access	Users & access	Admins · Two-factor
Access	Encryption & keys	Custody · Recovery
Sharing & spaces	Sharing	Policy · Active links
Sharing & spaces	Spaces	General (backend, IdP power mode)
Federation	Peering	Relationships · Inbound keys · Settings
Billing	Licensing	License · Seats · Billing

Optional landing Overview topic (instance name, version, license tier, storage used, peering on/off) — mirrors the Nextcloud/Paddle overview; decide during the shell build.

Non-goals

No change to the underlying settings APIs — this is an information-architecture / presentation change over the existing endpoints.
No new policy features introduced here.
Per-user (non-admin) settings stay where they are.

Rollout (incremental, one topic per PR)

Settings shell — grouped rail + tab framework + deep-link routing + admin gate. Land with one pilot topic.
Pilot: Peering — it is the most tab-shaped and freshest surface (Relationships / Inbound keys / Settings), so it validates the shell.
Port the rest topic-by-topic, each PR moving one existing surface in and leaving the old entry as a redirect until everything is migrated.
Remove the legacy Settings modal; redirect old entry points.
Docs: refresh admin-policy.md and peering.md, deep-link tabs, add screenshots (ties into #206).

Task checklist

Settings shell: grouped rail + tab framework + #/admin/<topic>/<tab> routing + admin gate
Pilot: port Peering into the shell (Relationships / Inbound keys / Settings)
Port Licensing (License / Seats / Billing)
Port Sharing (Policy / Active links) + Storage & quotas (Usage / Limits)
Port Retention & holds (Retention / Auto-purge / Legal holds) + Audit log (Settings / Query)
Port Encryption & keys (Custody / Recovery) + Spaces + Basic settings + Updates + Users & access
Optional: Overview landing topic
Remove legacy Settings modal + redirect old entries
Docs: refresh admin-policy.md / peering.md, deep-link tabs, screenshots (see #206)

Milestone: v0.7 (the closed-beta UI/UX batch). Refs: #206 (docs refresh), #176/#150 (peering panel this generalizes), #178/#186 (quotas/audit surfaces to fold in).

Break the checklist into individual issues when we're ready to schedule the batch.

## Problem Admin configuration has grown past what a single modal can hold: basic settings, storage/quotas, retention, auto-purge, legal holds, audit logging, sharing policy, spaces backend, encryption/key custody, peering (relationships + inbound keys + settings), licensing (license + seats + billing), updates. Today these are scattered across a Settings modal and a few purpose dialogs. It deserves a dedicated location, the way Keycloak, Nextcloud, and Paddle give admin config its own shell. ## Decision (mockups reviewed 2026-08-16) Chosen layout: **Option A — grouped rail + tabs.** One **Administration** entry → a left rail of topics grouped into sections → a content pane with a topic header, a tab strip for the topic's parallel views (the Paddle "API keys / Client-side tokens" pattern), and setting rows. Rejected: a three-pane Keycloak-style console (B, extra chrome, only worth it at ~2x the topic count) and a rail-plus-sticky-anchors scroll (C, mixes idioms). A is the lowest-friction and maps cleanly onto what already exists. Interaction model: - Single admin entry point (account menu → Administration), admin-gated exactly as today (`auth.admins` / `auth.adminGroups`). - **Deep-linkable**: `#/admin/<topic>` and `#/admin/<topic>/<tab>`, so docs and support can link straight to a tab. - Keyboard-navigable rail and tabs; in-memory session unaffected. - Wears Cairn's skin — glacier-teal active states, amber for keys/warnings, mono for fingerprints/IDs — reusing the existing peering-card component styles, not a new visual language. (Mockups were neutral wireframes for layout selection only.) ## Topic inventory + tabs | Section | Topic | Tabs | |---|---|---| | Instance | Basic settings | General (instance name, default share expiry, email server) | | Instance | Storage & quotas | Usage · Limits | | Instance | Retention & holds | Retention · Auto-purge · Legal holds | | Instance | Audit log | Settings · Query | | Instance | Updates | Version (running version + upstream check) | | Access | Users & access | Admins · Two-factor | | Access | Encryption & keys | Custody · Recovery | | Sharing & spaces | Sharing | Policy · Active links | | Sharing & spaces | Spaces | General (backend, IdP power mode) | | Federation | Peering | Relationships · Inbound keys · Settings | | Billing | Licensing | License · Seats · Billing | Optional landing **Overview** topic (instance name, version, license tier, storage used, peering on/off) — mirrors the Nextcloud/Paddle overview; decide during the shell build. ## Non-goals - No change to the underlying settings APIs — this is an information-architecture / presentation change over the existing endpoints. - No new policy features introduced here. - Per-user (non-admin) settings stay where they are. ## Rollout (incremental, one topic per PR) 1. **Settings shell** — grouped rail + tab framework + deep-link routing + admin gate. Land with one pilot topic. 2. **Pilot: Peering** — it is the most tab-shaped and freshest surface (Relationships / Inbound keys / Settings), so it validates the shell. 3. Port the rest topic-by-topic, each PR moving one existing surface in and leaving the old entry as a redirect until everything is migrated. 4. Remove the legacy Settings modal; redirect old entry points. 5. Docs: refresh `admin-policy.md` and `peering.md`, deep-link tabs, add screenshots (ties into #206). ## Task checklist - [x] Settings shell: grouped rail + tab framework + `#/admin/<topic>/<tab>` routing + admin gate - [x] Pilot: port Peering into the shell (Relationships / Inbound keys / Settings) - [x] Port Licensing (License / Seats / Billing) - [x] Port Sharing (Policy / Active links) + Storage & quotas (Usage / Limits) - [x] Port Retention & holds (Retention / Auto-purge / Legal holds) + Audit log (Settings / Query) - [x] Port Encryption & keys (Custody / Recovery) + Spaces + Basic settings + Updates + Users & access - [ ] Optional: Overview landing topic - [x] Remove legacy Settings modal + redirect old entries - [x] Docs: refresh admin-policy.md / peering.md, deep-link tabs, screenshots (see #206) Milestone: v0.7 (the closed-beta UI/UX batch). Refs: #206 (docs refresh), #176/#150 (peering panel this generalizes), #178/#186 (quotas/audit surfaces to fold in). _Break the checklist into individual issues when we're ready to schedule the batch._

Cordy added this to the v0.7 — Closed beta (dogfood + hardening) milestone

2026-08-16 17:06:22 +00:00

Cordy referenced this issue

2026-08-16 17:11:31 +00:00

Admin settings shell + Peering pilot (epic #250, phase 1) #251

Cordy referenced this issue

2026-08-16 17:11:35 +00:00

Admin settings: port Licensing, Sharing, Storage & quotas (epic #250, phase 2) #252

Cordy referenced this issue

2026-08-16 17:11:38 +00:00

Admin settings: port Retention & holds, Audit log, Encryption & keys (epic #250, phase 3) #253

Cordy referenced this issue

2026-08-16 17:11:44 +00:00

Admin settings: port Spaces, Basic settings, Updates, Users & access (epic #250, phase 4) #254

Cordy referenced this issue

2026-08-16 17:11:47 +00:00

Admin settings: retire legacy modal + redirects + docs refresh (epic #250, phase 5) #255

Cordy commented

2026-08-16 17:12:07 +00:00

Author

Owner

Broken into five dependency-ordered sub-issues (v0.7):

Phase 1 — #251 — Settings shell + Peering pilot (blocks the rest)
Phase 2 — #252 — Port Licensing, Sharing, Storage & quotas
Phase 3 — #253 — Port Retention & holds, Audit log, Encryption & keys
Phase 4 — #254 — Port Spaces, Basic settings, Updates, Users & access (+ Overview decision)
Phase 5 — #255 — Retire legacy modal + redirects + docs refresh (closeout)

Note: the ports (2–4) are logically independent but should land sequentially, not in parallel — they all edit the same web/static/index.html, so concurrent branches would fight over anchors and conflict on merge.

Broken into five dependency-ordered sub-issues (v0.7): - Phase 1 — #251 — Settings shell + Peering pilot (blocks the rest) - Phase 2 — #252 — Port Licensing, Sharing, Storage & quotas - Phase 3 — #253 — Port Retention & holds, Audit log, Encryption & keys - Phase 4 — #254 — Port Spaces, Basic settings, Updates, Users & access (+ Overview decision) - Phase 5 — #255 — Retire legacy modal + redirects + docs refresh (closeout) Note: the ports (2–4) are logically independent but should land **sequentially**, not in parallel — they all edit the same `web/static/index.html`, so concurrent branches would fight over anchors and conflict on merge.

Cordy referenced this issue

2026-08-16 17:53:25 +00:00

#251: consolidated Administration settings shell + Peering pilot (v0.6.30) #256

forgejo-actions referenced this issue from a commit

2026-08-16 19:49:41 +00:00

#252: port Licensing/Sharing/Storage into admin shell (epic #250 phase 2)

Cordy referenced this issue

2026-08-16 19:51:08 +00:00

#252: port Licensing, Sharing, Storage & quotas into the admin shell (epic #250 phase 2) #258

Cordy referenced this issue from a commit

2026-08-16 19:53:51 +00:00

#252: port Licensing, Sharing, Storage & quotas into the admin shell (epic #250 phase 2) (#258)

forgejo-actions referenced this issue from a commit

2026-08-16 20:19:45 +00:00

#253: port Retention/Audit/Encryption into admin shell (epic #250 phase 3)

Cordy referenced this issue

2026-08-16 20:20:52 +00:00

#253: port Retention & holds, Audit log, Encryption & keys into the admin shell (epic #250 phase 3) #259

Cordy referenced this issue from a commit

2026-08-16 20:22:52 +00:00

#253: port Retention & holds, Audit log, Encryption & keys into the admin shell (epic #250 phase 3) (#259)

forgejo-actions referenced this issue from a commit

2026-08-16 20:43:12 +00:00

#254: Overview + Updates/Spaces/Users admin topics (epic #250 phase 4)

Cordy referenced this issue

2026-08-16 20:44:16 +00:00

#254: Overview landing + Updates, Spaces, Users & access admin topics (epic #250 phase 4) #260

Cordy referenced this issue from a commit

2026-08-16 20:45:36 +00:00

#254: Overview landing + Updates, Spaces, Users & access admin topics (epic #250 phase 4) (#260)

forgejo-actions referenced this issue from a commit

2026-08-16 21:21:08 +00:00

#255: Check-for-updates button + admin-policy docs refresh (epic #250 closeout)

Cordy referenced this issue

2026-08-16 21:22:25 +00:00

#255: Check-for-updates button + admin-shell epic closeout (epic #250 phase 5) #261

Cordy referenced this issue from a commit

2026-08-16 21:23:46 +00:00

#255: Check-for-updates button + admin-shell epic closeout (epic #250 phase 5) (#261)

forgejo-actions referenced this issue from a commit

2026-08-17 18:41:44 +00:00

Remove redundant License/Peering/Settings quick-links from the account menu (#250 follow-up)

Cordy referenced this issue

2026-08-17 18:42:46 +00:00

Remove redundant License/Peering/Settings quick-links from the account menu (#250 follow-up) #262

Cordy referenced this issue from a commit

2026-08-17 18:44:05 +00:00

Remove redundant License/Peering/Settings quick-links from the account menu (#250 follow-up) (#262)

Cordy closed this issue

2026-08-26 17:40:15 +00:00

Cordy commented

2026-08-26 17:40:18 +00:00

Author

Owner

Closing — all mandatory rollout items complete (shell + all topics ported, legacy modal removed, docs refreshed). The one remaining checklist item, the optional Overview landing topic, shipped separately and is tracked/closed via #302.

Rows
Columns

Epic: Consolidated Administration settings (single entry → grouped rail → tabs) #250

Problem

Decision (mockups reviewed 2026-08-16)

Topic inventory + tabs

Non-goals

Rollout (incremental, one topic per PR)

Task checklist