Configure

Configure is where the event gets built before it becomes a live show. Good configuration keeps the show pages simple.

The setup model is opinionated:

1. Organisations and people decide who exists.
2. Event creation establishes the owner, host, creator access, and a resumable setup checklist.
3. Participation decides which organisations are part of the event.
4. Modules decide which tools the event uses.
5. People and access decide who can enter the event and which named role they have.
6. Event Control settings decide how logs behave.
7. Mapping configuration decides what the map shows.
8. Audit helps you check what changed.

Best practice

Start with a person and a named role. Use reusable-role configuration when a repeated job needs a new permission set, and module-specific roles for genuine exceptions. This keeps show-day access easier to explain and review.

Platform Admin

Platform Admin uses many of the same screens as Configure, but with wider scope. Large organisation, event, collection, membership, and user selectors are searchable and paged. Platform support actions that cross normal access boundaries ask for an audited reason.

Before show day

Run a rehearsal. Open the live Event Control page, create a test log if the event policy allows it, check the map, open documents, and confirm the export page. If a user cannot see a page, fix module status or access before the show starts.