Roles & permissions
FightReg checks every action against a permission slug: 79 permissions in 24 modules, spread over 13 roles. On top of that, every staff member can receive individual per-competition rights beyond their role.
rolessystem.manageRole overview
A role is the basic equipment. For a single competition it is added via competition_staff — a trainer can run an area there for a day without losing their role. The number next to each role is counted, not estimated: it comes from role_permissions after install.php and all migrations.
Super Administrator
super_admin
Everything, platform-wide. The only role with system.manage and devices.manage — platform settings (AI, chat, voice, mail server, mandatory 2FA, self-registration, languages), organisers, devices and rentals, user management.
platform
Competition Admin
admin
A whole competition: categories, participants, brackets, areas, displays, announcements, billing including prize money, settings, team. Without system.manage, devices.manage, users.edit and without creating, deleting or copying a competition. If the account is bound to an organiser (partner admin), the role only counts in that organiser's competitions — see below.
base role · assignable per competition · competition
Tournament Office
tournament_office
The role between the admin and the specialist roles: registration and club approvals, categories, start lists and fight order, check-in, area assignment, screens, team and the tournament management's messages. No billing, no generating brackets.
assignable per competition · competition
Trainer
trainer
Registers the athletes of the club, maintains them, sees start lists, brackets, the fight plan and the club's own invoice — and creates the club's coaches. Sees a competition only if the club is registered there; otherwise only what is public.
base role · club
Coach
coach
The trainer's rights without the invoice: a coach looks after athletes on competition day but does not pay. Coaches are created by the trainer, not by another coach; a coach may accompany several clubs.
base role · club
Staff
staff
The base role of a pure team account — judging, check-in, announcements. It carries no permissions of its own: everything the account may do comes from its competition role in the respective event. The roles next to it are assigned per event only, not as base roles.
base role · no permissions of its own
Ring Manager
ring_manager
Runs an area — since the merge with the former head judge the most far-reaching role on competition day: edit, score and revert brackets, fight order, manage areas, run forms sessions, control screens. Does not generate brackets.
assignable per competition · competition
Judge
judge
Scores fights and forms at the area, sets area status and results, sees bracket, fight plan and start list. No changes to structure or master data.
assignable per competition · competition
Announcer
announcer
Runs the hall announcements: queue, target per announcement, halt and resume, voice and templates of this competition. Sees participants, start lists and brackets in order to announce them.
assignable per competition · competition
Check-in Staff
checkin_staff
Entry and weigh-in: call participants, check them, review documents — nothing else.
assignable per competition · competition
Billing
billing
View, edit and send invoices, maintain surcharges and discounts, statistics, calculate and release prize money — and print via the Print Agent.
assignable per competition · competition
Observer
observer
Watches and changes nothing: categories, participants, start lists, brackets, areas. The role for guests, press and federation representatives.
assignable per competition · competition
Participant
participant
The athlete's own account. The permission table holds almost nothing — what the athlete sees belongs to them and hangs on the account, not on a permission.
base role · own account
Permission matrix (sign-in required)
Which role carries which module and which individual permission — the module comparison and the list of all permissions — is shown in the permission matrix. Since sprint 213 it sits behind the sign-in and is reserved for event administrators and super administrators; the role descriptions above stay readable for everyone.
Three special cases
Federation admin
Is not in roles. Whoever manages a federation is listed in federation_admins — responsibility hangs on the federation, not on a role. Federation admins see all linked competitions on the federation pages, guests only the public ones.
Partner admin
A competition admin whose account is bound to an organiser. The base role only counts in competitions of that organiser; in someone else's competition only a tournament role assigned there applies. Platform settings, other organisers and other invoice issuers are out of reach. An admin without an organiser and the super administrator remain platform-wide.
Spectator
Is not a role but the absence of a sign-in. The live page, the hall plan and the area status of public competitions are deliberately open; start lists appear there only once the organiser releases them. Anyone signed in but not involved in a competition (club not registered, no start, no tournament role) sees exactly as much there as a spectator.
competition.view is not a permission but a membership marker: every role gets it and nothing checks it. It says "this role belongs to a competition" — in one place instead of 12 lists.As of sprint 318 · 2 Nov 2026