Teams and roles.

Everything in the platform belongs to a team: your events, your venues, your guest lists, your saved question sets. Understanding teams explains why something you can see is not something you can change.

What a team owns

A team owns:

• every event, and through it every schedule, ticket tier, guest, terminal and attendance record
• every saved location
• every fieldset of registration questions
• every export file generated from its events

Nothing is owned by a person. When someone leaves, their work stays with the team.

Switching teams

The selector at the top of the sidebar decides which team you are working in. Switching teams switches every list on every page: a different events list, a different set of locations, different fieldsets.

If something you expected to see is missing, check the team selector before anything else. It is the most common explanation.

You can belong to as many teams as you are invited to. A freelancer running events for three clients might keep one team per client, which keeps the guest lists cleanly separated.

The three roles

Every member of a team holds one role.

Administrator (full access) can do anything: create and change events, manage guests and check-ins, invite and remove people, change other members' roles, edit team settings, and delete events that have never had a guest. Ownership transfer is an administrator action.

Editor (create, read, update) can create and change events, tiers, schedules, guests and terminals, and run the door. They cannot manage the team itself: no inviting, no role changes, no team settings.

Member (read-only) can see the team's events and their data but cannot change anything. This is the role for a client who wants to watch registrations come in, a sponsor who wants the numbers, or a volunteer who only needs to look things up.

Choosing roles for an event crew

A sensible default for a small team:

• You and your co-organiser: administrator.
• Anyone building events or working the guest list: editor.
• Door volunteers, clients, sponsors: member.

Roles are per team, not per event. If someone should only see one event, the cleanest way is a separate team for it.

Team settings

Under Team Information in team settings you can update the team's name and its logo. The name is what appears in the team selector and on the events created under it.

What a team cannot do

Teams do not nest, and there are no per-event permissions. A member of a team can see all of that team's events. When you need a harder boundary, make another team.