Custom Roles

The five built-in sub-roles — Venue Manager, Box Office Agent, Marketing Manager, Finance Manager, Staff/Volunteer — cover most teams, but not always exactly. A custom role lets you build a permission set of your own and hand it to a team member instead.

What you can do here

• Create a role — name it, then tick permissions across modules like Events, Bookings, Tickets, Venues, Discounts, Campaigns, Marketing, Finance, Vendors, Staff, Reports and Analytics.
• Start from a preset — one click prefills the checkboxes from a built-in sub-role's permission set, which you then adjust. Presets only prefill once; changing what a preset means later never silently changes a role you already saved from it.
• Edit or delete an existing custom role.
• Assign it to a team member — from the invite form, or from the role dropdown next to an existing member on Team Settings.

How to build one

1. Open Custom Roles and give it a name, e.g. “VIP Host” or “Box Office Supervisor.”
2. Optionally click a preset to prefill from an existing sub-role, then adjust the individual boxes.
3. Tick a row's checkbox to grant every standard action for that module at once, or a column header to grant one action (View, Create, Edit, Delete...) across every module.
4. Some modules carry extras beyond the standard columns — Bookings adds Cancel and Refund, Tickets adds Check-in, Finance adds Payouts and Invoices, and so on.
5. Save. At least one permission is required.
6. Assign the role to a member from Team Settings or the invite form.

Good to know

• A custom role is a plain, explicit list of permissions — it does not inherit or keep tracking anything after it is saved. Editing what a preset means later never reaches back into roles you already built from it.
• Assigning a custom role to a member overrides their sub-role's default permissions entirely; the sub-role field itself stays on the member record and becomes the fallback again the moment the custom role is removed.
• Deleting a custom role does not remove the team members who had it — they simply revert to whatever their underlying sub-role grants by default.
• Custom roles belong to your organizer account, not to a single event — the same role can be assigned to members across every event you run.

Troubleshooting

• Save button rejects the form — a name is required, and at least one permission must be checked; an empty permission list isn't a valid role.
• A member lost access after I deleted a role — expected: they fall back to their sub-role's default permissions, which are usually narrower than a custom role built for them. Recreate the role, or assign a different one, to restore the wider access.
• I changed a role but a member's access didn't seem to change — check the Permissions screen for that member; if it still doesn't match, confirm they actually have this custom role attached rather than just the matching sub-role.

Related

• Team Management
• Organizer Settings