Administrator Screen Reference

Global screens

These screens are available from the JoomLeague component menu and are not limited to one project.

Dashboard summarises installed profile/catalog and competition data, highlights incomplete programme items for the configured site club and links to the normal setup workflow.
Sport Profiles synchronises and lists immutable bundled JSON profile versions. It does not directly create runtime positions or statistics.
Sport Types creates the installation-specific sport definition from a selected profile version and optionally initializes its catalogs.
Competitions stores reusable competition identities.
Seasons stores reusable labels; exact date bounds are optional.
Projects lists operational competition editions. The project-name link opens Project Panel; the separate edit icon opens project settings.
Clubs, Teams, Persons and Venues manage reusable reference entities and their media/details.
Positions, Events and Statistics manage sport-type-scoped runtime catalogs. New/custom records are permitted even when profile defaults were not initialized.
Templates configures global presentation defaults separately for every sport profile.
Custom Fields opens Joomla's native field manager. Six independent contexts are available for projects, clubs, teams, people, venues and programme items; see Custom Fields.
Tools groups data exchange and maintenance entry points.
Migrations displays local migration history and source inventory. The external converter performs legacy conversion.
Settings opens Joomla com_config and returns to Dashboard on Close.

Global list screens default to newest ID first unless their domain requires a semantic sequence (for example rounds inside a stage). Joomla toolbar buttons respect ACL and selection state.

Project Panel

Project Panel is the entry point for every project-scoped operation. Always pass a valid project_id; opening a context screen without its project should return to a safe parent screen rather than guessing a record.

The panel links to:

project settings and permissions;
entries and participant membership;
project rules and templates;
stages, transitions and progression;
rounds, schedule planner and project schedule;
project officials/functions;
standings adjustments and project preflight.

The counters distinguish saved overrides from aggregate domain records. A zero is not always an error: a profile may not require officials or standings.

Entry and membership screens

Project Entries assigns teams, people or groups to the project. The profile's allowed entry model is validated on save. From an entry, manage current and historical members. Player positions are filtered to player positions for the project's sport; staff uses the label Function and is filtered to staff positions.

Membership history uses repeatable validity/status rows so injury, suspension, departure and return can each occur more than once without destroying prior information.

Stage screens

Stages defines ordered structural sections. Stage Entries controls inheritance versus explicit assignment. Stage Transitions defines how entries qualify for another stage, and Stage Progression previews/applies that transition. Stage Table manages stage-specific standing adjustments and inspection, not a second manual standings calculator.

Programme screens

Rounds groups programme items. Schedule Planner generates a preview from a selected JSON schedule method and only writes after Apply. Project Schedule provides a cross-round operational list. Programme Items for a round supports participant, date, time, venue and score entry; full Edit opens all fields.

The item detail branches into lineup, staff, substitutions, officials, timeline events, statistics and structured result segments. Availability is profile-driven.

Standings and readiness

Standings are calculated automatically. The administrator standings context is retained for inspection and adjustments, not because public output needs a manual Recalculate action.

Preflight is the final readiness audit. Each finding links to the closest management screen. Fix source data rather than dismissing a failed immutable contract.

New creates a record in the current global/project context.
Edit requires one selected row unless an inline edit link is provided.
Publish/Unpublish changes visibility, not domain readiness.
Save keeps the editor open; Save & Close returns to its logical parent; Close discards unsaved form changes and returns without relying on browser history.
Context editors preserve a return URL so closing project settings opened from Project Panel returns to that panel.

If a toolbar action appears to flash without navigation, check browser console and Joomla form task wiring, then report the exact view and selected rows.