Club & Application Management

**Menu:** Platform Admin → Business Management → Clubs → Club list**

Page layout

• Search by name, code, status.
• Columns: club name, package, subscription expiry, member count, active flag.
• Actions: open detail, impersonate support view (if policy allows).

Step-by-step

1. Open Club list for provisioning or support.
2. Filter inactive clubs for renewal campaigns.
3. Open club detail for deep configuration.

**Menu:** Platform Admin → Clubs → New club**

Typical wizard flow:

Step-by-step

1. New club — complete all five steps without skipping legal link.
2. Assign default membership level if module enabled later.
3. On finish, club manager receives credentials or invite per process.
4. Verify club appears in club panel login club picker.

Common tabs on club detail (names may vary):

1. Overview — stats snapshot
2. Settings — name, status, contacts
3. Subscription — package, expiry, renew
4. Options — feature toggles
5. Application — linked app project
6. Wallets — club treasury
7. Levels — membership tiers
8. Funds — if investment module on
9. Audit — change log if enabled

Step-by-step

1. Open club from list → work left-to-right tabs on new provisioning.
2. Options — enable only purchased modules to avoid menu clutter.
3. Application — link before telling club to use App Builder.

**Menu:** Platform Admin → Clubs → [club] → Wallets**

Treasury and settlement accounts for the club entity.

**Menu:** Platform Admin → Clubs → [club] → Levels**

Seed or lock templates — see Membership Levels guide.

**Menu:** Platform Admin → Clubs → [club] → Funds**

Oversight when fund module enabled.

**Menu:** Platform Admin → Clubs → [club] → Options**

Master switch per module slug — must match RequireFeature in API.

Step-by-step

1. Toggle option on after commercial agreement recorded.
2. Tell club to refresh panel — new menu items appear.
3. Toggle off for non-payment suspension — document reason.

**Menu:** Platform Admin → Business Management → Clubs → Packages**

Define sellable bundles for new clubs and renewals.

Step-by-step

1. New package — name, included options, price, duration.
2. Publish package for sales team catalog.
3. Assign to club on create or migration.

**Menu:** Platform Admin → Clubs → Subscriptions**

Pending upgrade requests, renewals, invoicing hooks.

**Menu:** Platform Admin → Tools & Development → Applications**

Wallet/mobile app definitions — multiple clubs may share one app shell with white-label theme.

Step-by-step

1. Maintain application records with store IDs and push certificates (ops).
2. Link club to application in club detail Application tab.
3. App Builder project binds to this link automatically in most setups.

**Menu:** Club Panel → Operations → Application & Wallet**

Club-side link to platform application — enables wallet and App Builder.

Step-by-step

1. Open after platform admin creates club and assigns app.
2. Confirm application name matches contract.
3. Save — test member login on portal.
4. Proceed to App Builder for home page setup.

**Menu:** Club Panel → Settings → Option store**

Self-service purchase or trial activation of add-on modules.

Step-by-step

1. Browse available options with description and price.
2. Purchase or start trial — wallet debit or invoice per billing setup.
3. After activation, new menu appears — assign staff roles in Panel access.
4. Train staff using help docs for that module.

**Menu:** Club Panel → Settings → My subscriptions**

View current package, expiry, renewal history, invoices if exposed.

Step-by-step

1. Check expiry monthly — renew before options auto-suspend.
2. Download invoice for finance department.
3. Request upgrade through store or account manager contact.

1. Platform admin: create club wizard + package + options
2. Link application and verify portal login
3. Club owner: Panel access — staff roles
4. Configure membership levels and trades
5. Onboard first acceptors and customers
6. App Builder — theme, home, publish pages
7. Notifications — welcome campaign
8. Smoke test: register member → wallet top-up → shop order
9. Document go-live date and support escalation path

• Enable options incrementally — easier support training.
• Keep one Owner account per club plus break-glass backup.
• Align option store purchases with signed contract to avoid revenue leakage.
• Mirror critical config changes in internal CRM ticket.

• Platform admin creates club, package, options, app link.
• Club manager completes application link, option store, App Builder, staff RBAC.
• Subscription expiry silently removes menu items — check dates first on "feature gone" tickets.