Training Module 17 — Central Command (Platform Administration)
GoClubPro User Training | Area: Central Command / Platform Administration
What Users Need to Learn
Central Command is the platform-level Platform Admin interface. This module is for platform operators and support staff. Users need to understand:
- What Platform administrators can do that no other role can
- How to manage associations and clubs
- How to view the full user directory
- How to use system diagnostics
- How to manage the Super Selector (platform-wide fantasy)
1. Step-by-Step Walkthrough
Accessing Central Command
- Log in with a Platform Admin account.
- Click Platform Admin (or Central Command) in the navigation.
- You land on the platform overview dashboard.
Managing Associations
- Central Command → Associations tab.
- You'll see all associations registered on the platform.
- Click any association to:
- View their clubs
- Edit association details (name, sport type, region)
- Assign or revoke Association Admin roles
- View financial compliance summary
Managing Clubs
- Central Command → Clubs tab.
- Full directory of all clubs on the platform.
- Click any club to:
- View their member list, team structure, financial status
- Impersonate the club (act on behalf of the Club Admin for support purposes)
- Suspend or reactivate a club
- Force-assign or revoke roles
Viewing the User Directory
- Central Command → Users tab.
- Search any user by name or email.
- View their:
- All club memberships and roles
- Account status (active, suspended, email unverified)
- MFA status
- Last login
- Actions available:
- Reset MFA
- Force email verification
- Suspend or reactivate account
- Impersonate user (for support)
Running System Diagnostics
- Central Command → Diagnostics (or
/admin/diagnostics). - Diagnostics show:
- System health status (API, database, email service)
- Recent error logs
- Queue status (background jobs)
- Active user sessions count
- Use this to diagnose platform-level issues.
Managing Super Selector (Platform Fantasy)
- Central Command → Super Selector.
- Create or manage platform-wide fantasy gameweeks.
- These span multiple clubs/associations — any registered player on the platform can be picked.
- Manage via the same interface as club-level Fantasy Admin, but with cross-club player pools.
2. Simple Explanation (Beginners)
Central Command is the control room for the entire GoClubPro platform — not just one club, but every club, every association, and every user on the system.
Platform administrators are typically platform operators or technical support staff. They can see everything, fix anything, and assist any club or user who needs help.
This role should be given to as few people as possible — it carries significant access to sensitive data across all organisations.
3. Advanced Explanation (Power Users)
Impersonation: Platform administrators can impersonate any user for support purposes. All impersonation sessions are logged with timestamp and reason. Impersonation is read-only by default; write access requires explicit confirmation per action.
Club suspension: Suspending a club makes it inaccessible to all its members. Use for non-payment, policy violations, or club dissolution. Suspended clubs can be reactivated.
Role assignment: Platform administrators can assign any role to any user across any club or association — bypassing the normal invite/approval flow. Use carefully; this capability can create unexpected access.
Diagnostics deep dive: The diagnostics page connects to internal health check endpoints:
- API latency percentiles (p50, p95, p99)
- Database connection pool utilisation
- Email delivery success rate (Resend)
- Background job queue depth and failure rate
Data governance: Platform administrators must comply with data access policies. Accessing individual user data should be logged and justified. Do not use impersonation to browse personal data without a support request.
Audit log: All Platform Admin actions are logged in an immutable audit trail accessible to platform operators for compliance review.
4. Visual Description (Text-Based)
┌─────────────────────────────────────────────────────────┐
│ CENTRAL COMMAND — Platform Administration │
│ │
│ [ Associations ] [ Clubs ] [ Users ] [ Diagnostics ] │
│ │
│ PLATFORM OVERVIEW │
│ Total Associations: 24 │
│ Total Clubs: 187 │
│ Total Users: 12,450 │
│ Active This Week: 3,821 │
│ │
│ SYSTEM HEALTH │
│ API: ✅ Healthy Latency: 124ms │
│ Database: ✅ Healthy Pool: 45/100 connections │
│ Email (Resend): ✅ Healthy 99.2% delivery │
│ Job Queue: ⚠ 45 jobs 3 failed (retrying) │
│ │
│ RECENT ACTIVITY │
│ New club registered: Hawthorn Hawks FC · 2h ago │
│ MFA reset requested: james@email.com · 4h ago │
│ Payment declaration flagged for review: #4892 · 6h ago │
└─────────────────────────────────────────────────────────┘
5. Tooltips & Hints
| Location | Tooltip Text |
|---|---|
| Impersonate User | Logs you in as this user for support purposes. All actions are audit-logged. |
| Suspend Club | Immediately locks out all members of this club. Use only for serious violations or shutdown. |
| Force Email Verification | Bypasses the email verification step for this user. Use only when genuinely needed. |
| Reset MFA | Removes MFA from this user's account. They'll need to set it up again on next login. |
| Diagnostics | Real-time system health. Refresh for the latest status. |
| Super Selector | Platform-wide fantasy league. Cross-club player pool. |
6. FAQ — Central Command
Q: Can I use Central Command to change a member's password? A: No — passwords are never accessible, even to Platform Admin. Users must use the Forgot Password flow.
Q: A club is reporting that member payment declarations aren't showing up for their Treasurer to review. What do I check? A: Diagnostics → database and background job queue status. A stalled job queue or DB slowdown can delay a declaration appearing in the Treasurer's Reconciliation tab.
Q: How do I create a new association on the platform? A: Central Command → Associations → Create Association. Enter the association name, sport, region, and assign an Association Admin.
Q: Can I delete a club entirely? A: Yes — but this is irreversible. All member data, payment records, and fixtures are permanently deleted. Only do this for truly defunct clubs that explicitly request deletion.
Q: What's the difference between suspending and deleting a club? A: Suspension is reversible — the club is locked but data is preserved. Deletion is permanent. Always suspend first; delete only if certain the club won't return.
7. Common Mistakes & How to Avoid Them
| Mistake | What Happens | How to Avoid |
|---|---|---|
| Impersonating users without a support request | Privacy violation; audit log flagged | Only impersonate in response to a logged support request |
| Deleting a club instead of suspending | Irreversible data loss | Always suspend first; delete only on explicit written request |
| Assigning Platform Admin role broadly | Security risk; excessive access | Platform administrators should be limited to 2–3 platform operators maximum |
| Acting on Diagnostics failure without investigation | May restart healthy services | Investigate root cause before taking remediation action |
| Resetting MFA without verifying identity | Could assist account takeover | Verify identity through secondary channel before MFA reset |
8. Short Onboarding Script
Central Command — Platform Oversight
As a Platform Admin, you have platform-wide visibility:
- Associations & Clubs — view, manage, and assist any organisation
- Users — find any user, reset MFA, manage access
- Diagnostics — check platform health in real time
With great access comes responsibility — all actions are audit-logged.
9. Long Training Guide
When to Use Central Command
Central Command is for exceptional situations — not for routine club administration. Typical support scenarios:
| Scenario | Action |
|---|---|
| User locked out (lost MFA, no backup codes) | Users → find user → Reset MFA |
| Club reports payment declarations not appearing | Diagnostics → database health + check failed jobs |
| Duplicate clubs created | Clubs → identify duplicates → contact clubs to merge manually |
| Association Admin not receiving bills | Users → verify Association Admin role → check email delivery |
| New association onboarding | Associations → Create → assign admin → notify them |
| Club wants to close | Suspend first → confirm → Delete after written request received |
Audit Trail Expectations
Every Platform Admin action is recorded:
- Who performed the action
- What was changed
- When it occurred
- Why (if a reason was entered — always enter a reason for impersonation)
This log is immutable and used for security audits and compliance reviews. Treat Central Command access with the same discipline as production database access.
Platform Health Monitoring
Key metrics to watch in Diagnostics:
| Metric | Healthy Range | Action if Outside |
|---|---|---|
| API latency p95 | < 500ms | Investigate slow endpoints; check DB |
| Database connections | < 80% of pool | Scale DB if consistently high |
| Email delivery rate | > 98% | Check Resend dashboard for bounces |
| Job queue depth | < 100 | Investigate stalled jobs; restart queue if stuck |
10. Micro-Training (Quick Tips)
⚡ QUICK TIPS — Central Command
✅ Only impersonate users in response to logged support requests
✅ Suspend clubs before deleting — deletion is permanent
✅ Check Diagnostics first when clubs report platform issues
✅ Limit Platform Admin accounts to 2–3 operators maximum
✅ All actions are audit-logged — act accordingly
✅ MFA reset requires identity verification first
11. Troubleshooting
| Problem | Likely Cause | Fix |
|---|---|---|
| Diagnostics shows DB connection pool at 95% | Traffic spike or slow queries | Monitor query performance; consider connection pool increase |
| Payment declarations delayed in appearing | Job queue backup | Restart job processor if queue is stalled |
| Email delivery rate drops below 95% | Domain reputation issue or Resend outage | Check Resend dashboard; review for spam flagging |
| Can't find user in Users tab | Typo in search, or account deleted | Try partial email search; check deletion audit log |
| Association not appearing in list | Not yet created | Create via Associations → Create Association |
| Impersonation session ended unexpectedly | Session timeout | Re-enter from Central Command → Users |
Module 17 of 20+ | Next: Module 18 — Feature Requests