Clubs
| Club | Site | License | Status | Last check-in | Actions |
|---|
1Club details
2License
3Confirm
Issued licenses
| Key | Club | Plan | Seats | Expires | Status | Actions |
|---|
Publish an update
The build is only ever offered to servers of this product. Caddie and Fleetline keep their own version histories.
Read from the uploaded build automatically. Only fill this in if you are publishing a download URL instead of a file.
Published updates
| Version | Product | For | Channel | Wave | Mandatory | File | Published |
|---|
Rollout — who is on what
| Club | Site ID | Version | Status | Health | Last seen | Contact |
|---|
Based on each club’s most recent check-in. A club that has not checked in since an update was published will still show its old version.
SMTP (outgoing email)
Expiry reminders
Comma-separated. e.g. 30,60 emails once at 60 days out and again at 30 days out.
Club backups
Where each club's uploaded backups are kept — one subfolder per club. Can be a local drive or a mapped/UNC path the central service can write to. Applies to new uploads (existing files stay where they were saved).
Test
Club servers
| Club | State | Version | What is wrong | Last seen | Contact |
|---|
Clubs check in every few minutes. Anything quiet for more than two hours is either switched off, off the network, or broken.
Recent check-ins
| Club | Version | Health | Errors | Message | When |
|---|
Latest backup per club
The most recent full database backup each club server has uploaded. Download the .dump and restore it with
pg_restore; the settings/logo file holds that club's licence, central address and branding.| Club | Version | Size | Uploaded | State | Get |
|---|
Test a license exactly as a club server would — this checks the key belongs to the site, isn't expired, and is within its terminal limit.
Add a user
Staff logins
| Username | Added |
|---|