Group onboarding link

TL;DR

A single group link the club distributes via WhatsApp or any channel. The player opens it, sees the squad photo grid, clicks “That’s me” on their photo, and triggers an email to the address pre-loaded by the coaching staff. 100% anti-spoofing: even if another player clicks a photo that isn’t theirs, the email won’t reach them.

For sales

• Problem it solves: inviting a full squad one by one by email is slow and ends in spam or outdated emails. The group link goes through WhatsApp (the channel the squad actually uses) and the player confirms identity visually.
• Typical use cases: the first time the club activates CÉNIT — the HoP loads the squad’s emails into Squad, generates the link, pastes it in the WhatsApp group, and by the next day most of the squad is in.
• Plans that include it: all of them.
• Differentiator: identity by photo, not by typed email. And the email is sent to the pre-loaded address — a prankster cannot harvest other people’s emails.

How staff use it

Access and permissions

• Allowed roles: Head of Performance, Sporting Director, and S&C. Anyone else is redirected to the dashboard.
• The link URL contains a token unique per organization (not per player).

Step-by-step flows

• Pre-requisite. The coaching staff loads the emails on the player’s profile from Squad. If a player has no email pre-loaded, they can still use the link — the confirmation screen prompts them to type their email manually.
• Generate / copy the link. The HoP sees the group link URL with three counters:
  1. Eligible — active players without an account and without completed onboarding.
  2. No email — eligible players who additionally don’t have an email loaded (they will have to type it).
  3. Linked — already have an active account.
• Distribute. Copy the URL and paste it into WhatsApp / the squad’s channel.
• Player flow (public side).
  1. Opens the link → sees their org’s squad photo grid.
  2. Clicks “That’s me” on their own photo → confirmation screen.
  3. The system sends an email to the pre-loaded address with a set-password link. If there was no pre-loaded email, the player types it on the confirmation screen.
  4. The player sets a password.
  5. The system automatically links the account to the player and marks onboarding as completed.

FAQ / edge cases

• Can I regenerate the token? The token is generated when the org is created. There is no UI to regenerate it today.
• What if the player clicks twice? The system takes only the first one and handles the second without breaking anything.
• Changing the email later: if the player has already activated their account, changing the email on the profile does not affect their login.

How the player sees it

Yes — this sub-page describes the player flow. Screens:

• Screen with the squad photo grid.
• Identity confirmation screen (+ email typing if missing).
• Email with set-password link.
• First login → player portal.

Integrations

• Squad — pre-loading the player’s email is a functional requirement.

Limitations

• No direct deep-link to the app store; the flow is web → PWA.
• No report on “how many viewed the link but didn’t complete”.