Good operations start with a clear handoff.
Launch the right LocalLoop workflow while keeping privileged decisions in their existing secured services.
Onboard a business onto the map
Capture the listing, verify its location and details, then move it through the correct review path.
Moderation stays separated
Bridge-draft pins and flagged public content use different schemas and must not be merged into one unsafe queue.
Block admin marker
Control the zone cluster on a live map: pin the fan, toggle satellites, drag the Logo cluster, and save the new location.
Map unavailable — Mapbox token is not configured.
Operate the same marker used on the public map
Drag the Logo cluster on the map to move a zone. Select a row below, then Save position to publish that zone to the public map. Satellite toggles persist in this browser.
Lng / lat appear after the marker loads.
- Select a zone in the list, drag the Logo cluster on the map, then Save position.
- Satellite clicks still open Block totals when the public map news panel is present.
- The older platform pin remains a separate layer.
Postal zones default to Supa-Admin until claimed.
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.
Move a listing from intake to map.
Use the canonical capture and review surfaces rather than entering privileged data directly from this dashboard.
-
1
Capture the listingOpen onboarding
Collect category, address, business details, contact information, and map position.
-
2
Verify the submissionOpen pin review
Check ownership, location accuracy, payload source, and moderation state before publishing.
-
3
Confirm it on the mapOpen public map
Verify the approved marker appears at the expected zoom and opens the correct customer action.
Keep each review queue honest.
Card-pin approvals and flagged-content removals are different operations with different authorization contracts.
Pending HybridCard pins
Approve or reject bridge-delivered drafts. Writes go through the Looper gateway, which verifies the JWT and server allowlist.
Open card-pin reviewFlagged public content
This console stays unpublished until its database fields and moderator RLS policies are verified. Client RBAC alone is not enough.
Schema and RLS requiredHeartBeat tiers, transaction fees & gateways
Adjust 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.
Operational entry points
Use the narrowest tool that owns the task. Supa-admin never stores service-role credentials.
Feature flags
Server-enforced kill switches (gateway + ADMIN_USER_IDS — this page grants nothing by itself). Crypto stays locked until the ASIC review clears.