Configure game entry, verification and approvals
MyClubtap
Last Update 12 days ago
Audience: Game admins
Game entry is controlled through three separate decisions:
- Is the game Public or Private?
- Is verification completed before joining or later?
- Is approval Manual or Automatic?
Configure each setting deliberately. Public entry does not automatically mean automatic approval, and Private entry does not automatically mean manual approval.
Entry options
| Setting | Use it when | Member experience |
| Public | Anyone who finds the active game may request access | No private code is required |
| Private (Group Code) | An invited group can use a shared code | Member enters the group code |
| Private (Individual Code) | Access must be tied to a specific invitation | Member enters the code assigned by the organiser |
A group code is one shared code for the Private game and can be used by anyone who receives it. An individual code is created or shared for a particular member and is intended for that member only. Codes do not have a scheduled expiry date. An individual code can no longer be used after its intended member uses it.
Verification options
| Setting | Member experience |
| Complete Verification Before Joining | Required information must be submitted before the joining process can be completed |
| Complete Verification Later | The member can proceed to the permitted stage and is prompted to complete verification later |
With Complete Verification Later, the member can access and use the game normally before completing verification. The organiser can follow up with incomplete members and may suspend game access when required, at its discretion.
Approval options
| Setting | Result |
| Manual Admin Approval | The request remains Pending until an admin approves or declines it |
| Automatic Approval | Access is approved automatically once the configured entry requirements are met |
All supported combinations
| Entry | Verification | Approval | Admin action required? |
| Public | Later | Manual | Review each request |
| Public | Later | Automatic | No approval action; monitor incomplete verification |
| Public | Before joining | Manual | Review verified requests |
| Public | Before joining | Automatic | No routine approval action |
| Private | Later | Manual | Distribute code and review requests |
| Private | Later | Automatic | Distribute code; monitor incomplete verification |
| Private | Before joining | Manual | Distribute code and review verified requests |
| Private | Before joining | Automatic | Distribute code; no routine approval action |
Configure admin email notifications
Approval-request emails and new-member-signup emails are separate settings. For each notification type, choose:
- None: No admin email; this is the default;
- Instant Email: Send an email for every relevant request or signup; or
- Daily Summary: Send one daily email containing the new activity.
Use Instant Email when entry decisions are time-sensitive.
Use Daily Summary when volume is higher and same-day review is sufficient.
Ensure at least one admin is responsible for reviewing Pending requests if Manual Approval is selected.
Presently, these emails are sent only to the game's official admin.
The Daily Summary is sent at 6:00am, using the timezone configured for that game.
Before opening entry
Test the full member journey with a non-admin account. Confirm the invitation link or code, verification fields, Pending screen, approval action and Approved access before sharing the game publicly.