Admin Dashboards

The boilerplate includes two admin dashboards: a platform-wide super admin and an organization-level admin for B2B workspaces.

Platform Admin Dashboard

Located at /admin-dashboard, accessible only to users with is_admin=true in their profile.

Auto-Admin Assignment

The admin check uses the shared maybeAutoPromoteAdmin() helper so layout and API admin verification follow the same auto-fix path:

• Compares user email with admin_email in app_settings table
• If email matches but is_admin=false, automatically updates to is_admin=true
• Works in both layout (server-side) and API routes without duplicating the update/audit logic
• Uses supabaseAdmin (service role) to bypass RLS

Dashboard Pages

KPI Performance

Dashboard queries are optimized for performance:

• Server Component pages render pre-aggregated data from core/admin/* modules instead of inlining service-role query orchestration
• Parallel database queries with Promise.all (9 queries in parallel)
• MRR/ARR calculation from pricingConfig (code-based, not DB)
• Efficient counting with count: 'exact', head: true
• Explicit projections such as select('id') or select('amount') instead of select('*') for production queries
• supabaseAdmin bypasses RLS for platform-wide stats

Admin Dashboard Design System

The admin dashboard follows a Data-Dense Dashboard design pattern optimized for information density and at-a-glance insights. The design uses shadcn/ui components with Tailwind CSS v4 theme tokens.

Organization Admin Dashboard

Located at /org-dashboard, accessible to workspace owners and admins.

Pagination

Tables include reusable pagination controls:

• Rows per page selector (5, 10, 20, 50)
• Page navigation (first, previous, next, last)
• "Showing X to Y of Z entries" display
• Page indicator (Page X of Y)
• Independent pagination state per table

Shared Dashboard Context

The private and organization dashboards share request-level context helpers in core/accounts/dashboard-context.ts. They use React.cache() to deduplicate repeated auth/account reads between a layout and its child page during one request.

These helpers are not static caches. They read the current request session with getUser(), so they remain appropriate only for protected dynamic routes. Layouts and pages still own redirects: unauthenticated users go to login, users without org-manager membership go back to /private-dashboard, and B2B workspaces without access go to pricing.

Organization Dashboard Performance

Organization dashboard analytics and member usage stats are pre-aggregated in SQL instead of loading raw usage rows into the page component. Keep this boundary when adding new dashboard cards:

• core/accounts/dashboard-usage.ts wraps the aggregate readers used by the private dashboard overview, org overview, org analytics, member list, and member detail pages.
• get_org_dashboard_analytics returns 30-day KPIs, previous-period comparisons, daily usage, top members, model/agent breakdowns, active users, latency, and success rate for /org-dashboard/analytics.
• get_org_member_usage_summary returns per-member request count, token total, cost, last AI activity, and chat-session count for member list/detail screens.
• get_account_dashboard_usage_summary powers lightweight overview counters without downloading ai_requests or chat_sessions.
• Supporting indexes cover ai_requests(account_id, user_id, created_at desc), chat_sessions(account_id, user_id, created_at desc), and user_access_logs(user_id, created_at desc).