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

Roles and Permissions

This guide explains what each role can do and why some actions are intentionally restricted.

Community Roles

RoleMain UseKey PowersKey Restrictions
OWNERFinal authorityFull control, ownership transfer, destructive actionsCannot leave while still owner
ADMINGovernance operatorSettings, branding, roles, invites, moderationNo ownership transfer
MANAGEREvent operations leadEvent lifecycle, tickets, attendance ops, updatesNo full hub governance
MEMBERStandard participantJoin events, hold/transfer tickets, chat where allowedNo admin controls

Event Staff Permissions (Event-Scoped)

Event staff can be assigned explicit permissions per event, such as:

  • SCAN_TICKETS
  • VIEW_ATTENDEE_LIST
  • EDIT_EVENT
  • MANAGE_TICKETS
  • ISSUE_COMP_TICKETS
  • OVERRIDE_CONSENT

This allows event-day delegation without granting full hub governance.

Who Should Have Which Role?

  • Use OWNER for very small trusted count.
  • Use ADMIN for people responsible for hub governance.
  • Use MANAGER for reliable event operators.
  • Use event staff permissions when someone should operate one event only.

Practical Capability Matrix

CapabilityOWNERADMINMANAGEREvent Staff (with permission)
Hub branding/settings/rolesYesYesNoNo
Hub invite governanceYesYesLimited by policyNo
Event create/edit/publishYesYesYesLimited
Ticket operations/refunds/compsYesYesYesLimited
Scanner validationYesYesYesYes (SCAN_TICKETS)
Consent override at scannerYesYesNoYes (OVERRIDE_CONSENT)

Why You Sometimes See 404 Instead of 403

HubIRL uses privacy-by-default for sensitive resources:

  • 404 can mean “not found” or “not allowed to know this exists”.
  • This prevents existence leakage of private hubs, events, and records.

Permission Debug Checklist

  1. Confirm active hub context.
  2. Confirm your hub role in that hub.
  3. If event-scoped, confirm event staff permissions.
  4. Confirm whether route is governance-level or operations-level.
  5. Capture URL + role + exact error text if still blocked.
Last updated on