Skip to main content

Event access

Event access decides who can use each module for an event.

DesktopConfigure event access desktop view
MobileConfigure event access mobile view
Access is split into reusable role bundles and direct people roles.

Start with role bundles​

Role bundles group permissions into something humans can understand: Event Admin, Event Control Controller, Mapping Viewer, Document Editor, and similar patterns.

Use bundles when several people need the same access. Assign the bundle to the person or membership, then review access from the overview.

Best practice

Bundles are the default. They are easier to audit, easier to remove, and easier to explain at 8am on show day.

Use direct module roles for exceptions​

Direct module roles are for one-off cases. For example, a single person from a partner organisation might need Mapping Viewer without giving that organisation a broader bundle.

Use them sparingly. If you assign the same direct role more than a few times, create a bundle instead.

Event, collection, and platform scope​

Access can be scoped to an event, a collection, or wider platform administration depending on the screen and your own permissions.

  • Event scope is safest for live show access.
  • Collection scope works when a series genuinely shares the same access model.
  • Platform scope is powerful and should be reserved for trusted administrators.
caution

Platform Admin can see and change more than a normal Configure user. Add a clear reason when the UI asks for one, and avoid using platform scope as a shortcut for event setup.