Appearance
Team members & permissions
Colleagues work in your organization under their own sign-in, each with only the access you give them. Open Settings → Members in the left menu of the organizer app.
Seats
Pro includes 5 team members, Business 30, and Enterprise is unlimited. The owner does not use a seat; an invitation that has not been accepted yet does. The count is shown above the list, as Seats used / available.
Staff who only scan tickets at the door do not need a seat at all: they join a check-in device with a short code you approve. See Check-in.
Invite someone
- Choose + Invite member.
- Enter their Email and, optionally, a Display name.
- Choose a Role:
- Admin (all modules) — everything, across the events in their scope, except the masking permissions described below.
- Member (selected modules) — only the modules you tick. A member needs at least one.
- Choose an Event scope: All events (including ones created later) or Selected events, then pick the events.
- Send the invitation.
They get an email with a link. The link works once and expires in 7 days. Until they open it and accept under their own account, they have no access at all and show as Invited.
An invitation that has not been accepted cannot be edited. Choose Re-send to send a new link (the old one stops working), or Remove and invite them again with different access.
Role templates
Instead of ticking modules one by one, start from a template under Role templates and adjust:
| Template | For |
|---|---|
| Event manager | Day-to-day event work, without organization administration or integrations |
| Check-in staff | Scanning on site, nothing else |
| Guest & agenda editor | Speakers, agenda and venues |
| Ticketing | Tickets, the registration form, and adding, importing and exporting attendees |
| Sales | Sales channels, discount codes and viewing orders |
| Marketing | The event website, sharing, email and broadcasts, surveys and discount codes |
What the modules cover
Permissions are grouped by the part of the work they cover — the organization itself (creating events, members, the API and webhooks, contacts), event setup (details, website, tickets, payment accounts, form, venues, agenda, speakers, sponsors and exhibitors), people (viewing or managing orders and attendees, adding, importing, exporting), on site (check-in, self check-in, badges, collection points), promotion (discount codes, tracking, sharing, email and broadcasts) and content (surveys, dashboard and reports).
Two permissions work the other way round: Mask attendee email and Mask attendee phone hide those details from that person, in the console and in any API key they create. Use them for people who need to work with attendee records without seeing contact details. They can only be set on a Member; an Admin always sees contact details.
Change or remove access
Open an active member to change their role, event scope, modules, or Status — set DISABLED to suspend someone without removing them. Remove takes them out of the organization. The owner cannot be edited or removed here.
Related
- Check-in — door staff join a device with a short code, without a seat.
- Webhooks & API — needs the OpenAPI & webhooks permission.
- Pricing on bagevent.io — seats per plan.