Beta Free while we're in beta, then £60 a year, just £5 a month. Start free

Guide

Accounts and roles

Super admin, team admin, and player accounts — who can do what, and how people sign in.

Every person who logs in has a user account (email + password). Accounts can be linked to a team, a player profile, or both, depending on role.

Super admin

Full access to /admin. Use this for the league secretary, results secretary, or whoever runs the website. There can be more than one super admin.

Team admin

Captains or club contacts. They land on /team-admin — their own squad, directory, match sheets, and scorecards. They cannot change league-wide settings, other teams’ rosters, or generate the season’s fixtures.

Player

Linked to a player record. They use /player-portal for personal stats, upcoming matches, and (where allowed) individual/doubles scorecards. Players typically claim an account via an invite email rather than being created from scratch by the secretary.

More than one role

One login can be super admin, team admin, and player at the same time. Tick the roles that apply when you create the account. The account page shows each role and links to the matching area, and the person can keep their own name, email, and phone there. A captain can also make another player on their squad a team admin.

Sign in, passwords, and joining

  • /login — email and password. After login, the site sends people to the right dashboard for their role.
  • /forgot-password — reset link by email (needs SMTP configured in Settings).
  • /join — invite token from a player invitation. The player sets a password and claims their existing profile (name and team already on the site).

Create team-admin logins from Admin → User Accounts. Assign the role and the team. Create player invites from the player list or the team-admin roster tools.

Keeping sign-in safe

Repeated wrong passwords and password-reset requests are slowed down. The sign-in page gives the same message whether the email is wrong or the password is, so nobody can test which emails are registered. Sign-in cookies only travel over HTTPS, and every form is protected so another website cannot submit changes on someone’s behalf.