Preview
Your post title
Your zone update appears here.
Open public zone feedChecking your LocalLoop session and role.
Publish to an approved, live zone. Posts remain in the public zone feed until they expire.
Your zone update appears here.
Open public zone feedKeep your details up to date and choose your login code.
This replaces your account password. Use it with your email next time you sign in.
Launch the right LocalLoop workflow while keeping privileged decisions in their existing secured services.
Capture the listing, verify its location and details, then move it through the correct review path.
Bridge-draft pins and flagged public content use different schemas and must not be merged into one unsafe queue.
Control the zone cluster on a live map: pin the fan, toggle satellites, drag the Logo cluster, and save the new location.
Map unavailable — run npm run start:platform, set MAPBOX_PUBLIC_TOKEN=pk… in .env, then confirm /api/zones/map-config returns your public token.
—
Every geo-zone is Supa-Admin controlled by default. A Facebook group admin can claim the zone their group covers; on approval, day-to-day control transfers while Supa-Admin retains override.
Demo zone data falls back when the gateway is unavailable. Live zones, claims, and published marker positions load from Looper when signed in as admin.
Use the canonical capture and review surfaces rather than entering privileged data directly from this dashboard.
Collect category, address, business details, contact information, and map position.
Check ownership, location accuracy, payload source, and moderation state before publishing.
Verify the approved marker appears at the expected zoom and opens the correct customer action.
Card-pin approvals and flagged-content removals are different operations with different authorization contracts.
Approve or reject bridge-delivered drafts. Writes go through the Looper gateway, which verifies the JWT and server allowlist.
Open card-pin reviewThis console stays unpublished until its database fields and moderator RLS policies are verified. Client RBAC alone is not enough.
Schema and RLS requiredAdjust the plan ladder shown on the marketplace VIP card and dashboard, plus in/out fees. Saved per-browser (demo) until the Supabase pricing_settings table ships.
Kill switches, Explorer UI flags, and the signed-in role map. Use the narrowest tool that owns the task. Supa-admin never stores service-role credentials.
Server-enforced HybridCard flags (gateway + ADMIN_USER_IDS — this page grants nothing by itself). Every key returned by GET /api/flags is listed. Crypto stays locked until the ASIC review clears.
Runtime Explorer flags from this bundle (LL_FLAGS / ?ff=). Read-only here — they are not gateway kill switches.
Client UI gate from LocalLoopRBAC. Workers and RLS still authorize every privileged write.