Community Infra — Events, Badges, Hosts, Referrals

    RBAC-first architecture with privacy-centric visibility.

    Decoupled role/badge logicClosed beta live
    PlatformCommunityPrivacy UX

    Overview

    Infra for communities to run events with assigned hosts, badges, and optional participant visibility.

    Context & Role

    Architect & PM; admin-only edits by design.

    Problem

    Role/badge coupling; visibility/privacy requirements; host workflows.

    Objectives

    Separation of concerns; admin-only edits; privacy by default.

    Product Decisions

    Badge system separate from roles; one host per event; admin assignment. Visibility flags enforced at API layer; no participant data sent by default.

    Solution

    RBAC model; visibility filters; Google Sign-In; preferences endpoint; storage-efficient activity logging.

    Architecture

    Supabase (RLS) + Next.js; endpoints for events/hosts/badges; admin console.

    Metrics & Impact

    Clean governance; beta usage across growing communities.

    Evidence

    ERD; RLS policies; privacy tests.

    Challenges

    Balancing visibility with privacy and safety.

    Lessons

    Make privacy choices backend-configurable and overridable.

    Tech Stack

    SupabaseNext.jsRBACAdmin tools
    Ping me