Docs β€Ί Admin Manual
Admin Manual

FightReg Administration

Complete guide to setting up, running and wrapping up a tournament with FightReg.

πŸ“… As of sprint 318 Β· 2 Nov 2026 βš™οΈ Admin πŸ‘” Staff πŸ’Ά Billing πŸ” RBAC
Event Process β€” Overview Diagram
6 phases from initial setup to post-event wrap-up β€” as a printable SVG.
Open process diagram
βš™οΈ

1. Initial Setup

These steps are required once before the first tournament can be created.

Organizer profile

Enter the master data under Settings β€Ί Organizer β€Ί Master data:

  • Company name, address, logo
  • E-mail, phone, website
  • Tax ID / VAT ID (for invoices)

Invoice Issuer

Enter the invoice data under Settings β€Ί Organizer β€Ί Invoice Issuer. It is printed on every generated invoice (PDF). Several invoice issuers are possible (e.g. for different locations).

SMTP Configuration

The super admin configures the SMTP credentials under System β€Ί Services β€Ί E-mail. Use "Send test mail" to verify the connection.

⚠️
Without SMTP configuration, no invitation links, booking confirmations or invoices can be sent by email.

Create Super Admin

On first run, install.php automatically creates a super admin. Additional admins can be created under System β†’ Users.

πŸ”

2. Roles & Permissions (RBAC)

FightReg uses a fine-grained role model with 67 permission slugs in 14 modules. Every role has an individually configurable permission matrix.

System roles (standard roles)

RoleDescriptionTypical permissions
super_admin Full access to everything β€” system-wide settings, all competitions, user management All permissions
admin Event admin β€” with an organizer (partner admin) only in that organizer's events, see Tenant boundary All except system.manage
trainer Club representative β€” own participants, registrations, check-in participants.*, checkin.perform, startlists.view
staff Helpers on competition day β€” check-in, brackets, announcements checkin.*, brackets.score, announce.*
billing Accounting β€” billing area only billing.*
athlete Athlete β€” own data only, no admin functions Own profile, bookings
spectator Spectator / guest β€” read access to public areas only competition.view, brackets.view

Permission modules at a glance

competition

view, edit, create, delete, duplicate, stats, dashboard

categories

view, edit, merge, status

brackets

view, edit, generate, score, revert, settings, fightorder

checkin

view, perform, call, documents

billing

view, edit, send, surcharges, discounts, stats

announce

view, manage, speak, settings

participants

view, edit, enroll, documents

arenas

view, manage, assign, status, notify

settings / system

view, edit, ai, languages, mail Β· manage

Assigning staff to a competition

  1. Open the competition β†’ tab "Staff".
  2. Search for a user or create a new one (OTP invitation by mail).
  3. Pick the role and override single permissions if needed.
  4. Save β€” the user has access immediately.

Tenant boundary: who acts where

  • Partner admin (admin with an organizer) acts only in events of their own organizer β€” including the lists of clubs, accounts, participants, bookings and invoices, rankings, payout recipients, the competitor number stock and translations. In another organizer's event only through an event role held there. Other organizers and invoice issuers are neither visible nor editable. Accounts of other organizers are found only by the exact user name or e-mail.
  • Platform settings only for the super admin β€” AI, chat, TTS, SMTP, mandatory 2FA, self-registration, curtain, languages, platform mail design and templates, global certificate templates and ranking profiles. Reading the platform defaults remains allowed.
  • Coaches, corner coaches and athletes read an event only if they take part (club entered or starting there) β€” otherwise only what is public.
  • Organizer and invoice issuer of an event are changed only by the platform or the partner admin (own organizer, no foreign invoice issuer) β€” not by an event role with competition.edit.
  • Test mails go only to one's own address or an address of the organizer; the super admin is free.
  • API keys (AI, TTS) of the organizer are never delivered, only shown masked.
  • Daily cap β€” without an own key, a cap per organizer and day applies to the platform keys (default 200 voice outputs, 100 AI rounds). When it is reached, a notice appears; there is no usage display in the interface. With an own key there is no cap.
⚠️
Renew your keys: Until the security update, AI and TTS keys stored by organizers could be read by signed-in users through an interface. No misuse is known, but it cannot be ruled out; the gap is closed. If you stored your own keys: create new ones with your provider, enter them under Settings β€Ί Organizer β€Ί Services, delete the old ones with the provider and check the usage of the past weeks there.
βž•

3. Create Competition

  1. Navigation β†’ Competitions β†’ "+ New competition".
  2. Enter the basic data: name, date, time, venue, max. participants.
  3. Assign organizer and invoice issuer β€” only the platform or the organizer's admin may do this (no foreign invoice issuer), not an event role.
  4. Set the registration deadline (after it, no coach self-service).
  5. Choose the event language and further languages (tab Languages); they must be among the platform languages.
  6. Set the tournament type for the ranking: regional / national / international.
  7. Save β€” the competition now appears in the list.
πŸ’‘
Existing competitions can be duplicated β€” including all categories and settings. Ideal for event series.

Competition dashboard

The dashboard of a competition shows in real time: registered schools, participant numbers, check-in progress, bracket status and KPI charts.

πŸ“

4. Categories

Categories have two levels: main categories (e.g. "Kata") contain sub-categories (e.g. "Kata individual U12 female").

Creating a sub-category

  1. Competition β†’ Categories β†’ "+ Category".
  2. Set name, discipline, age limits, weight limits, grade.
  3. Pick the bracket type: Single Elimination (KO) or Round Robin (everyone against everyone).
  4. Set max. participants per category (optional).
  5. Activate the partner/team flag for partner forms.

Merging categories

If a category has too few participants, two categories can be merged:

  1. Categories β†’ choose "Merge".
  2. Pick source and target category.
  3. Confirm the merge β€” participants move to the target category, the merge history is logged.

Category status

StatusMeaning
openRegistration possible
closedRegistration locked (by hand or after the deadline)
runningCompetition in progress
completedFinished β€” results finalised
🏫

5. Manage Schools

Schools (clubs) are the organisational unit in FightReg. Every coach belongs to a school.

Approving a school for a competition

When a school registers for a competition, the admin has to confirm it:

  1. Competition β†’ tab "Schools".
  2. Find the school with status pending.
  3. Click "Confirm" β†’ status becomes confirmed.
  4. The coach can now enter participants.

School code (for the athlete ID)

Every school has a three-letter code (short_code) that becomes part of its members' athlete IDs. The code must be unique system-wide.

⚠️
A code once assigned should not be changed, otherwise existing athlete IDs become invalid.
πŸ‘₯

6. Participants

Admins can view and edit all participants of all schools. In addition to the coach functions, these admin functions are available:

FunctionDescription
Bulk invitationInvite all coaches of a school by mail
Reset participantCancel the booking and remove the participant from the category
Set walkoverMark a participant as winning or losing without a fight
Guest participantBook in outside the normal registration
Assign athlete IDGive existing participants without an ID one (bulk possible)
πŸ”’

7. Competitor numbers

Competitor numbers are physical bibs β€” a stock of roughly two hundred, reused every year. FightReg manages the stock, not a running number.

Setting up the stock

  1. Settings β€Ί Event β€Ί Competition Day: define the range under competitor numbers.
  2. States per number: free, assigned, lost, damaged. A damaged bib stays in the stock and is never handed out.

Assigning β€” before check-in, not during it

  1. Administration β†’ Clubs, toolbar on the right, button Start numbers.
  2. Batch assignment per club: one button at the club header covers everyone entered.
  3. At the bottom of the dialog, Listing β€” the sheet for the coach: who wears which number.
βœ…
If an athlete withdraws, their number is free again immediately. The number also appears on the participant card and on the scoresheet.
πŸ“‹

8. Start Lists

Start lists show the order of participants per category on competition day.

  1. Competition β†’ Start list.
  2. Pick the category.
  3. Adjust the order by drag & drop.
  4. Export as PDF (handout for the judges).
πŸ’‘
The start list is the starting point for bracket seeding. The manual order here determines the automatic bracket distribution.
πŸ†

9. Brackets & Fight System

Generating a bracket

  1. Competition β†’ category β†’ "Generate bracket".
  2. Pick the type: Single Elimination (standard KO) or Round Robin.
  3. Check the seeding order (drag & drop of the participants).
  4. Generate β€” the SVG bracket tree is created.

Single Elimination (KO tree)

Shown as an SVG bracket tree with interactive match cards (260Γ—72px). Features:

  • Zoom and pan (mouse + touch)
  • Enter the match result directly in the card
  • Winner highlight (green bar + winner badge)
  • Loser dimmed (50% opacity)
  • Seed numbers (β‘ β‘‘) and match numbers
  • Bracket exportable as PDF

Round Robin

Horizontal wizard with round navigation. Features:

  • Automatic table generation
  • Standings table in real time
  • Start the next round by hand
  • Completion β†’ placements are taken over into the ranking table

Bracket settings per competition

SettingDescription
Loser bracketActivate the consolation round (3rd place fight)
Bye logicAutomatic bye for an odd number of participants
Result formatConfigure points / technique / flags
🏟

10. Arenas & Mats

Arenas are areas in the hall (e.g. "Area A"); mats/rings are the actual competition areas within an arena.

  1. Competition β†’ Arenas β†’ "+ Create arena".
  2. Name the arena and add mats.
  3. Assign categories to mats (drag & drop).
  4. Set estimated start times per category.
  5. Status: pending β†’ active β†’ completed (can also be set by hand).
πŸ’‘
Brackets can be assigned directly to a mat. The main screen module then shows the current fight per mat.

Area and area manager

  • "Rest (fights)" in the dialog Edit area β€” how many fights a competitor rests at least between two of their own fights (empty = 2, 0 = no rule).
  • Delay β€” the Area manager and the area cards under Arenas show a delay chip and "Plan 10:00 Β· Actual 10:25"; the table "Area schedule" lists plan, actual (with delay) and state per category. While an area is running today, no waiting category starts before "now".
  • Shared categories β€” if a category also fights on another area, it appears there in the block "Split categories (fights here too)" with "(split)" and a link to its own area; its home area shows "(shared Β· also Ring 2)".
  • Areas in selection lists are sorted alphanumerically; venue map and assignment keep the order of the hall.
  • "Area thread" in the area manager opens the message thread of this area (see Messages).

Schedule

The tab Hall β€Ί Arenas β€Ί Schedule shows which category starts when on which area.

  • "Time windows" β€” tiles per area: one block per continuous period (frame, status bar running/upcoming/done, large time, codes as chips).
  • "By category" β€” sortable list; grouping as chips by main category, type or age group.
  • The icon button "Schedule on screen" sends it to a screen (screen type Schedule), "Print" creates the PDF in the event language: time windows in portrait per area, list in landscape per group.
  • Shared categories appear at their home area with "(shared Β· also …)".
πŸ—Ί

11. Venue map & mat occupancy

The venue map is the second route to the mats: the same data as the mat list, only spatial. Its own page and menu entry β€” the list view stays untouched and remains the route that reliably works on competition day.

Building the map

  1. Pick the aspect ratio of the hall, optionally add a background image.
  2. Drag mats from the tray on the left onto the map, rotate and resize them.
  3. Objects for everything that is not a mat: entrance, scales, awards, first aid, sales, toilets β€” with icon, image or sponsor banner.
  4. Save once. The editor does not write on every drag: rebuilding a hall would otherwise be fifty requests over venue Wi-Fi.

Where it appears on the day

  • Projector β€” as an item in the screen queue, with live status per mat.
  • Spectator phones β€” on the live page, their own mat in colour, the rest dimmed.
  • Printed notice β€” for the entrance.
ℹ️
The map belongs in the projector's rotation, not as a permanent image: a static venue map burns screen time that belongs to the fight in progress.

Screens and devices in the map

  • Fit (on by default) β€” editor and Assignment fit the map into the visible height without scrolling (from tablet width; not together with the rulers).
  • Map objects TV, Pi, Monitor β€” in the inspector "Hide on the screen" (on by default: the Venue map screen leaves the object out; map, assignment and overview show it dashed with an eye) and "Stands for" (a screen, a device or none). Linked objects carry name and contact dot.
  • Tray "Screens and devices" β€” with a contact light; dragging an entry onto an object in the map sets "Stands for".
  • Printing the notice β€” if the map has hidden objects, a dialog asks with the box "Print hidden objects too" (off by default); otherwise it prints at once.
  • Displays β€” button and layer in the map with a badge per area; a click opens the screen control or the Displays overview.

Assignment

  • Delay and actual times β€” a chip "Delay +25 min" at the list header, per row "Actual 10:25" when it differs from the plan. Start times follow the actual end of the fights, never earlier than planned and, once an area has a result on the same day, never before now.
  • "Areas per tier" β€” on fight categories: an area choice per tier; the line "Preliminary: Ring 2 + Ring 3 Β· Final: Ring 2" shows the split.
  • "Move running category" β€” with a question about the open fights; the category's pointer stays.
  • Split categories appear here and in the assignment PDF as "(split)" too.
  • Button Displays next to "To the screen" and a counter per ring card (icon, number, contact dot); a click opens the overview with this area first.
βš”οΈ

12. Fight Order

The fight order decides which fight takes place when on which area. The fight plan follows rules: blocks, tiers, rest, anchors.

How the fight plan is built

  • Blocks β€” one block row per main category or bundled block. In the dialog Main Category, "Fight order" (default / category by category / bundled) and "Block" set how its categories run.
  • Tiers β€” inside a block one row per tier (preliminary, semi-final …).
  • Rest β€” between two fights of the same competitor there are at least as many fights as the area sets under "Rest (fights)".
  • Anchors β€” dragging a fight sets an anchor at that position; the hints column shows it with "Release anchor". A fight cannot be dragged before its source.

The page

  • Columns # Β· Pos. (only after fixing) Β· time Β· code Β· category Β· round name Β· pairing Β· area (only without area filter) Β· hints Β· status.
  • Round badges before the code (e.g. SF, F, R1, BF = B-final for places 3/4), the long form in the category column; the round legend sits below the plan. Sections per round and category are framed as a group.
  • Hints β€” anchor, rest, collision (area and number) and deciding fight.
  • "More actions β–Ύ" β€” shuffle, undo, "Reset anchors" and "Fix numbers" (with a confirmation; locked with a reason). While the numbers still follow the position, a hint line says so; afterwards every fight keeps its fixed number.
  • "Other area …" at an open fight sends this one fight to another area; sources across areas then read "Winner of fight 3 (Ring 3)".
  • Round names follow one rule: round robin and Swiss are "Round n" (a round robin with only one round is the final), the deciding fight has its own name; KO says "Semi-final" instead of "Round 1".

The fight plan PDF follows the event language: a section per block, tier rows, round codes in square brackets before the category, hint symbols βš“ ⟳ ⚠ β˜… and a legend of the codes that occur.

⚠️
At the table, the current and the next fight show the chips collision and rest; the button "Move back" sets the anchor behind the next fights so the competitor gets their break.
βš”οΈ

13. Contact modes & fight scoring

Light contact and full contact are distinct modes β€” not two names for the same thing. They differ in how results are recorded, which is why the scoring form follows the contact mode of the category.

What gets recorded

  • Rounds β€” a score per round, not just a final result.
  • Flags β€” the judges' decision per round.
  • Judging panel per fight β€” who judged this fight is stored on the fight, not on the mat: panels change during the day.
  • Competitor number β€” printed on the scoresheet so the paper can be matched without asking.

At the judging table

A dedicated monitor shows the current competitor and their score β€” a view for the table, not for the hall. It opens separately and takes no room on the projector.

  • Fight scoring, the fight list and Next Matches of the area manager show the round as a badge; the announcement adds the round to the category.
  • After the round clock starts, the desk shows "Call queued" when the fight call at the start of a fight is switched on (see Venue announcements).
  • Names in the referee panel that have an account are links with "Message to …"; the button "Area thread" opens the thread of the area.

Referee panel: seats, pool and rotation

There is one panel per area. A separate panel per category no longer exists.

  1. Open the Area manager, pick the area and click "Assign" next to the referees.
  2. Seats of the fight scoring: head judge, ring judge and judges 1–3 (up to 5 with "Add judge"). Further referees go into the pool; dragging a name from the pool onto a seat puts them there. Each name shows "last seated …" and "Categories today: n".
  3. A fixed seat applies on one area only; in the pool a referee may stand on several areas.
  4. Rotation β€” when a category starts, fight scoring (or the forms page) opens "Referee panel for <category>" once by itself: fixed seats stay, free seats go to whoever from the pool has rested longest. Adopt seats them, "Later" closes; a line with "Propose panel" stays below. On the forms page the route is called "Propose from the area".
  5. Bias β€” nobody from a competitor's club is proposed; biased referees are marked. For that the referee needs a club: selectable under Team and when creating them; the referees' self-registration stores it.

The referee list PDF and the area card show the seats including the pool.

βœ…

14. Check-in Management

Check-in dashboard

The check-in module shows the check-in status of all participants in real time. Search by name, athlete ID or school. Status filter: all / not yet / checked in.

Checking documents

At check-in, uploaded documents (licence, medical certificate etc.) can be viewed directly and their status set (checked / missing).

Fight calls

From the check-in module, fight calls can be sent to participants by hand (they appear on the participant card as a push message).

πŸ“Ί

15. Screens & projectors

An event can have several screens, each with its own queue. The projector above the mat shows something different from the one at the entrance. A screen has a home area (or none = hall), can add further areas, mirror another screen and have a fixed device.

Setting up

  1. Screen control (Venue β€Ί Main Screen): create a screen and put together its queue. Hovering over the "+type" buttons (long press on a phone) shows a preview of the screen type with sample data; "?" opens the gallery "What does each screen show?" β€” a click there creates the type.
  2. Set the rotation interval per screen (default 30 seconds).
  3. Font size per screen β€” a projector in a large hall needs different values from a TV at the entrance.
  4. Per screen: hearing chip Announcements: off Β· ring Β· hall Β· all, "further areas", "Ticker for announcements" and Mirror of screen … (see Venue announcements).
  5. Sponsor banner: default banner height 200 px; values already set stay.

Screen types

TypeWhat it shows
Start screenName and logo of the event, when nothing else is running
Current fightThe running fight of an area with corners, points, time and round ("VK-65 Β· Round 3 Β· Fight 23"). Without an area binding and with several areas it shows the tiles like the hall screen.
Current athleteWho is competing right now, large and with club β€” for the monitor at the judging table; forms score with deduction ("8.40 (βˆ’0.3 time)")
Hall screenOne tile per area (1 / 2Γ—2 / 3Γ—2, from seven areas pages of six): fight with corner colours and round, forms competitor or "Start: approx. …". Fight clock, podium and announcement of an area lie only over its tile.
Fight OrderThe next fights: "#n Β· time Β· code Β· names", round badge before the code, sections per round and category framed as a group, chip "Next", round legend below
Arenas (board)All areas with their open categories, in groups per main category (header, time span, status bar, zebra rows); split categories with "(shared Β· also …)"
ScheduleTime windows per area or a list by time; finished blocks drop out
Venue mapThe venue map with live status per area; objects hidden on the screen are left out

In addition there are overlays you send to a screen: podium (remaining list as a grid; for forms with the final score per place and "TB …" where the tie-break decided), bracket, standings and the starter list of a forms category after finalising (forms page More β€Ί "Starter list on screen"). The target choice at the action button marks hall screens and does not preselect them. The Arenas and Schedule screens and the board fill the stage: the font grows with it, rings are sorted by name.

Overview Venue β€Ί Displays

The Displays page shows per area which screen runs there and which device shows it (ring ↔ screen ↔ device), with "Screens: n" and the weakest contact in the area header; plus "Screens without an area (hall)" and "Devices without assignment". The Displays button also sits at the ring table (forms desk), in fight scoring, the area manager, the assignment, the screen control and the venue map; without the right to manage screens the overview is view only.

  • Drag a screen onto an area β€” choice Set as home area or Add as further area.
  • Drag a screen onto another screen β€” after a confirmation it becomes its mirror ("Mirror β†’ screen …"): it shows the same. Chains of mirrors do not exist.
  • Drag a free device onto a screen card β€” assigns it to the screen; if the screen already has a device, FightReg asks and the old one becomes free.
  • Card "Objects in the venue map" β€” dragging a screen or device onto a TV, Pi or monitor object links it ("Link …").
  • "Assign to …" (or "Assign to screen …") is the same route with the keyboard or on a phone.

The display wall shows the hearing chip and "Mirror β†’ screen n" per tile.

Opening it

The screen runs without a login and is opened through a token in the address β€” whoever holds the link sees that one screen and nothing else. The machine at the projector needs no account.

ℹ️
Two things are easily confused: the projector in the hall and the live page on spectators' phones. Two audiences, two views β€” what runs on one does not automatically run on the other.
  • No dialogs on display pages β€” screens, devices and every tile of the display wall show no mandatory dialogs, no privacy notice and no maintenance message.
  • Reload after an update β€” after a new version, screen and display wall reload by themselves: with a random delay, never during an announcement or a running fight clock, at most once every ten minutes.

Ring displays and devices

A fixed device (such as a small computer at the area's TV) needs no screen link. It opens its own address #geraet/<key>; which screen runs on it is decided by the assignment in FightReg.

  • Waiting image β€” a device without an assignment shows a waiting image with its state ("available" or "waiting for assignment"). Show identity displays the identity on the device so you can see at the TV which one it is.
  • Assigning β€” in the screen control via the Devices button (only with a running or upcoming rental): per device contact light, screen choice, Show identity, at the top Show identity on all; "takes effect from …" while the rental has not started. Dragging in the Displays overview works too. A screen with a fixed device offers Show identity and In a new window in its access card instead of link and QR code β€” the device needs no link.
  • Rental β€” devices belong to the platform and are rented to an organizer (optionally to one event) for a period; only then can they be assigned. When the rental ends, the assignment is dropped.
  • Device health β€” the device chip in the screen control is coloured by the worse of contact and health; the device dialog shows the values (temperature, power and clock speed, free memory, free storage, running since start-up, display service).
  • Sound over HDMI β€” a ring display that listens speaks the announcements itself through the TV, without login and without a click (see Venue announcements).
  • "Connection lost – display not up to date" β€” this bar appears when a screen or device can no longer reach the server, with the time of the last state; when the connection returns, the display reloads.
  • "This address is no longer valid" β€” the screen was deleted or the device key renewed. Look up the current link in FightReg (screens or devices).

Inventory, rentals and device links are managed by the operator under System β€Ί Devices (see System Module).

πŸ”Š

16. Venue announcements

Announcements form a queue per event. They are not spoken in the announcer's browser but on the screens that listen to them β€” at the projector, at the TV by the area or on the ring display. Each event has its own queue and its own history.

Setting up

  1. Key β€” the TTS key belongs to the organizer (Settings β€Ί Organizer β€Ί Services). Without an own key the platform speaks with its own β€” with a daily cap (see below).
  2. "Voice of this event" under Announcements β€Ί Settings β€” with a default line: without a choice of its own the platform voice speaks; "Override" picks an own voice, "Use the default" takes it back. Only the super admin changes the platform voice below.
  3. Templates β€” a default line per template and language (platform default or built-in default). Pronunciation rules apply to the whole platform.
  4. "Fight call at the start of a fight" (on by default) β€” when the round clock starts for the first time, FightReg queues the call itself at the top, aimed at the fight's area. The desk shows "Call queued"; the announce button stays for repeating it.
  5. "Second language of the fight call" β€” selectable below. The first language is always the event language; "None β€” event language only" speaks just that. Applies to fight call and get-ready call.

Where an announcement goes

  • Target per announcement β€” an announcement about a category goes to its area, otherwise to the hall. The target chip on the queue entry switches between hall and the areas, on the category card of the announcement board even before queueing.
  • Fight calls go to the top of the queue.
  • Hearing per screen β€” in the screen control the chip Announcements: off Β· ring Β· hall Β· all sets what a screen speaks: ring = its areas and the hall (only with an area), hall = hall announcements only, all = every announcement. With "further areas" a screen also listens to additional areas.
  • One screen speaks an announcement β€” if several screens listen to the same target, one of them takes it. If no screen with fresh contact listens at an area, the board shows "No speaker for …".

On competition day

  • Status per entry β€” "running on …", "spoken: …", "error on …" with the name of the screen. The queue refreshes every five seconds.
  • Halt β€” Halt stops the queue for all screens; the bar "The queue is on hold …" stays until someone presses Continue. The screens show "Announcements paused" in their footer.
  • Ticker β€” announcements also run as text across the top of the screens that hear them (switch "Ticker for announcements" per screen in the screen control, on by default). The chip "Ticker" switches it off or on per queue entry.
  • Free text β€” target selectable (default hall), switch "Also as a ticker" (on by default).
  • "+N" on board and card opens a menu with one row per language and "Queue all N".
  • Get ready β€” the sentence comes from the server, in the languages of the fight call, aimed at the fight's area.
  • History per event; clearing it removes only your own event's history.

Sound on the device

  • The ring display on the device (#geraet/…, see Ring displays and devices) fetches its announcements itself and speaks them without login and without a click. Only what someone has queued is spoken.
  • A browser tab that opens the same device address without the device only displays: "This browser only displays β€” the device itself speaks the announcements."
  • Silent playback β€” if the browser or device blocks the sound, the notice bar offers "Enable sound"; the entry goes back to open and is spoken afterwards.
⚠️
Daily cap without an own key: if the event speaks with the platform key, a cap per organizer and day applies (default 200 voice outputs). When it is reached, a notice appears; there is no usage display in the interface. With an organizer's own key there is no cap. Recurring texts come from the cache and do not count again.
πŸ“£

17. Fight calls & push notifications

The fight call reaches coaches and athletes on their own phone β€” in addition to the announcement in the hall, not instead of it.

Switching it on

  1. Push is off by default per event. Sending messages to coaches and athletes is a deliberate decision.
  2. It requires a VAPID key. Without one, every device subscription fails silently β€” check by requesting the public key.
  3. Calls can be triggered automatically from the fight order or by hand.

Proof of delivery

Delivery is logged per device β€” sent is not delivered, and without a log nobody notices an expired subscription.

⚠️
On iOS only some devices hold a push subscription. For those participants the venue announcement remains the reliable route β€” the call does not replace it.
πŸ’¬

18. Messages from the tournament lead's view

Messages connect the tournament lead, areas, team and clubs on competition day. The organizer's admin counts as tournament lead, even without a team entry.

  • Thread kinds β€” direct, area, club, team and operator. FightReg creates area threads itself; a team member joins an area thread via "Join thread". The lead may delete area and club threads.
  • @-mention β€” with a picker in the input field. In area, team and club threads only those mentioned get a push; direct and operator messages push the other side.
  • Mark as done β€” a tick per message with name and time; thread filter "Open / Done / All" (default Open). "Reply" quotes a message.
  • Panel or window β€” on the right as a panel (full screen on a phone) or as a separate window "FightReg Β· Messages" with list and thread side by side.
  • Notifier β€” a large number for mentions and direct messages, also as an app shortcut.
  • "Area thread" in the area manager and fight scoring, "Message to …" on names in the referee panel and per team member under Settings β€Ί Team.
  • Coaches and corner coaches see only first name and role of the team and never write directly to other clubs.
ℹ️
Details on using it: User manual β€Ί Messages.
πŸ’Ά

19. Billing & Invoices

Price rules

Flexible price rules can be defined for every competition:

  • Base price per category/booking
  • Surcharges: e.g. "late booking +10%"
  • Discounts: e.g. "club member -5€"
  • Self-payer flag (separate invoice directly to the athlete)

Drafts and issuing

  1. Drafts are created automatically β€” from the first booking per payer (club or self-payer) and renew themselves with every change to bookings, price rules, surcharges or discounts. The state ("Drafts Β· 10:25") is shown on the left of the toolbar; "Update drafts" rebuilds them at once.
  2. Check the items.
  3. "Issue" β€” for the selection or all drafts. Outdated drafts are rebuilt first; issued documents stay unchanged.
  4. Send the invoice by mail or download it as PDF (event language).
πŸ’‘
Invoices are stored as PDF in storage/invoices/ and can be downloaded again at any time.

Invoice status

StatusMeaning
draftDraft β€” not yet sent
sentSent by mail
paidPaid (can be marked by hand)
cancelledCancelled

Deviation and difference document

  • Billing per payer above the document list: Target Β· Billed Β· Paid Β· Deviation, filter All / with deviation (n). The deviation counts only the entry fees of the categories; discounts, surcharges and special items stay as they were billed.
  • "Create settlement" per row (or More β–Ύ β€Ί "Settlements for all") β€” one difference document per payer: invoice, credit note or zero-value document, depending on whether entries were added, cancelled or only rebooked. Credit notes have their own number range.
  • An open credit note is paid out ("Record payout") or set off against an invoice ("Set off").
  • Document kind as a badge in the list: credit note, settlement, zero-value document. Clubs see credit notes like invoices, but not the deviation itself.
  • The phase Billed is reached only when nothing is open and bookings and documents match; otherwise it names the payers with a deviation.

Payment methods and currency

  • Payment methods are chosen by the organizer under Organizer β€Ί Payment methods (cash, bank transfer, card, PayPal, other) for all its events. The payment dialog offers only these; refunds and payouts stay free.
  • Currency β€” default of the organizer, can be overridden per event on the Billing tab. Every invoice keeps the currency it was issued in; drafts follow the event. With mixed currencies the key figures are marked and not converted.
  • Bank details in mails β€” if "Show bank details in mails" is on, the invoice mail adds account holder, IBAN, BIC and bank of the invoice issuer (not for credit notes).
  • If the event does not ask for membership, only price rules "All" apply β€” without a membership note and without a "Member" column.
  • Surcharges and discounts accept only payout recipients of the own organizer or the platform.

Prize money

Tab Billing β€Ί Prize money (right billing.prizes: super admin, admin, billing).

  • Pot β€” from income (payments received minus refunds and fees of other recipients) or as a fixed amount. "How the pot is made up" shows the derivation.
  • Three rankings β€” winners' places per category, individual ranking, club ranking; the three shares add up to 100 % (0 % drops a ranking). Only categories with a minimum number of competitors count.
  • Key per ranking in percent per place; default 40/30/15/15.
  • Per contact mode β€” individual and club ranking are split per contact mode, by default by the number of categories ("Split by categories"); points like the event's ranking or an own profile.
  • "Not paid out" with a check: paid out + not paid out = pot.
  • "Release" β€” after a confirmation a new version is created; it is frozen (income, categories, shares). Only then can it be printed.
  • "Take release back" β€” only with a reason (mandatory, kept in the history). The old version stays readable and printable; the next release is a new version.
  • PDF "Prize money payout list" (event language) β€” header with version, cut-off and release (taken back: "no longer valid"), pot, categories, individual and club ranking with a signature line per recipient, remainder and check.
🀝

20. Sponsors

Under Settings β†’ Sponsors. There are three placements, booked separately β€” the same company can run on one and not on another.

PlacementWhat is soldRecord
BannerSpace: how often the logo appears per passno β€” a standing promise needs none
Spectator full screenTime: seconds per impression, with a minimum gapyes, per impression
ProjectorTime, as its own page in the queueyes, per impression
ℹ️
The frequency counts per sponsor and per placement. Booking two placements yields twice the promised volume β€” not the same volume split in half. The organiser places, the contract sets the volume.
⚠️
The record counts only what ran in live operation. Setup and rehearsals do not belong on an invoice.
πŸ–¨

21. Printing: print agent, cards, lists

At the check-in desk every print dialog is in the way. The print agent is a small program on the workstation's Windows machine; the application hands it a finished PDF and it prints without a preview window.

Setting it up

  1. Download and install the agent. It is code-signed, so Windows SmartScreen stays quiet.
  2. Map printer roles in the agent: invoice, receipt, certificate, participant card. The application only ever knows the role, never the device name β€” replacing a printer is then a change at the workstation, not in the software.
  3. Several profiles per workstation are possible (A4 and receipt printer side by side).
  4. Receipt printers: set the role to Continuous. Width 0 means β€œfrom the driver” and is the normal case; enter a number only if the printout stops short.

What gets printed

  • Participant card β€” 85 Γ— 90 mm, two by three on A4, or from a receipt printer on an 80 mm roll. With athlete ID, competitor number and QR code.
  • Invoices and receipts β€” with the design of the issuing entity. At the cash desk the receipt prints by itself after β€œRecord payment” when the dialog shows From the print agent or Receipt printer. If the agent cannot print, the payment stays saved and the dialog says why in red β€” with Send to agent again and Print as A4/PDF.
  • Certificates β€” individually, per category or for a whole club.
  • Lists and notices β€” start lists, fight order, venue map.
ℹ️
Printouts follow the event language, not the interface language: the sheet hangs in the hall, and whoever reads it has never seen the interface. Names of categories, areas and fees are therefore required in the event language; German is a translation like any other, and the system adds English when saving (Sprint 290).
βœ‰οΈ

22. Mail Templates & CI

All automatically sent mails can be designed individually β€” per competition or globally.

Available mail types

TypeTrigger
invitationCoach/staff invitation (OTP link)
booking_confirmationBooking confirmation for coaches
password_resetPassword reset link
invoiceInvoice by mail
participant_inviteInvitation to athletes (athlete link)

Corporate Identity

Mail design and mail templates exist on three levels: platform (global), organizer (Settings β€Ί Organizer β€Ί E-mail) and event. The chain event β†’ organizer β†’ platform applies.

  • Upload a logo (shown in the mail header) β€” for the organizer under Organizer β€Ί E-mail β€Ί Design with preview and removal
  • Pick a colour scheme (predefined CI presets); below each colour and the footer a default line with "Use the default" β€” whatever is not overridden is inherited
  • Sender: "Sender of the platform (name)" under System β€Ί Services β€Ί E-mail, "Sender of the organizer" under Organizer β€Ί E-mail; the event's e-mail page only shows the sender (BCC stays there)

A test mail goes only to one's own address or an address of the organizer.

πŸ‘”

23. Staff Management

Every competition can have its own staff team with individual permissions.

  1. Competition β†’ Staff β†’ search for a user or create a new one.
  2. Pick the role (from the global role list).
  3. Optional: override single permissions for this user in this competition.
  4. The invitation mail is sent automatically (OTP one-time link).
πŸ”
The RBAC audit (System β†’ RBAC audit) checks whether every permission slug used in the code is correctly registered in the database.
  • Referees β€” club per referee selectable under Team (for bias); the panel of the areas is described under Referee panel.
  • "Message to …" per active team member under Settings β€Ί Team opens a direct message (see Messages).
πŸ‘₯

24. Corner coaches

A corner coach looks after athletes on competition day without seeing the club's invoice. They hold the trainer's rights without billing.view β€” they coach, they do not pay.

  • Created by the trainer, not by another coach.
  • A coach may accompany two clubs β€” which is why they hang off their own assignment rather than the trainer record.
  • It is a base role, not a competition role: they do not appear under a competition's "members".
πŸ…

25. Ranking System

FightReg calculates ranking points automatically when a bracket is completed.

Points configuration

  1. Competition β†’ Ranking settings.
  2. Set the tournament type: regional (factor 1.0), national (1.5), international (2.0).
  3. Define points per placement (1st place = 100, 2nd place = 70 etc.).
  4. When a bracket is completed, the points are written to athlete_rankings automatically.

Global ranking

The global ranking aggregates all results of all competitions. Under Ranking in the navigation you find the overall ranking β€” filterable by category, period and federation.

🌐

26. Federations

Federations can organise schools and competitions and keep their own rankings.

FunctionDescription
Create federationName, logo, contact, parent federation (hierarchy)
Assign schoolsAssign clubs to a federation
Link competitionsAssign tournaments to a federation (for the federation ranking)
Federation rankingRanking only within the federation's competitions
Federation adminsSeparate admins on federation level
πŸ”§

27. Settings

Every setting has exactly one home: the platform, the organizer or the event. What a level does not set itself, it inherits from the next one. Keys, bank details, tax and number ranges never exist per event.

Three levels and the inheritance chain

LevelWhereWho
System (platform)System β€Ί Services β€Ί Defaults, System β€Ί Sign-up and curtain and otherssuper admin only
OrganizerSettings, group "Organizer"admin of the organizer
EventSettings, group "Event settings"event admin, tournament office with the matching right

The lookup order is: event β†’ organizer β†’ platform β†’ server configuration (.env) β†’ program. The first value that is set applies.

Every setting that can be overridden shows a default line below it, e.g. "Default of the organizer: EUR" or "Built-in default: …". "Override" sets an own value for this level, "Use the default" takes it back. The same line appears in the mail design below each colour and the footer, for the announcement templates and for the voice.

Platform (super admin)

  • System β€Ί Services β€Ί Defaults β€” defaults for all events: name display, minimum age for an athlete account, retention of TTS announcements, and in the card "Competition Day" the forms timing ("Forms: seconds per starter", default 210 s). Each field names its origin ("Set for the platform." or the built-in default).
  • System β€Ί Services β€Ί Levels β€” table of all settings: home, can be overridden by, program default, right to change and "In force from" (platform, server configuration (.env) or program β€” only the origin, never the value).
  • System β€Ί Sign-up and curtain β€” self-registration, second factor and curtain for all events (see Access).
  • Mandatory columns (column policy) as a platform default.

Settings sidebar

  • Group "Organizer" β€” Master data, Invoice Issuer, E-mail, Services, Payment methods, Defaults. What is set here applies to all events of this organizer.
  • Group "Event settings" β€” This event (including participant fields and e-mail), Event (the eight tabs below), Manage categories, Fights, Ranking profiles, Team, Certificate Design, Sponsors.
Organizer β€Ί …What is there
Master dataName, address, contact of the organizer
Invoice IssuerInvoice data, bank, tax; the currency appears there as the organizer's default
E-mailSender of the organizer, mail design (with mail logo) and mail templates of the organizer
ServicesAI and TTS keys of the organizer (masked, with a quota check); visible only to the organizer's admin
Payment methodsPayment methods offered: cash, bank transfer, card, PayPal, other
DefaultsCurrency, corner colours, participant fields, receipt format β€” every event inherits them

Settings β€Ί Event β€” eight tabs

TabWhat is there
GeneralName and description per language, logo, venue; deleting the event
DatesDates of the event, cancellation lock (days before event)
RegistrationAllow self-booking for athletes, "Self-registration for this event", "Ask for membership", "Second factor required for tournament roles", medical certificates, documents at the check-in, minimum age for an athlete account; participant fields as a link
BillingCurrency, receipt printing, invoice abbreviation, invoice attachment; payment methods only as a display (the organizer chooses them)
Competition DayStartlists released, competition finished, merge suggestion, federation, competitor numbers, practice copy; fights (corner colours, modes) and announcements as a link
Display/printDate format, name display (privacy), screen curtain, column policy; QR code of the live page
LanguagesEvent language, competition languages
ServicesChat assistant, BCC of the e-mails as a link, data link
  • "Go to page" β€” settings with a page of their own (fights, participant fields, e-mail, announcements) appear in the tab only as a link with this button.
  • Save sits below the tab. Fields save anyway as soon as you leave them; the button saves everything at once.
  • Old addresses and bookmarks (venue, competitor numbers, data link) lead to the new tab.
  • The languages of an event must be among the platform languages, otherwise saving is refused.

Individual settings

  • "Ask for membership" (tab Registration) β€” asks at registration whether a club is a federation member. Off: no question, no membership note on invoices, only price rules "All" apply. Without a choice of its own: on if a federation is assigned; "Restore default" goes back to that.
  • AI and TTS keys sit under Organizer β€Ί Services, no longer with the event. They apply to all events of the organizer; without an own key the platform's applies (with a daily cap, see Tenant boundary). Only the organizer's admin may change them, not an event role.
  • Mail logo of the organizer β€” upload under Organizer β€Ί E-mail β€Ί Design, check it in the preview, remove it. The chain event β†’ organizer β†’ platform applies.
  • Fight call β€” the switch "Fight call at the start of a fight" and the "Second language of the fight call" are under Announcements β€Ί Settings (see Venue announcements).
  • Column policy β€” the platform sets mandatory columns; an event can override them on the Display/print tab. In the tables, mandatory columns appear ticked in the column menu and locked with a padlock, with their origin (platform or event); "Reset" leaves them in place.
πŸ”‘

28. Access: self-registration & one-time passcode

Self-registration

For all events under System β€Ί Sign-up and curtain (super admin); per event additionally "Self-registration for this event" on the Registration tab β€” it applies only while the platform allows it. When off, the register button disappears from the landing page and the organiser creates accounts. When on, clubs register themselves.

ℹ️
The lock works server-side, not just on the button: if the query fails, the answer is closed. A failure must not let anyone in.

One-time passcode as a second factor

Also under System β€Ί Sign-up and curtain: enforced for everyone or optional; per event "Second factor required for tournament roles" on the Registration tab. If the schema is not yet migrated, login behaves as before β€” here a failure must not lock anyone out. Same pattern as self-registration with the opposite sign, and both directions are deliberate.

🈯

29. Translations

Eleven languages. The language files are the base and the database layers over them β€” anything changed on the translation page takes effect immediately and survives every deployment.

  • Translation happens on the live system, not on a copy.
  • That work therefore lives in the production database first and should be exported back into the language files regularly.
  • Translators can be invited without an account of their own.
⚠️
English text in an English slot looks right even when it is untranslated. Gaps do not show up by looking β€” only by counting.
πŸ§ͺ

30. Demo and practice

Demo: For trials there is a separate installation at demo.fightreg.org with fixed role accounts (credentials on its login page) β€” among them "leitung_demo" for the tournament office, with sample messages. It is reset every night, and the operator can also reset it by hand under System β€Ί Operation β€Ί Maintenance mode (at most once every ten minutes); no mail leaves it. The AI assistant and voice announcements run there on the platform key and therefore under the daily cap β€” the login page shows β€œAI today N of M Β· Voice today N of M”. Instead of the consent dialog the demo shows the notice "This is the demo …" with "OK"; nothing is kept. The demo cup comes with areas and referee panels (head, ring, judges, pool), a hall screen and a ring display at Ring 1. Since Sprint 268 fightreg.org has no demo competitions and no demo accounts.

Practice copy: Under Event β€Ί Settings an event can be copied for practice β€” optionally with schools, participants and bookings. The team rehearses check-in, weigh-in, brackets, fights and screens in it; afterwards Discard practice removes the copy with everything created in it. The real event and the participant records stay untouched.

Export for the box: Under Event β€Ί Settings β€Ί Competition Day the admin exports his own event for the competition-day box (right competition.box_export: super admin, admin; since Sprint 326). The export freezes the event, the trial run does not. Loading it on the box stays with the operator.

⚠️
Nothing leaves a practice. No mail to coaches or schools, no invoice, push only to the practice team. A practice is never public and carries the badge PRACTICE in the top bar and on printouts.
πŸ–₯

31. System Module (Super-Admin)

The system module is visible to super admins only (system.manage permission).

TabContent
UsersList, deactivate, delete and create users
RolesEdit system roles and their permission matrix
RBAC auditConsistency check: code permissions vs. database permissions
Chat logsView and delete the AI assistant log
Audit logTrace all admin actions
Service WorkerView the cache version, force an update
Services β€Ί Defaults / LevelsPlatform defaults and table of all settings (see Settings)
Sign-up and curtainSelf-registration, second factor, curtain for all events
DevicesInventory and rentals of the fixed display devices (below)

System β€Ί Devices

  • Inventory per case: label, kind, serial number, state (ready, to be checked, defective, retired), light "Last contact" (green, yellow, red, grey = never connected) and below it the reported device health (on a phone only when there is a warning). Actions: Edit, Duplicate, Copy link (device link), Show identity, New key β€” the old link stops working at once.
  • Device dialog with the block "Device health" (otherwise "no report yet") and History (log). A device that has been rented before is not deleted but retired.
  • Rentals β€” running, upcoming, past. New rental: organizer, optionally event, first and last rental day, devices by case ("whole case"; occupied and not ready ones locked with a reason), note. Return ends the rental at once; deleting only before it starts. If an event is deleted, its rentals end as returned.

Probe mail

The daily check of external services tests the mail server with an SMTP handshake; a real probe mail goes out on Mondays, after an error, after a week or on demand. System β€Ί Services shows "Handshake ok Β· last probe mail …".

πŸ€–

32. AI Settings

Chat assistant, coach chat, AI help and AI translation run on one of three providers. Set up under System β€Ί APIs β€Ί AI (card AI translation and card AI chat assistant); key, model and base URL are stored per provider, so switching back loses nothing.

Anthropic Claude

Default provider. Model: claude-sonnet-4-20250514. Tool use for database queries.

OpenAI

Alternative provider β€” interchangeable. Same tool definitions.

OpenAI-compatible (e.g. TensorX)

Any server with the OpenAI interface. In addition the field Base URL (e.g. https://api.tensorx.ai/v1, without /chat/completions). Only https and publicly reachable hosts are allowed β€” no internal addresses, no credentials in the URL.

Model, load models, test

Load models asks the provider with the saved key for its models and offers them in the model field (save first). Test asks one question without and one with a tool: it shows whether the model really calls tools β€” without that, data and actions in the chat do not work.

Model for the AI help (below the daily limit): the help has only two read-only tools and many calls β€” a small model is enough. Empty = chat model; it applies only while the chat assistant uses the same provider.

Per organizer (Settings β€Ί Organizer β€Ί Services): own key for AI and voice output; it applies to all events of the organizer. Without an own key the platform's applies β€” with a daily cap (see Tenant boundary). Stored keys are never shown again, only masked.

Chat logs under System β€Ί APIs β€Ί AI β€Ί Logs.

πŸŽ“

33. Certificates

FightReg generates individually designed certificates for placements and participation β€” as print-ready PDFs with a QR verification code.

Template Designer

Under Settings β†’ Certificates β†’ Template Designer (URL: /certificate-designer) you create visual certificate templates:

  1. Select preset β€” templates for placement or participation, portrait/landscape (A4/A5).
  2. Position elements β€” drag & drop on canvas: text fields, athlete name, category, placement, date, logo, winner image.
  3. Accent colour & fonts β€” primary colour and font size adjustable per element.
  4. Preview β€” real-time PDF preview with sample data.
  5. Save β€” template is stored under a name and available for assignment.
πŸ’‘
Undo: Ctrl+Z, or DEL key to remove selected elements. Language of category labels (DE/EN) switchable via toggle.

Template Assignment

  1. Competition β†’ Certificates β†’ select template.
  2. Optionally: category-specific template overrides competition-level template.
  3. Templates can be duplicated and customised.

Generating Certificates

ActionDescription
Single placement certificateCompetition β†’ Category β†’ Participant β†’ "Certificate (Placement)"
Single participation certificateCompetition β†’ Category β†’ Participant β†’ "Certificate (Participation)"
Bulk: all placedCompetition β†’ Certificates β†’ "All Placement Certificates (PDF)"
Bulk: all participantsCompetition β†’ Certificates β†’ "All Participation Certificates (PDF)"
Bulk: completeCombined PDF with placement + participation certificates
⚠️
PDFs are generated server-side with TCPDF and provided as a download. Large bulk exports may take a few seconds.

QR Verification

Every certificate contains a QR code pointing to /verify/{uuid}. Anyone can verify the authenticity of a certificate via this URL β€” without login.

πŸ”’
QR codes are generated locally via the internal /api/qr endpoint (no external service β€” GDPR-compliant).
πŸ“

34. Forms & Kata Scoring

For kata and forms categories (technical scoring by judges), a dedicated scoring system is available β€” independent of the KO/Round Robin bracket.

Create Scoring Session

  1. Competition β†’ Forms β†’ "+ New Session".
  2. Select category (must have type forms or kata).
  3. Assign the area β€” the panel comes from the area's seats (rotation, see Referee panel).
  4. Import start order from start list or adjust manually.

Conducting Scoring

Each judge scores via /judge (separate tablet view, no navigation):

  1. Enter session code or open via QR link.
  2. Select current participant.
  3. Enter score (configurable decimal format, e.g. 8.5–10.0).
  4. Submit β€” visible in real time on the admin overview.
πŸ’‘
The judge view (/judge) loads no global JS β€” no session timeout, optimised for tablet use.

Results & Finalisation

FunctionDescription
Live overviewAdmin sees all scores in real time (average, individual marks)
Intermediate rankingSorted by average score at any point
Finalise sessionFreeze results β€” ranking fixed, certificates unlocked
Reset sessionDelete all scores and restart (only before finalisation)
NotesFree-text notes per participant for judges

Deduction and bonus "Β±"

  1. Choose "Β±" in the competitor's row.
  2. Set the value in steps of 0.1 between βˆ’1.0 and +1.0; a reason is mandatory (time, weapon, equipment, conduct, other), a note is possible. Add several deductions up and enter them as one value.
  3. The value is applied to the final result; the final standing shows it with its reason, e.g. "(βˆ’0.3 time)" β€” on the screen too.
  4. Until finalising it can be taken back; afterwards it is locked.

The result list PDF (event language) has a column "Deduction" with the reason; the certificate shows only the final value. The forms result list is a grid of place Β· medal Β· name Β· points.

Partner forms

For partner and team forms all members ("A & B" or one per line) appear on screen, podium, scoresheet, start list, result list PDF and certificate. The announcement does not name members who have opted out of AI use of their name.

Category Setup for Forms

When creating the category, select type forms (instead of fight). Forms categories appear automatically in the Forms tab and do not create a KO bracket.

As of sprint 318 Β· 2 Nov 2026