Permissions and Publication
Editing access and public visibility
Joomla permissions determine who may manage an operation. Publication state and view access levels determine what a visitor can see. Allowing an editor to change scores is not the same as making a private project publicly visible.
Grant only the actions a role needs. Use Joomla user groups, access levels and the component/project permission controls; do not give every editor Super User solely to make a missing toolbar button appear.
Check the full relationship chain
A published match can still be unavailable when its project, competition, season, sport, stage, round or related records are hidden or inaccessible. Public histories and ranking aggregates also apply visibility checks.
Test the relevant page after logging out or in an independent guest browser. An administrator seeing a record is not sufficient proof of guest access.
Project-scoped work
An editor permitted to manage one project should not acquire authority over another by changing a URL parameter, entry ID or hidden form field. Use the project's own links and keep project/entry/stage context consistent.
If a save rejects a foreign-context record, fix the selected context rather than disabling access checks. A UI filter is a convenience, not the security boundary; server-side validation still applies.
Concurrent editing
Respect checkout and stale-revision messages. Reload the record, compare the other editor's changes and make an explicit correction. Repeatedly sending an old score is not a safe way to force a save.
Imports and maintenance
Database import, reset, bulk maintenance and scheduling are privileged actions. Provide only the specific permissions required, keep a verified backup and run destructive experiments only on an isolated copy.
Do not bypass CSRF protection, manually manufacture request tokens, disable foreign keys or use broad administrator permissions as a substitute for investigating an error.
Publishing people's information
Review photographs, birth dates and historical personal information before publication. Decide what your organisation intends to disclose and verify the actual output. The presence of a field in an editor does not establish that the information should be made public.
Send private diagnostics through an agreed private channel. Never publish SQL dumps, passwords, tokens, session cookies or unsanitised logs in support topics.
