Dominus template

A polished starter for service dashboards that still respects the backend.

CareBridge Admin Portal is built for projects where the real product pages are custom, but auth, tenant switching, admin tools, and operations scaffolding should already be coherent on day one.

Tenant switcher remains JWT-backed and Portal-native.

Appearance settings stay local to the browser, not mixed into backend profile state.

Fallback nav stays intentionally minimal so real navigation still comes from the backend.

Service overview starter

What downstream teams get on first launch.

backend-aware shell

Starter routes

Reusable operations scaffolds ready for project-specific data wiring.

Auth source

Portal

Admin source

Guardian

Roles, pages, scopes, and navigation are configured where operators already work.

Included dashboard scaffolds

Client operations

Reusable list/detail scaffold for accounts, cases, members, or customers.

Work queue

Prioritized queue scaffold for triage, tasks, reviews, and service requests.

Automations

Jobs and pipelines starter for schedules, run history, and health states.

Reports and analytics

Reporting starter with comparison cards, charts, and export affordances.

Portal-driven navigation

Sidebar and tenant context stay backend-authoritative instead of drifting into hardcoded frontend state.

Guardian-managed access

Roles, scopes, pages, and nav configuration continue to live in the auth admin surface where downstream projects expect them.

Reusable dashboard starters

Clients, work queue, automations, and reports provide project-safe scaffolds without pretending to know the product domain.

Starter modules

Generic enough to clone, specific enough to feel useful.

Most projects built from this template will still be service dashboards. These starters avoid fake product detail pages and focus on the patterns those projects actually need.

Client operations

Searchable tables, status chips, and a detail panel give downstream projects a credible entity-management starting point.

Preview route

Work queue

Bulk actions, assignee visibility, due-date awareness, and mobile cards fit most operations teams immediately.

Preview route

Automations

Lets projects layer in cron jobs, integrations, or orchestration views without first inventing a shell.

Preview route

Reports and analytics

Provides a solid analytics frame without pretending to know the final KPIs or data warehouse shape.

Preview route

What remains project custom

The template stops short of pretending to know the product domain. Downstream teams should replace placeholders with real service logic and real backend data.

Project-specific dashboards and workflows

Actual entity schemas, reports, and automations

Tenant/category-specific page access rules

Final navigation composition inside Guardian

What you get polished upfront

The shell, auth surfaces, appearance controls, and onboarding flow are ready to hand to a new project without an immediate visual redesign pass.

One-page landing focused on service dashboards

Branded auth screens aligned to actual Portal behavior

Appearance controls for theme, accent, density, shell, and radius

Service overview page with setup checklist and route discoverability

Admin setup path

Manual backend configuration is still the intended path.

The template makes new starter pages easy to discover, but it does not silently expand fallback navigation or auto-seed backend page records beyond the existing first-hit registration path.

Step 1

Visit each starter route as an admin.

Step 2

Confirm page rules inside Auth > Pages.

Step 3

Create navigation entries inside Auth > Navigation.

Step 4

Replace placeholder data with project services.