Skip to Content
HubIRL Help Center is live with mobile-first guides for members and admins.
Community Admin

Community Admin

Community admin surfaces live under Hub -> Admin and separate governance from event operations.

Governance vs Operations

Governance (usually OWNER/ADMIN)

  • hub settings and branding,
  • role management,
  • invite and join-policy control,
  • high-impact moderation decisions.

Operations (OWNER/ADMIN/MANAGER where allowed)

  • event creation and publishing,
  • ticket and attendance operations,
  • event updates,
  • event-day staffing/scanner workflows.

Use Roles and Permissions for exact boundaries.

Weekly

  • review join requests/invite health,
  • verify member share-link policy still matches your moderation posture,
  • review invite usage outcomes (joined, pending, no longer member) for anomalies,
  • verify readiness for upcoming events,
  • review moderation and incident queue.

Invite and Join Attribution Controls

  • Use Hub -> Admin -> Invites to create labeled invites with optional join messages and max-use limits.
  • Use Hub -> Admin -> Settings to control whether members can create tracked share links.
  • If members join from ?code=...&referrer=... URLs and need to sign in first, attribution is preserved after auth.

Before publishing each event

  • ticket policy and capacity confirmed,
  • required forms attached/published,
  • staff assignments and permissions tested,
  • event schedule and visibility verified.

Event day

  • scanner operators assigned,
  • form blockers resolved deliberately,
  • critical updates posted clearly,
  • attendance and incident logs monitored.

Post event

  • attendance and reconciliation reviewed,
  • refunds/voids resolved,
  • lessons captured for next event.

High-Risk Actions (Pause and Double Check)

  • changing community roles,
  • bulk member removal,
  • destructive moderation actions,
  • refund/void actions,
  • visibility changes on active published events.

If an Admin Action Fails

  1. Verify active hub context and your role.
  2. Verify event-scoped staff permissions if relevant.
  3. Confirm this is governance vs operations action.
  4. Capture exact error text + URL + UTC timestamp.
  5. Escalate with minimal reproduction steps.

High-Quality Handoffs

Use a consistent handoff note when shifts change or when support/ops takes over:

  • open issues and immediate risk,
  • actions already attempted,
  • decisions made and by whom,
  • next owner and escalation route.

Template: Support Playbooks.

Last updated on
Photos and PrivacyPlatform Admin