SB
Stream Bandit Owner Admin HubOwner/admin protected controls - V7.12.300.22
Permissions MatrixBack
V7.12.300.22 Owner/Admin Hub + Simple Delete Queue

Real owner control room

This page keeps the stable User Management controls and folds in the tested simple account-delete queue. Profile management still uses sb_owner_manage_profile. Account deletion uses the real sb_account_deletion_requests queue and the server-side sb-account-delete Edge Function for spare normal users only.

Owner/admin route gateSchema-backedRPC controlledAudit loggedSimple DELETE confirmNo service-role secret in browserNo admin/owner delete
Current account--

Checking...

Visible users--

Rows RLS allows this verified owner/admin to see.

Selected user--

Current managed profile.

Delete requests--

Rows from the real request queue.

Real controls
  • Role admin/user
  • can_submit
  • account_status
  • admin_level
  • plan_key
  • permissions_json
Simple account delete

Delete requests now live here. Select request, click the right button, type DELETE, done. No ID field. No email field.

No fake security

Admin/owner/platform-owner targets never show the delete path. They can only be declined/cancelled.

Audit + server boundary

User management writes stay in RPC. Real Auth deletion stays in the Edge Function.

Ready. Refreshing owner/admin state...

Users

Find user
Search pinpoints and scrolls to a user card.

Manage selected user

Set the intended values, then open Confirm Real Update. Leave fields as “keep” to avoid changing them.

Role
Submit privilege
Account status
Admin level
Plan
Admin notes
Permissions JSON
Select a user first.

Account deletion requests

This is the tested simple delete system. Admin/owner requests can only be declined/cancelled. Spare normal accounts can be deleted server-side after typing DELETE.

Request queue not loaded yet.

Audit log

No audit read yet.

Safety locks

Protected page lock

This page loads stream-bandit-protected-page-v7-12-273.js and uses the shared route map.

Owner/admin guard

User reads, profile writes and delete queue actions stop unless the signed-in profile is owner/admin/platform_owner.

No service role in browser

The browser uses only the publishable Supabase client and the signed-in user token.

No admin/owner delete

The UI blocks protected targets, and the Edge Function blocks them again server-side.

Profile RPC required

Profile writes go through sb_owner_manage_profile.

Real Auth delete boundary

Only sb-account-delete can remove a spare normal Auth user.

Debug

Waiting...