Events permissions reference

This page lists the permissions that control access to events management features. Permissions are granted to roles in your organization by your organization owner.

To use any of these features, see the relevant how-to linked in each row.

Admin event management permissions

Permission	Who can do this	How-to
`events:write`	Create new events and publish draft events. Both the create and publish operations require this scope.	Create an event · Publish an event
`events:edit`	Edit event details (name, description, dates, location, tags, and registration settings) before and after publishing. Post-publish edits are gated by the product at the screen level — not by a separate scope.	Create an event
`events:cancel`	Cancel a published event and configure refund mode.	Cancel an event
`events:register`	Register a member for an event as an admin, including complimentary registrations with capacity override.	Register someone for an event on their behalf
`events:check-in`	Access the check-in screen and check in attendees by searching for them. (The screen does not scan QR codes yet.)	Check in attendees at an event
`events:check-in-undo`	Undo a check-in. This is a separate scope from `events:check-in` — a staff member granted only `events:check-in` cannot un-check-in.	Check in attendees at an event
`events:view-attendees`	View the Attendees tab with the full registration list, filter it, and see each registration’s details.	Manage and edit registrations
`events:edit-registration`	Edit a registration record (change ticket type, update form answers, modify registration status).	Manage and edit registrations
`events:message-attendees`	Send an email to a filtered group of attendees using the Email this group button in the Attendees tab.	Manage and edit registrations
`events:export-attendees`	Export the attendee list as a CSV file (name, email, ticket type, status, registration and check-in times). If this permission is limited to some membership levels or member tags, an attendee outside them has empty Name and Email cells; an Email cell also needs `members:read` covering that member.	Export the attendee list
`events:export-sensitive-fields`	Include sensitive columns (the registrant’s email) in an attendee export. Without this permission, a sensitive column is left out of the file and the export dialog says so.	Export the attendee list
`website:write`	Configure and embed the events calendar widget on an external website.	—

Notes

Permissions not shown here are not visible to that role in the admin panel — items are hidden, not disabled, when access is absent.
Organization owners hold all permissions by default.
Adding check-in staff for a single event isn’t available yet — the check-in screen has no button for it. Someone can check attendees in only if one of their admin roles includes events:check-in; reversing a check-in needs events:check-in-undo as well.