Built-In Roles Explained
Understand Owner, Admin, Event Manager, and Viewer before giving people access to live event records.
Article guidance
Roles decide which pages a user can open and which actions they can take. The built-in roles give you a useful starting point, but you should still check whether a person really needs broad access.
Built-in roles
- Owner: full account control, including billing, package changes, team access, roles, account settings, payments setup, data exports, retention, and all operational areas.
- Admin: broad day-to-day operational access without automatically needing every owner-level billing and account-control task.
- Event Manager: suitable for staff who create and run events, review applications, manage participants, documents, payments, communications, site plans, stages, tickets, or transport where those permissions are included.
- Viewer: read-only access for people who need to look up information but should not edit records.
Important role details
- Built-in role names are protected so the account always has recognisable defaults.
- Permissions on roles affect the sidebar, available actions, module visibility, and API access.
- A feature can be available to the organisation but still hidden from a user whose role does not include a relevant permission.
- Owner-level access should be limited to people trusted with billing, account security, data export, and user management.