Admin access

Users

App-owned Hub accounts, permissions, and AI personalization. This is separate from the Notion-synced Team directory.

Registry pending

Hub users0App-owned accounts, not Notion Staff rows.

Active0Eligible for role-scoped Hub access after Auth cutover.

Admins0Owner and admin app roles.

AI profiles0Users with AI profile or working-style context.

User registry

Access and personalization

Add Hub users here as the source for login access, visible modules, external user IDs, and Ask Hub profile context. Staff rows can be linked later for directory context, but they do not grant access.

Permissions live in Supabase/app code. AI prompts and Notion Staff fields are not security boundaries.

No Hub users yet

The registry is ready for app-owned users. The first write path should invite users into Supabase Auth and create a matching `hub_users` row with role, modules, and optional AI notes.

Next access step

Build the invite action after Supabase Auth is wired: create the Auth user, insert a `hub_users` record, then send the magic link. Do not auto-import the Team directory.

Personalized Today

Today can later rank cards from `allowed_modules`, `ai_focus_areas`, and `today_preferences`, while the underlying records stay protected by RLS.

Data sources: 0 connected · 1 pendingDetails

Hub user registryPendingThe Hub user registry tables are not readable yet. Apply the migration, then refresh this page.