Table of Contents
Membership and digital cards
Membership tiers (public)
Visitors complete the journey at *Membership* (/en/membership, etc.). Typical tiers:
| Tier | Who it is for | |
|---|---|---|
| *Fan / consumer* | Supporters following the sport and BBM programme | |
| *Driver* | Named drivers on a programme | |
| *Race team / crew* | Mechanics, engineers, and operations staff tied to a team | |
| *Temporary staff* | Short-event crew where your programme uses that category | |
Exact labels and teams offered depend on programme configuration.
Sign-up flow (member)
1. Choose your *tier and, if prompted, your race team*. 2. Complete contact details and any interest preferences. 3. Accept terms and marketing choices where shown. 4. *Generate card* — the site produces a membership card image you can download. 5. Where enabled, add the card to *Apple Wallet* from the same flow.
Payment may be shown as a step; some environments still run in *demo mode* until live billing is switched on for your programme.
What appears on the card
Cards use the *programme default look (BBM navy and red) unless your team has a custom theme* (logo, colours, footer label). Team-branded cards still identify the member name, tier, and member number.
Team administrators: viewing sign-ups
*Admin → Memberships* lists applications captured from the website or kiosk sync, newest first. You can:
- Review name, email, tier, team, and source. - Edit details when a member made a mistake. - Delete a record when required (only removes the portal copy).
Team admins only see members for their programme unless you are super-admin.
Card studio (branding)
*Admin → Card studio* edits how cards (and related outputs) look for your team:
- Header colour and logo - Accent colour - Footer “network” label (e.g. your team name)
The same theme applies to:
- Downloadable *PNG membership cards* - *Apple Wallet* passes (where enabled) - *Weekend briefing PDFs* for your events
See *Card studio and team branding* in this manual for field-by-field guidance.
Super-admins edit the *global default* first; team admins override only their layer.