Skip to content
Guide8 minute read

Invite a family and review a player registration

Invite a parent, work through the registration queue, check documents and existing-player matches, then approve, request changes or reject.

Reviewed 1 September 2026 · Verified for Clubs web and app · September 2026

Before you start

  • Club owner, club admin or registrar access
  • A team and active season
The registrations queue in Playlee Clubs populated with fictional demo playersOpen full-size screenshot
The registration queue separates pending, approved, incomplete and payment-pending records while keeping the parent invite controls close by.WEB · captured 1 September 2026
On this page

What this workflow does

A registration is how a player joins your club. Families usually register through the team’s signup link or team code; you can also invite a parent by email. Each registration then arrives in People → Registrations for a decision.

By default, registrations approve automatically once any signing-on fee is paid. The ones left for you are those that need a person: when “Require admin approval” is on in Settings → Joining, or when the registration matched a player the club already has.

Registering players with the league (the FA Club Portal, FANs, “Mark submitted”) is a separate step. See “Register players with the league (FA Club Portal)”.

Where to go

People → Registrations
Invite parent, the pending invites list, and the Registration queue with Approve, Request changes and Reject.
Player record → Admin tab
“Request a player update” asks the family for one specific missing or outdated detail.
People → Information requests
Track every detail families have been asked for, approve what they send, remind or cancel.

Invite and review a registration

  1. 1

    Invite a parent if they do not have the team link

    In People → Registrations, use Invite parent: enter the parent email and choose Send invite. They get a secure link to the parent onboarding flow. Most families simply use the team’s signup link or team code instead.

  2. 2

    Keep an eye on pending invites

    Invite links never expire. Anything still unused stays in the pending list; choose Revoke on any invite that should no longer work.

  3. 3

    Filter the Registration queue

    Use the status filter: Pending review, Missing information, Approved, Rejected or Payment pending (signing-on fee not yet paid).

  4. 4

    Check the details and documents

    Open the documents shown on the registration and check the player, guardian and team before deciding.

  5. 5

    Take care with “Check existing player”

    This badge and “Guardian identity needs checking” mean the registration matched a player you already have, but the adult did not recognise the masked guardian email. Approving confirms it is the same child and adds this adult as another guardian. If you are not sure, contact the family first.

  6. 6

    Approve, request changes or reject

    Approve adds the player; Request changes marks it Missing information; Reject declines it (shown as “Reject & refund” when a signing-on fee was paid). The family is told about the decision.

  7. 7

    Ask for one specific detail later

    Open the player record, go to the Admin tab and use “Request a player update”, then Send request. The request stays visible to the family in the app until it is completed or cancelled; follow it up in People → Information requests.

    The Playlee Clubs player directory populated with fictional demo players and varied registration statesOpen full-size screenshot
    Use the player directory to find the member and check registration, payment and information flags before opening the player card.WEB · captured 1 September 2026

Check before you finish

  • Nothing is left in Pending review without a reason.
  • “Check existing player” matches were confirmed with the family.
  • Payment pending registrations are expected to approve once the fee is paid.
  • Unused invites that should not work any more are revoked.

Avoid duplicate players

Avoid duplicate players

If Playlee recognises that the child is already registered, approve the match to add the adult as a second guardian rather than creating another player. The warning should not block a genuine second guardian.

Common questions

Why can I not see Approve or Reject?

Deciding registrations needs club owner, club admin or registrar access. Other roles see “You don’t have permission to approve or reject registrations.”

Why is a registration stuck on Payment pending?

The signing-on fee has not been paid yet. With admin approval off, the registration approves itself once the payment goes through.

Where is “Mark submitted”?

That is part of league registration, not this queue. Use People → League registration.

Do invite links expire?

No. Invite and signup links only stop working when the club revokes, pauses or archives them.

Why do so few registrations reach the queue?

With “Require admin approval” off (the default), registrations approve automatically once any signing-on fee is paid. Turn it on in Settings → Joining to review every one.

Request a member information update

  1. 1

    Open the current controls

    Open the member profile request controls; guardian requests start from the member?s existing guardian link.

  2. 2

    Review and confirm

    Choose the field and person, Missing or Replace, an optional reason and due date, then request the update.

  3. 3

    Check the effect

    Eligible family accounts receive an app push. Existing medical/contact values are not copied into the request review.

Request team or club information

  1. 1

    Open the current controls

    Open the registration information request controls.

  2. 2

    Review and confirm

    Choose the permitted team/club scope, a player field, Missing or Replace and optional reason/date, then submit.

  3. 3

    Check the effect

    The native batch limits requests to eligible players, can skip existing values/open requests and sends grouped app pushes.

Request missing registration information

  1. 1

    Open the current controls

    Open the registration information controls.

  2. 2

    Review and confirm

    Choose the permitted scope, all or not-yet-registered players, and optional reason/due date, then request missing information.

  3. 3

    Check the effect

    The native sweep applies current required fields and limits, notifying eligible families in the app.

Cancel an information request

  1. 1

    Open the current controls

    Open the named active information request.

  2. 2

    Review and confirm

    Choose Cancel and confirm.

  3. 3

    Check the effect

    It is cancelled without a new family notification.

Remind a family about an update

  1. 1

    Open the current controls

    Open the named active information request.

  2. 2

    Review and confirm

    Choose Remind and confirm the app push.

  3. 3

    Check the effect

    The native 24-hour cooldown and recipient availability can refuse the reminder; no successful delivery is promised.

Create a guardian without contact details

  1. 1

    Open player guardian controls

    Open the player member profile and guardian links as an authorised member administrator. Select the current player before entering a new name.

  2. 2

    Review a new person

    Enter first and last names, relationship, primary status, profile-update and future-email switches. This creates a new person without contact details or an invitation. An identical existing name refuses; existing-person and contact variants stay in the app.

  3. 3

    Confirm global access consequences

    Choose Do it after reviewing the global full-child-access association with fee visibility disabled. A later account link can grant family access. Person, membership, association and audit writes are separate, so failure can leave earlier records saved. No message or payment is sent.

Review a submitted requested document

  1. 1

    Use the current app controls

    Open People, Requests. Find the named submitted document request and choose Approve or Reject; enter an optional rejection reason.

  2. 2

    Review what happens

    Approving verifies the document and completes the request without a message. Rejecting reopens it, detaches the submission and can push a request to currently eligible linked accounts. This guided review does not download or display the file; use the app to inspect the evidence before deciding.

  3. 3

    Check the original outcome

    Only explicit approval invokes the native action. Current reviewed witnesses are rechecked, but later reads, writes, audits and delivery may remain separate. If the result is uncertain, reconcile the original request rather than creating another operation.