Build org admin home screen variant and content
epic-role-based-access-control-ui-and-navigation-task-004 — Implement the org admin home screen content variant showing org-level statistics, member counts, area summaries, and admin action shortcuts. This variant is displayed only when the active role is org admin, distinguishing it from the global admin who is redirected to No-Access Screen.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 1 - 540 tasks
Can start after Tier 0 completes
Implementation Notes
Implement OrgAdminHomeCubit or OrgAdminHomeNotifier for data fetching, scoped to the admin's org_id extracted from the current RoleState. For area summaries, prefer a Supabase RPC or aggregated query over N individual queries (one per area) to keep load times acceptable for orgs with many chapters (NHF has up to 1,400 lokallag — a full list is not appropriate here; limit to top 5 by activity count with a 'View All' link). Admin action shortcuts should use the existing reusable card/button components from the shared widget library rather than custom styled containers. Clearly document in code comments that this variant is for orgAdmin only and is distinct from the globalAdmin blocked state.
Testing Requirements
Widget tests using flutter_test. Cover: (a) loaded state with sample org stats and area list, (b) loading state, (c) error state. Assert that OrgAdminHomeContent is NOT present in the widget tree when RoleState is coordinator, peerMentor, or globalAdmin — pump each state and use find.byType with findsNothing. Verify admin shortcut tap navigation using NavigatorObserver.
Assert org_id scoping: inspect the queries captured by the fake Supabase client and verify org_id filter is present on all calls.
Combining GoRouter's declarative redirect logic in the route guard with StatefulShellRoute's stateful branch management is known to produce subtle bugs where the shell rebuilds unnecessarily on role switches, losing tab state or causing double-navigation events.
Mitigation & Contingency
Mitigation: Implement the route guard as a GoRouter redirect callback that only evaluates role from an already-resolved Riverpod provider (not async). Use a dedicated ShellRoute navigator key per tab branch to anchor state independently of role-driven rebuilds. Write integration tests for the full navigation graph.
Contingency: If StatefulShellRoute state loss is confirmed during QA, fall back to a manual tab state preservation approach using a TabStateManager service that caches the last route per tab and restores it after role switches, decoupling tab state from the shell lifecycle.
The role-based home screen must render three significantly different layouts (coordinator dashboard, peer mentor activity summary, org admin overview). If these variants are implemented as a single widget with conditionals, the file will become unmaintainable and difficult to test in isolation, especially as each variant grows with downstream feature additions.
Mitigation & Contingency
Mitigation: Design the role-based home screen as a router/dispatcher widget that delegates to three separate variant widgets (CoordinatorHomeView, PeerMentorHomeView, OrgAdminHomeView). Each variant is independently testable and can be developed by separate team members in parallel.
Contingency: If variant coupling has already occurred before this risk is addressed, refactor to the dispatcher pattern in a dedicated cleanup task before feature handoff. The dispatcher pattern is a straightforward extraction that carries low refactoring risk.
The no-access screen must link global admin users to the correct admin portal URL, which may differ per organization (NHF, HLF, Blindeforbundet each have their own admin portals). Hardcoding a single URL will result in wrong or broken links for some global admin users.
Mitigation & Contingency
Mitigation: Source the admin portal URL from the organization's configuration record in Supabase rather than hardcoding it. The no-access screen reads the active org context and resolves the portal URL dynamically. Provide a safe fallback to a generic Norse Digital Products support page if the URL is not configured.
Contingency: If dynamic URL resolution is not ready when the no-access screen ships, display a static instruction to contact the organization's administrator along with a support email address as an interim measure, and track the URL configuration task as a follow-up.