# Your own player fields — LEKKIN help

> Record what your club keeps about its players beyond a name and date of birth, like shirt size, school or whether kit is paid, and fill it in when you add, import or open a player, or ask it on your join form.

[Help](/help/) / [Club Hub](/help/club/)

# Your own player fields

Club HubClub admins3 min read

Most clubs keep a spreadsheet for shirt sizes, schools and who has paid for kit. Add those as your own player fields, and they're asked when you add a player and kept on the player's page.

## Adding a field

Open **Configure**, then the **Player fields** tab, and choose **Add a field** from the button in the bottom corner.

-   **Name.** What it’s called on the form, like _Shirt size_ or _School_.
-   **What it holds:**
    -   **Short text**, like a school or a FAN number;
    -   **Long text**, for a few lines;
    -   **Number**;
    -   **Date**;
    -   **Yes or no**, like _Kit paid_;
    -   **One of a list**, like a shirt size: write the choices one per line;
    -   **Several of a list**, like the days they can train.
-   **A hint (optional).** A line under the field, saying what you want in it.
-   **Required.** It must be filled in whenever a player is added: by hand, from a spreadsheet, or on the join form if you ask it there.
-   **Staff can’t see this.** Only your club admins see it and fill it in. Team managers and coaches don’t see it anywhere, not even that it exists.
-   **Players can see this.** The player, or their guardian, sees their answer on their page in the Player Hub. On unless you turn it off: turn it off for anything the player shouldn’t read, like a safeguarding note.
-   **Players can fill this in.** They give or change it themselves in the Player Hub, so you don’t have to collect it. Off unless you turn it on, and only for a field they can see.
-   **Ask it on the join form.** Anyone asking to join through your club’s join link answers it, so a new player’s shirt size comes with their request. Off unless you turn it on. If it’s also **Required**, the form can’t be sent without it.

What a field holds can’t be changed once you’ve added it, because players’ answers are already in it. To ask it another way, archive it and add a new field.

## Where your fields appear

-   **Inviting a player**, in the Club Hub and the Team Hub: your fields come after the player’s details. A required one has to be filled in before the invitation can be sent.
-   **Importing from a spreadsheet**: each field is a column you can choose. A column headed with the field’s name is chosen for you. Dates are read day first, yes or no can be _yes_, _no_, _y_ or _n_, and a choice is matched whatever its capitals. A value that doesn’t fit, or a required field left empty, is a problem with that row, shown before anything is added. See [Importing players from a spreadsheet](/help/club/importing-players-from-a-spreadsheet/).
-   **The player’s page**, under **Club details**. Press **Change** to fill them in or correct them. A blank one says _Not given_.
-   **The join form**, if you ask it there: under a heading with your club’s name, like _Riverside FC also asks_. You see the answers on the request in **People**, **Join requests**, and approving puts them on the player. See [Teams, players and fixtures](/help/club/teams-players-and-fixtures/).
-   **The Player Hub**: players and guardians see the fields you let them see, on the player’s page, and fill in the ones you let them. See [Your club details](/help/player/your-club-details/).

## Who sees them

-   **Club admins** see and change every field.
-   **Team management**, and a **team’s manager** for their own squad, see and change them, except a field marked **Staff can’t see this**.
-   A team’s **coaches** see them for their own squad but can’t change them.
-   The **player**, and their **guardian**, see a field if **Players can see this** is on, and fill it in if **Players can fill this in** is on. **Staff can’t see this** doesn’t hide a field from the player.
-   **Secretaries**, the **welfare officer** and other players don’t see them.

## Changing, archiving and deleting

Press **Change** on a field to rename it, change its hint or its choices, or whether it’s required or hidden from staff. If you take away a choice that players have already given, they keep that answer, but it isn’t offered again. Use **Move up** and **Move down** to put the fields in the order the forms ask them.

A field that players have answered can only be **archived**: it comes off the forms and the import, and what players already have stays on their pages, marked _no longer asked_. **Bring back** asks it again. A field nobody has answered can be **deleted**.

## Good to know

-   **Only ask for what you need.** If a field holds health information, like medical notes, your club is responsible for it under data protection law, as the [privacy notice](/privacy/) says. Mark it **Staff can’t see this** unless your team staff need it.
-   **Think twice before asking health information on the join form.** Anyone with your link can fill it in, before you’ve agreed to take them on. If you don’t take them, rejecting the request deletes it, answers included.
-   A club can have up to 40 player fields.
-   When somebody deletes their LEKKIN account, your club’s details about them are deleted with it.

Still stuck? [Tell us what you were trying to do](/contact/).