MEIMOSI
Sports System
MeiMosi Sports — Mei Mosi Taifa 2026.Web App for tournaments: organisations, payments, teams, players, verification, matches, and results. This guide matches application version 4.9.0APP_VERSION.
What Is This System?
MeiMosi Sports (Mei Mosi Taifa 2026) is a web application for managing sports tournaments for Tanzanian ministries, institutions, and partners. It covers organisation registration, payments, teams, players (including self-registration and verification), match scheduling, referee tools, and results.
Ministries, agencies, and companies register, pay fees, enter teams and players.
email loginSchedule matches, assign referees, and record results across all sports.
email loginView your team, fixtures, profile, and messages in the Player Portal.
player ID loginManage assigned matches, record live results, update match state.
email loginYou Are Not Registered Yet
Opening the main site URL without logging in shows the public landing page: tournament info, statistics, and links. If already logged in as staff you go to the dashboard; if logged in as player, the player portal.
| If you are… | Your first step |
|---|---|
| Representative of a new organisation not yet in system | Use organisation self-registration — see Section 3 below. |
| Staff (committee, referee, etc.) with an admin-created account | Use staff login with the email + password you were given — Section 4 (Signing in). |
| A player who must register alone | Use player self-registration, then wait for approval — Section 9 (Player Portal). |
| A player added by your organisation | Wait for your MEIMOSI player number and password (often by email), then use player login — Section 4 (Signing in, Player tab). |
Organisation Registration
This flow is for a new organisation not yet in the database. It creates both the organisation record and the first manager account.
From the public site, follow the link for organisation registration — usually at /home/register.
Name, type, abbreviation, organisation email, phone, address. The contact person's email must not already exist in the system.
This person becomes the Organisation Administrator. Password must be at least 8 characters; confirmation must match exactly.
Organisation (status: pending), user account (role: Org Admin), payment record with reference and amount. A welcome email is sent when outbound email is configured on the server.
Go to /auth/login → Staff tab → sign in → open Payment → upload bank receipt using your payment reference.
Once your organisation is active and payment is approved, you can add teams and players.
Signing In
Open /auth/login — you will see two tabs. Use the correct one for your role.
Quick URL reference:
/auth/login /auth/forgot /home/register /playerportal/signup /playerportal/dashboard /settingsOrganisation Administrator
You are an Org Admin if your account is tied to your organisation and you see your organisation's teams and players in the sidebar menu.
Shows organisation status, payment progress, bank details (when configured), teams, and players. Teams and players can only be registered when the system allows — usually organisation is active and payment approved.
/payments/teamsCreate teams (tournament, sport, gender, name). Open a team to see the roster. Configure formation, jersey colours, starting lineup, substitutes, captain. When rules are met, submit the squad ("Wasilisha") for competition.
/playersAdd players (name, email, NIDA, team, photo, etc.). The system generates a MEIMOSI player ID and temporary portal password and can email them. Use filters such as Mapitio (self-registration and resubmissions) and Jisajili wapya (pending self-registrations only) to process the queue faster.
Editing an existing player: You can always change team, jersey number, and position. Full name and photo are read-only unless the super admin has turned on “Msimamizi wa Taasisi: Hariri Jina na Picha ya Mchezaji” in /settings — then those two fields appear on the edit form for your organisation’s players only. NIDA, email, date of birth, and other identity data remain editable by the super administrator only.
Review self-registered players and choose:
Secretary, Chair & Verifier
Secretary and Chair are the approval gatekeepers for organisation payments. They see the staff dashboard and menu items for organisations, payments, teams, players, and reports (as configured). The Data Verifier is a separate staff role for the player identity / data verification queue: they use Kagua wachezaji and a read-only Players list to work through submissions without payment powers.
Reviews uploaded payment receipts. Moves payments through the Secretary step of the approval workflow. First verifier in the chain.
step 2 of 4Performs the Chair approval after the Secretary has reviewed. Final authority before an organisation becomes active.
step 3 of 4Staff account with access to the verification queue and read-only player directory (filter by organisation). Does not approve payments or change tournament configuration.
verificationReferee
After signing in with a staff email, referees see a focused menu — only matches assigned to them.
Use your email and password at /auth/login → Msimamizi / Afisa.
Dashboard and My Matches menu shows scheduled, live, and recent completed matches assigned to you.
Use match screens to manage match state and record results as the tournament process defines.
Player Portal
Go to /auth/login → tab Mchezaji → click "Sajili Mwenyewe", or go directly to /playerportal/signup. Complete all required fields: personal data, NIDA, insurance, organisation, team, gender, photo, password.
| Portal Section | What it does |
|---|---|
| Dashboard | Team info, squad view, upcoming matches. Switch between teams if multi-team is enabled (?t=team_id) |
| Hariri Taarifa | Update phone, jersey number, position, photo. Change password (current password required) |
| Ujumbe | Messages from administrators. Opening one marks it as read. Check this — not just email |
Messages from Administrators
Passwords & Problems
On /auth/login, click "Umesahau nywila yako?" → go to /auth/forgot. Enter your email; use the OTP sent to your email on the reset page. OTP expires — act quickly and follow on-screen instructions.
There is no self-service reset on the login page in the standard flow. Contact your Organisation Administrator or use the support channels your tournament provides. You can also change it while logged in under Hariri Taarifa if you still know the current password.
Check your player ID spelling — ensure Caps Lock is off for the password. If your account is rejected or inactive, the system blocks login — contact your organisation directly.
Check Payment status and whether the organisation is active. If payment is still pending, complete the upload and wait for approvals. A super admin may enable bypass in rare cases.
Check your spam/junk folder. The wrong email may be on file. Or the server's SMTP may not be configured — but the portal message (Ujumbe) may still be present even if email fails.
Menu by Role
After staff login, the sidebar varies by role. Players use a separate portal menu entirely.
System Architecture
users tableplayers tableSuper admin maintains tournaments, sports, venues, and global configuration. Nothing can be registered without this.
Organisation is registered and linked to the tournament via a registration record.
Org uploads proof; Secretary → Chair approval chain. bypass_payment_registration in Settings skips this if enabled by super admin.
Org admin creates teams: sport, gender, name. Rules prevent duplicate teams per sport/gender/org/tournament.
Formation, colours, starting lineup, substitutes, captain. When rules are satisfied the squad is submitted ("Wasilisha") — flagging it ready for competition.
Admin adds: form → system generates player_id + password + email. Self-register: player uses portal signup → pending → org admin approves / revises / bans.
If allow_multi_team_registration is on, the same player record can link to extra teams via player_team_assignments. Primary team stays on players.team_id.
Super admin / match workflow creates matches, assigns referees, enters results. Published matches feed public/landing views.
APP_VERSION in config/constants.php
© Samwel Mmari · Afritis TZ