Assign tasks before inviting accounts
Decide who creates events, handles customer questions, reviews finance and scans admission. Use individual accounts rather than a shared password. Roles make the relevant screens and actions clearer. This explorer shows four examples without inviting anyone or changing actual permissions. It explains access and is not a management screen.
Agree a clear responsibility for each team member.
A scanner does not need order management
The scanner role is intended for event access and scanning, without general order or finance-management access. Finance staff have different capabilities, including viewing order and billing information. Event managers can work with events and orders according to their role. The matrix makes these differences explicit rather than giving everyone the same administrator account.
Choose the narrowest role that fits the task.
Combine organisation roles with scanning assignments
A role is not permission to use every entrance indiscriminately. Use event and scan-profile assignments to direct the door team. Profiles define accepted ticket types and assigned scanners. Also identify who handles exceptions: being able to scan does not automatically authorise someone to resolve a payment issue. Test the intended workflow using the actual staff account.
Test access using the intended staff account.
Keep team access current after the event
Review who still needs access when the edition ends. Committee changes, different responsibilities and completed engagements need appropriate team arrangements. Do not work around missing permissions by distributing full visitor lists. The demo uses fictional data; real access is checked by TixBeam and depends on the organisation and assigned permissions, not a selection in this preview.
Include access review in the next-edition handover.