FightReg Administration
Complete guide to setting up, running and wrapping up a tournament with FightReg.
Contents
- Initial Setup
- Roles & Permissions (RBAC)
- Create Competition
- Categories
- Manage Schools
- Participants
- Start Lists
- Brackets & Fight System
- Arenas & Mats
- Fight Order
- Check-in Management
- Screens & projectors
- Venue announcements
- Messages
- Billing & Invoices
- Mail Templates
- Staff & RBAC
- Ranking System
- Federations
- Settings
- System Module
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.
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)
| Role | Description | Typical 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
- Open the competition β tab "Staff".
- Search for a user or create a new one (OTP invitation by mail).
- Pick the role and override single permissions if needed.
- 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.
3. Create Competition
- Navigation β Competitions β "+ New competition".
- Enter the basic data: name, date, time, venue, max. participants.
- Assign organizer and invoice issuer β only the platform or the organizer's admin may do this (no foreign invoice issuer), not an event role.
- Set the registration deadline (after it, no coach self-service).
- Choose the event language and further languages (tab Languages); they must be among the platform languages.
- Set the tournament type for the ranking: regional / national / international.
- Save β the competition now appears in the list.
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
- Competition β Categories β "+ Category".
- Set name, discipline, age limits, weight limits, grade.
- Pick the bracket type: Single Elimination (KO) or Round Robin (everyone against everyone).
- Set max. participants per category (optional).
- Activate the partner/team flag for partner forms.
Merging categories
If a category has too few participants, two categories can be merged:
- Categories β choose "Merge".
- Pick source and target category.
- Confirm the merge β participants move to the target category, the merge history is logged.
Category status
| Status | Meaning |
|---|---|
open | Registration possible |
closed | Registration locked (by hand or after the deadline) |
running | Competition in progress |
completed | Finished β 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:
- Competition β tab "Schools".
- Find the school with status pending.
- Click "Confirm" β status becomes confirmed.
- 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.
6. Participants
Admins can view and edit all participants of all schools. In addition to the coach functions, these admin functions are available:
| Function | Description |
|---|---|
| Bulk invitation | Invite all coaches of a school by mail |
| Reset participant | Cancel the booking and remove the participant from the category |
| Set walkover | Mark a participant as winning or losing without a fight |
| Guest participant | Book in outside the normal registration |
| Assign athlete ID | Give 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
- Settings βΊ Event βΊ Competition Day: define the range under competitor numbers.
- 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
- Administration β Clubs, toolbar on the right, button Start numbers.
- Batch assignment per club: one button at the club header covers everyone entered.
- At the bottom of the dialog, Listing β the sheet for the coach: who wears which number.
8. Start Lists
Start lists show the order of participants per category on competition day.
- Competition β Start list.
- Pick the category.
- Adjust the order by drag & drop.
- Export as PDF (handout for the judges).
9. Brackets & Fight System
Generating a bracket
- Competition β category β "Generate bracket".
- Pick the type: Single Elimination (standard KO) or Round Robin.
- Check the seeding order (drag & drop of the participants).
- 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
| Setting | Description |
|---|---|
| Loser bracket | Activate the consolation round (3rd place fight) |
| Bye logic | Automatic bye for an odd number of participants |
| Result format | Configure 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.
- Competition β Arenas β "+ Create arena".
- Name the arena and add mats.
- Assign categories to mats (drag & drop).
- Set estimated start times per category.
- Status: pending β active β completed (can also be set by hand).
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
- Pick the aspect ratio of the hall, optionally add a background image.
- Drag mats from the tray on the left onto the map, rotate and resize them.
- Objects for everything that is not a mat: entrance, scales, awards, first aid, sales, toilets β with icon, image or sponsor banner.
- 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.
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.
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.
- Open the Area manager, pick the area and click "Assign" next to the referees.
- 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".
- A fixed seat applies on one area only; in the pool a referee may stand on several areas.
- 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".
- 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
- 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.
- Set the rotation interval per screen (default 30 seconds).
- Font size per screen β a projector in a large hall needs different values from a TV at the entrance.
- Per screen: hearing chip Announcements: off Β· ring Β· hall Β· all, "further areas", "Ticker for announcements" and Mirror of screen β¦ (see Venue announcements).
- Sponsor banner: default banner height 200 px; values already set stay.
Screen types
| Type | What it shows |
|---|---|
| Start screen | Name and logo of the event, when nothing else is running |
| Current fight | The 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 athlete | Who 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 screen | One 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 Order | The 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 β¦)" |
| Schedule | Time windows per area or a list by time; finished blocks drop out |
| Venue map | The 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.
- 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
- 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).
- "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.
- Templates β a default line per template and language (platform default or built-in default). Pronunciation rules apply to the whole platform.
- "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.
- "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.
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
- Push is off by default per event. Sending messages to coaches and athletes is a deliberate decision.
- It requires a VAPID key. Without one, every device subscription fails silently β check by requesting the public key.
- 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.
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.
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
- 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.
- Check the items.
- "Issue" β for the selection or all drafts. Outdated drafts are rebuilt first; issued documents stay unchanged.
- Send the invoice by mail or download it as PDF (event language).
storage/invoices/ and can be downloaded again at any time.Invoice status
| Status | Meaning |
|---|---|
| draft | Draft β not yet sent |
| sent | Sent by mail |
| paid | Paid (can be marked by hand) |
| cancelled | Cancelled |
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.
| Placement | What is sold | Record |
|---|---|---|
| Banner | Space: how often the logo appears per pass | no β a standing promise needs none |
| Spectator full screen | Time: seconds per impression, with a minimum gap | yes, per impression |
| Projector | Time, as its own page in the queue | yes, per impression |
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
- Download and install the agent. It is code-signed, so Windows SmartScreen stays quiet.
- 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.
- Several profiles per workstation are possible (A4 and receipt printer side by side).
- 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.
22. Mail Templates & CI
All automatically sent mails can be designed individually β per competition or globally.
Available mail types
| Type | Trigger |
|---|---|
| invitation | Coach/staff invitation (OTP link) |
| booking_confirmation | Booking confirmation for coaches |
| password_reset | Password reset link |
| invoice | Invoice by mail |
| participant_invite | Invitation 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.
- Competition β Staff β search for a user or create a new one.
- Pick the role (from the global role list).
- Optional: override single permissions for this user in this competition.
- The invitation mail is sent automatically (OTP one-time link).
- 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
- Competition β Ranking settings.
- Set the tournament type: regional (factor 1.0), national (1.5), international (2.0).
- Define points per placement (1st place = 100, 2nd place = 70 etc.).
- When a bracket is completed, the points are written to
athlete_rankingsautomatically.
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.
| Function | Description |
|---|---|
| Create federation | Name, logo, contact, parent federation (hierarchy) |
| Assign schools | Assign clubs to a federation |
| Link competitions | Assign tournaments to a federation (for the federation ranking) |
| Federation ranking | Ranking only within the federation's competitions |
| Federation admins | Separate 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
| Level | Where | Who |
|---|---|---|
| System (platform) | System βΊ Services βΊ Defaults, System βΊ Sign-up and curtain and others | super admin only |
| Organizer | Settings, group "Organizer" | admin of the organizer |
| Event | Settings, 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 data | Name, address, contact of the organizer |
| Invoice Issuer | Invoice data, bank, tax; the currency appears there as the organizer's default |
| Sender of the organizer, mail design (with mail logo) and mail templates of the organizer | |
| Services | AI and TTS keys of the organizer (masked, with a quota check); visible only to the organizer's admin |
| Payment methods | Payment methods offered: cash, bank transfer, card, PayPal, other |
| Defaults | Currency, corner colours, participant fields, receipt format β every event inherits them |
Settings βΊ Event β eight tabs
| Tab | What is there |
|---|---|
| General | Name and description per language, logo, venue; deleting the event |
| Dates | Dates of the event, cancellation lock (days before event) |
| Registration | Allow 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 |
| Billing | Currency, receipt printing, invoice abbreviation, invoice attachment; payment methods only as a display (the organizer chooses them) |
| Competition Day | Startlists released, competition finished, merge suggestion, federation, competitor numbers, practice copy; fights (corner colours, modes) and announcements as a link |
| Display/print | Date format, name display (privacy), screen curtain, column policy; QR code of the live page |
| Languages | Event language, competition languages |
| Services | Chat 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.
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.
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.
31. System Module (Super-Admin)
The system module is visible to super admins only (system.manage permission).
| Tab | Content |
|---|---|
| Users | List, deactivate, delete and create users |
| Roles | Edit system roles and their permission matrix |
| RBAC audit | Consistency check: code permissions vs. database permissions |
| Chat logs | View and delete the AI assistant log |
| Audit log | Trace all admin actions |
| Service Worker | View the cache version, force an update |
| Services βΊ Defaults / Levels | Platform defaults and table of all settings (see Settings) |
| Sign-up and curtain | Self-registration, second factor, curtain for all events |
| Devices | Inventory 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.