Dattavani Backend: Admin Console Diagram

What it is

An Expo Router web app. npm run deploy exports dist/ and runs firebase deploy (package.json:11-12).
It edits content and settings straight in Supabase. It does not go through core-service for writes.
Sidebar: books, bedtime stories, Tataji config, curated prompts, nudge questions, app config, WebP converter, feedback.
Quiz, gamification and logs screens exist but are not in the sidebar. Open them by URL.

Who can get in

Login is email OTP for users who already exist (shouldCreateUser false, login.tsx:18-23).
After login the app_metadata.user_role claim must be admin. Otherwise the app signs the user out.
lib/rbac.ts defines super_admin, content_manager and support_lead, but no screen calls it. Every admin sees every module.

Security risk

Both Supabase clients are built with [redacted] (lib/supabase.ts:6-30).
The R2 access key and secret are EXPO_PUBLIC_ too (lib/r2.ts:3-10).
Expo inlines EXPO_PUBLIC_ values into the hosted bundle, so anyone who loads the site can read them (docs/setup.md:118).
The service-role key bypasses row-level security. Move privileged writes behind core-service.

When edits show in the app

Content saves POST /api/learnings/internal/cache/invalidate with [redacted].
core-service caches the catalog in each process for 600 s, so the bust clears one instance behind the load balancer.
Story saves call /api/stories/internal/cache/invalidate. core-service has no such route, so stories refresh only when the TTL ends.

Stale parts

The allowlist screen still reads public.allowlist. Migration 20260723120000_drop_allowlist.sql dropped that table.
admin/README.md is the Expo template. Use docs/setup.md section 4 for setup.