Modules overview

Modules overview

Use this page to quickly see all modules available in JudoManager and how they’re grouped. Modules are organized into functional groups (Register, Tools, Codes, Competitions, Commissions, Web). Access to each module is controlled with R/W/U/D permissions and is always scoped to an organization (country, region, or club).

#
MODULEGroup
1
Organisations
Register
2
Countries
Register
3
Register
4
Register
5
Register
6
Register
7
Register
8
Register
9
Register
10
Registrations
Register
11Register
12
Enforcement
Register
13
Cards
Register
14
Tools
15
ToolsTools
16
Messaging
Tools
17
Import data
Tools
18
Export data
Tools
19
Tools
20
Compute cup

21
Software modules
Tools
22
Software
Tools
23
Duplicates
Tools
24
Competitions Overview
Tools
25
Registration Periods
Tools
26
Statistics
Tools
27
External Sync
Tools
28
Tools
29
Weight Categories
Codes
30
Age Categories
Codes
31Coaches
Codes
32Functions
Codes
33Belts
Codes
34Referees
Codes
35
Cups
Codes
36
News types
Codes
37
ScoringCodes
38
Register competitors
Competitions
39
Competitions
Competitions
40
Rangs
Competitions
41
Register guest competitorsCompetitions
42
Events
Competitions
43
Referee commission
Commissions
44
Belt commission
Commissions
45
Coach commisions
Commissions
46
News
Web
47
Notifications
Web
48
Surveys
Web
49
Fragments
Web
50
Gallery
Web
51
Content
Web
52
Tags (#)Web
53
Competition organisation
Competitions
54
Import data V2
Tools
55
Analytics
Tools
56
Upload document
Tools

Category: register / countries

What the user CAN do:

• Can read info about countries (required R – READ).
• Create new countries (requires W – WRITE).
• Modify existing country data (edit a record in Countries) (requires U – UPDATE).
• Edit typical fields: country name, display name/locales, dialing code, time zone, flag/logo, default competition settings, contact metadata, visibility (active/inactive) — if not locked by policy (requires U – UPDATE).
• Save changes to one or multiple sections (general, formatting, competition defaults) (requires U – UPDATE).
• Delete countries (requires D – DELETE).

Category: register / provinces

What the user CAN do
• Can read info about provinces (required R – READ).
• Create new provinces (requires W – WRITE).
• Modify existing province data (edit a record in Provinces) (requires U – UPDATE).
• Edit typical fields: province name, code/abbreviation, ISO-3166-2, parent country, time-zone override, flag/logo, visibility (active/inactive), notes — if not locked by policy (requires U – UPDATE).
• Save changes to one or multiple sections (general, formatting, defaults) (requires U – UPDATE).
• Delete provinces (requires D – DELETE).

register / provinces — R: Read permission to view province list and details.
register / provinces — W: Write permission to add new provinces.
register / provinces — U: Update permission to modify province data.
register / provinces — D: Delete permission to remove a province.


Category: register / regions

What the user CAN do
• Can read info about regions (required R – READ).
• Create new regions (requires W – WRITE).
• Modify existing region data (edit a record in Regions) (requires U – UPDATE).
• Edit typical fields: region name, code/abbreviation, ISO-3166-2 (where used), parent province/country, time-zone override, visibility (active/inactive), notes — if not locked by policy (requires U – UPDATE).
• Save changes to one or multiple sections (general, formatting, defaults) (requires U – UPDATE).
• Delete regions (requires D – DELETE).

register / regions — R: Read permission to view region list and details.
register / regions — W: Write permission to add new regions.
register / regions — U: Update permission to modify region data.
register / regions — D: Delete permission to remove a region.


Category: register / clubs

What the user CAN do
• Can read info about clubs (required R – READ).
• Create new clubs (requires W – WRITE).
• Modify existing club data (edit a record in Clubs) (requires U – UPDATE).
• Edit typical fields: title/official title, international title, tax/ID number, location, street & number, city/postal, country & region, logo, contacts, visibility (active/inactive), notes/log — if not locked by policy (requires U – UPDATE).
• Save changes to one or multiple sections (Basic, Extra, Contacts, Logo) (requires U – UPDATE).
• Merge/mark duplicates (when feature is enabled) (requires U – UPDATE; may require elevated “Merge” right by policy).
• Delete clubs (requires D – DELETE).

register / clubs — R: Read permission to view club list and details.
register / clubs — W: Write permission to add a new club.
register / clubs — U: Update permission to modify club data (incl. logo, contacts; duplicates if allowed).
register / clubs — D: Delete permission to remove a club.


Category: register / schools

What the user CAN do
• Can read info about schools (required R – READ).
• Create new schools (requires W – WRITE).
• Modify existing school data (edit a record in Schools) (requires U – UPDATE).
• Edit typical fields: school type, title/official title, location, street & number, city/postal, country & region, logo, contacts, visibility (active/inactive), notes/log — if not locked by policy (requires U – UPDATE).
• Save changes to one or multiple sections (Basic, Contacts, Logo) (requires U – UPDATE).
• Delete schools (requires D – DELETE).

register / schools — R: Read permission to view school list and details.
register / schools — W: Write permission to add a new school.
register / schools — U: Update permission to modify school data.
register / schools — D: Delete permission to remove a school.


Category: register / registrations

What the user CAN do
• Can read info about registrations (required R – READ).
• Create new registrations for a person/season/type (requires W – WRITE).
• Modify registration details and status — edit type/season, add/remove notes, upload required docs, set status (Requested / Confirmed / Canceled / Expired), bulk Confirm all requested / Cancel all confirmed when enabled (requires U – UPDATE).
• Delete a registration (when policy allows and it’s not locked by usage; otherwise use Cancel) (requires D – DELETE).

register / registrations — R: Read permission to view registrations.
register / registrations — W: Write permission to add new registrations.
register / registrations — U: Update permission to change registration data and status (incl. bulk confirm/cancel if enabled).
register / registrations — D: Delete permission to remove a registration.


Category: register / enforcement

What the user CAN do
• Can read info about enforcement records (required R – READ).
• Update enforcement records — open “Show more”, edit details/notes, change status (e.g., Dirty / Not dirty / Resolved), assign owner, run Search duplicates, link/unlink related person/club (requires U – UPDATE).
• Delete enforcement records (where policy allows) (requires D – DELETE).

Notes
• Enforcement items are typically system-generated from data checks; manual creation is not supported (no W – WRITE).

register / enforcement — R: Read permission to view enforcement list and details.
register / enforcement — U: Update permission to modify enforcement records (status, notes, owner, link/unlink related entities, run “Search duplicates”).
register / enforcement — D: Delete permission to remove an enforcement record.
register / enforcement — W: Not applicable — enforcement items are system-generated (no manual create).


Category: tools/ questRequest

What the user CAN do
• Can read info about guest requests (required R – READ).
Process requests — create a user from a request, mark as processed, add an internal note/flag (requires W – WRITE).
Edit request details — fix name/email/club, (re)assign competition, update status/notes (requires U – UPDATE).
Delete a guest request (requires D – DELETE).

tools / guestRequests — R: Read permission to view guest requests.
tools / guestRequests — W: Write permission to process requests (create user, mark as processed, add notes).
tools / guestRequests — U: Update permission to edit request fields and status.
tools / guestRequests — D: Delete permission to remove a guest request.


Category: tools / reportedErrors

What the user CAN do
• Can read error reports (required R – READ).
• Update a report — add/edit reply, change status (Contact federation / Fixed / Declined / In progress), assign owner, link related entity (person/club/… ) (requires U – UPDATE).

tools / reportedErrors — R: Read permission to view reported errors.
tools / reportedErrors — U: Update permission to modify reports (reply, status, owner, links).


Category: code / ages

What the user CAN do
• Can read info about age codes/categories (required R – READ).
• Create new age codes/categories (requires W – WRITE).
• Modify existing age codes/categories — titles (per language), short tag/sex, age/Year ranges (Age to/from/min; Year to/from/max), match duration (seconds), order number, limited GS, visibility; manage Defined group categories and Defined special needs categories via Create actions (requires U – UPDATE).
• Delete an age code/category (requires D – DELETE).

code / ages — R: Read permission to view age codes.
code / ages — W: Write permission to add new age codes.
code / ages — U: Update permission to modify age codes.
code / ages — D: Delete permission to remove age codes.


Category: competitions / regcompetitors

What the user CAN do
• Can read competitions and registered competitors (required R – READ).
• Add competitors (cart → submit/checkout), register delegation/teams, print entry lists (requires W – WRITE).
• Modify entries — change category/weight block, coach, club slot, notes; move between time blocks; edit delegation/team members; resend confirmation; manage required docs (requires U – UPDATE).
• Remove/cancel entries (from cart or from the registered list), clear cart (requires D – DELETE).

competitions / regcompetitors — R: Read permission to view registered competitors and competition lists.
competitions / regcompetitors — W: Write permission to add/register competitors (cart + submit), delegation/teams.
competitions / regcompetitors — U: Update permission to modify existing registrations (category/coach/time block/team, notes, docs).
competitions / regcompetitors — D: Delete permission to remove/cancel registrations.


Category: competitions / competitions

What the user CAN do
• Can read competitions list and details (required R – READ).
• Create new competitions (requires W – WRITE).
• Modify competition settings (requires U – UPDATE), including:
– General: title, dates (from–to, deadline), country/city/venue, organizer, rank, visibility/publish, API user, files/attachments, “results/points” flags.
– Applies/ages & categories linking, entry limits, fees/notes/messages to clubs.
– Advanced/Timeblocks: create/edit time blocks, assign categories to blocks, open/close blocks.
• Delete competitions (requires D – DELETE).

Notes
• Managing competitor registrations (add/change/remove entries) is covered by competitions / regcompetitors permissions.

competitions / competitions — R: Read permission to view competitions.
competitions / competitions — W: Write permission to add new competitions.
competitions / competitions — U: Update permission to modify competition settings (general, applies, timeblocks, files, visibility).
competitions / competitions — D: Delete permission to remove competitions


Category: competitions / events

What the user CAN do
• Can read events list and details (required R – READ).
• Create new events — New event (Title, Dates, Applications till, Type, Location/Address/City, Country/Region, Visibility, Event confirmed) (requires W – WRITE).
• Modify event details — edit any of the above fields, attach/update files if enabled, toggle visibility/confirmation (requires U – UPDATE).
• Delete events (requires D – DELETE).

competitions / events — R: Read permission to view events.
competitions / events — W: Write permission to add new events.
competitions / events — U: Update permission to modify events.
competitions / events — D: Delete permission to remove events


Category: commissions / beltcommission

What the user CAN do
• Can read commission dashboard, candidates list, belt licenses, Events/Exams tabs (required R – READ).
• Add new belt license for a candidate (title/grade, date, related event, notes/files) and create commission events/exams if enabled (requires W – WRITE).
• Modify existing belt licenses — change grade/date/event, mark passed/not passed, update notes/files; edit commission events/exams details if enabled (requires U – UPDATE).
• Delete belt licenses and, if policy allows, remove commission events/exams (requires D – DELETE).

commissions / beltcommission — R: Read permission to view candidates, belt licenses, and Events/Exams.
commissions / beltcommission — W: Write permission to add belt licenses and create events/exams.
commissions / beltcommission — U: Update permission to modify belt licenses and edit events/exams.
commissions / beltcommission — D: Delete permission to remove belt licenses and events/exams.


Category: commissions / referee commission

What the user CAN do
• Can read referee commission data — lists, referee profiles, licences, delegation/events overview, PDFs (required R – READ).
• Add items (requires W – WRITE):
– Create a new referee licence (title/grade, date, place/event, validity).
– Add a delegation assignment for a competition (invite/assign a referee).
• Modify existing data (requires U – UPDATE):
– Edit referee profile details (contacts, address).
– Edit licences (title/grade, dates/validity, event/place, notes).
– Update delegations (assign/unassign, status such as invited/accepted, role/type, rating, notes).
• Delete items (requires D – DELETE):
– Remove a referee licence.
– Remove a delegation assignment.

commissions / referee commission — R: Read permission to view referee commission (profiles, licences, delegations, events).
commissions / referee commission — W: Write permission to add referee licences and delegation assignments.
commissions / referee commission — U: Update permission to modify profiles, licences, and delegation details/status.
commissions / referee commission — D: Delete permission to remove licences and delegation assignments.


Category: commissions / coachcommission

What the user CAN do
• Can read coach commission data — lists, coach profiles, competencies, License periods, Events, and Licenses tabs; export PDFs (required R – READ).
• Add items (requires W – WRITE):
Competence for a coach (title/level, date, note/points).
Event (seminar/training/exam) for coaches.
License period definition (valid from–to, title, period years, points).
Issue license to a coach (license period, number, issued on/by).
• Modify existing data (requires U – UPDATE):
– Edit coach profile contact details.
– Edit competencies (title/date/points/notes).
– Edit events (title, dates, place, files, points; mark passed/not passed).
– Update license period settings (validity, title, years, points).
– Update issued licenses (number, issued on/by, revoke/renew status if enabled).
• Delete items (requires D – DELETE):
– Remove a competence, event, license period, or issued license.

commissions / coachcommission — R: Read permission to view coach commission (profiles, competencies, periods, events, licenses).
commissions / coachcommission — W: Write permission to add competencies, events, license periods, and issue licenses.
commissions / coachcommission — U: Update permission to modify profiles, competencies, events, license periods, and issued licenses.
commissions / coachcommission — D: Delete permission to remove competencies, events, license periods, and issued licenses.



    • Related Articles

    • Navigation Overview

      ? Navigation Panel Overview After logging in, you’ll see the side navigation panel on the left, which gives you access to all key sections of the admin system. Here is a breakdown of each main menu group: ? REGISTER Used to manage all fundamental ...
    • Persons

      ? Persons The Persons section is the central place where all individual profiles of registered participants, coaches, referees, and other members are managed. Every person in the system is stored with personal details, club affiliation, registration ...
    • Add or Change User Permissions

      Use this guide to give a user access to specific modules in JudoManager (e.g., register / countries, competitions / events). Permissions are scoped to an organization (country, region, or club) and use four levels: R – Read = view lists and details W ...
    • Individual Competition

      ➕ Creating a New Competition Once logged in: 1. In the left-hand menu, click Competitions. 2. Click Competitions button. 3. Click the New competition Button. 4. ? Filling in Competition Details 4.1 Title – Enter the name of your competition. 4.2 ...
    • Special Needs Competition

      ➕ Creating a New Competition Once logged in: 1. In the left-hand menu, click Competitions. 2. Click Competitions button. 3. Click the New competition Button. 4. ? Filling in Competition Details 4.1 Title – Enter the name of your competition. 4.2 ...