Rollare

Officials and access

Invite collaborators, scope referees and scorekeepers to their matches, and read the audit log.

Big events need more hands without handing over the keys. Rollare's access model has role-based invites plus per-match assignments.

Inviting collaborators

Invites are single-use links generated from the tournament's access settings. Each invite carries a role:

  • Owner — full control (that is you).
  • Member — organizer-level collaboration: roster, schedule, recording, settings.
  • Observer — read-only, including the organizer-side views.
  • Referee — records only matches assigned to them.
  • Scorekeeper — same as referee, for score-focused roles.

Invitees can decline; revoking a link kills it immediately, even if it was already forwarded. Each accepted invite appears in the collaborator list where you can adjust or remove access later.

Match assignments

Referees and scorekeepers work off per-match assignments:

  • Assign from the schedule — each match can carry a referee and/or scorekeeper.
  • Assignees are notified of their matches, and new assignments show up in their "my tournament" view.
  • Assignment is enforced: an invited referee opening the bracket can record only their assigned matches, other nodes are read-only for them.
  • The schedule grid also checks referee conflicts — double-booking, unavailable slots, and missing rest buffers — and offers an auto-assign mode that distributes matches across your officials. Referee availability (blocked dates, venues, windows) is configurable per official.

The audit log

Every organizer-side action — recorded results (including cascade clears), stage advances, registration reviews, access changes, settings edits, lifecycle events — lands in the audit log, visible to the owner and collaborators with manage rights. Each entry says who did what, when, with structured before/after details.

Use it to:

  • Answer "who recorded this score?" weeks later, without relying on memory.
  • Review the cascade impact after a mid-bracket correction.
  • Export the trail as CSV for post-event reports or dispute resolution.