Stop treating intake, policy, and operational work like unrelated tools. Start in the right lane, keep access context visible, and move straight into execution.
Start in operations, policies, or intake based on the task instead of burying everything on one page.
Keep role-aware access visible so protected routes and real workflow permissions stay obvious.
Push directly from intake into the case workspace instead of forcing repeated setup screens.
This page now has one job: orient the team, expose access state, and route people into the right workspace with minimal friction.
Run recurring work, track due tasks, and preserve attestation without leaving the queue.
Draft, review, publish, and answer policy questions from the same operating surface.
Launch a patient case from a dedicated route built for intake, verification, and handoff.
Protected routes require a Supabase access token whose user metadata resolves to `Tech`, `Pharmacist`, or `Admin`, so this panel stays focused on authentication and role status only.
Use Google when the team already works from managed Supabase accounts.
Send a magic-link sign-in email when passwordless access is enabled for the current Supabase project.
Production access requires Supabase role metadata for Tech, Pharmacist, or Admin.
Operations and policies are first-class work areas, not utility pages.
Intake is route-based so case creation stays focused and fast.
Intake lives on its own route so patient entry, verification, and handoff can happen without crowding the operating view.