Permissions reference
Every permission in Bookitive — 23 organization-scope actions and 19 event-scope actions — with what each grants, plus the system-role grant matrix.
This is the complete catalog that custom roles are built from and that the system roles draw on. Two scopes: organization actions apply across the whole organization, event actions apply to one event (and cascade to all events when held through an org role).
Organization permissions
| Action | Grants |
|---|---|
org.view | See the organization and its basic details |
org.edit | Edit organization name and settings |
org.delete | Delete the organization and everything in it |
members.view | See the member list and their roles |
members.manage | Invite, remove and change roles of members |
roles.view | See roles and their permissions |
roles.manage | Create, edit and delete custom roles |
venues.view | See venues and their arrangements |
venues.manage | Create, edit and delete venues and arrangements |
events.view | See all of the organization's events |
events.create | Create new events |
events.delete | Delete events, including their orders and issued tickets |
billing.manage | Manage billing, payouts and subscription |
api.manage | Manage API keys and webhook endpoints |
devices.manage | Add, edit and revoke scanner devices at the doors |
customers.view | See the organization's orders and customer details |
customers.export | Export customers and their contact details |
protection.manage | Review held orders and manage anti-scalping rules and lists |
integrations.manage | Connect and disconnect third-party integrations |
sponsors.view | See the sponsor book, campaigns and outreach results |
sponsors.manage | Manage the sponsor book, deals, templates and campaigns |
sponsors.send | Send outreach and manage sending identities (SMTP) |
audit.view | See the organization's audit log |
Event permissions
Every action below can be granted in an event role (one event) or inherited from an organization role (all events).
| Action | Grants |
|---|---|
event.view | See the event and its details |
event.edit | Edit event details and settings |
event.publish | Publish the event and control its sale status |
seating.view | See the seating plan and seat statuses |
seating.edit | Edit the event's seating plan |
files.view | See and download the event's files |
files.upload | Upload files and manage folders |
files.delete | Delete the event's files and folders |
files.share | Create and revoke shareable download links |
files.collect | Create upload links and review submissions |
ticket_types.manage | Create, edit and delete ticket types and prices |
discounts.manage | Create, edit and delete discount codes |
orders.view | See orders and customer details |
orders.manage | Create and edit orders (box office) |
orders.refund | Refund and cancel paid orders |
checkin.scan | Scan and validate tickets at entry |
staff.view | See who has access to this event |
staff.manage | Grant and revoke event roles (scanners, box office) |
reports.view | See sales and attendance reports |
System roles at a glance
| Role | Scope | Grant summary |
|---|---|---|
| Owner | Org | All organization and event actions. |
| Admin | Org | Everything except org.delete and billing.manage. |
| Member | Org | org.view, events.view, sponsors.view, customers.view, event.view, reports.view — not customers.export. |
| Event manager | Event | Every event action, for one event. |
| Box office | Event | event.view, orders.view, orders.manage, reports.view — not orders.refund. |
| Scanner | Event | event.view, checkin.scan — nothing else, not even reports. |
Deliberate boundaries worth re-reading: refunding money (orders.refund) is
separate from running the box office (orders.manage); exporting personal
data (customers.export) is separate from viewing it (customers.view); and
audit.view is implied by no other permission — you grant the ability to read
the log explicitly or not at all.
Related
Custom roles
Build a role from the permission catalog when the system roles don't fit — organization-scope or event-scope, cloned or from scratch.
People directory
One merged view of everyone around your organization — members, event staff, and a saved roster — and how the roster lets you prepare people before granting access.

