
# Events & squads

Events are how you organize a specific gathering — a match, a social, or a general get-together — for one member group. This guide covers scoping an event, collecting RSVPs, picking the squad, and the extra tools that sport events unlock, including lineups, results, and per-game MVP voting.

## Scope: every event belongs to a group

An event is tied to one **member group**. Only members of that group can RSVP or be selected for the squad. Choosing the group is the first decision you make, because it defines the whole eligible pool. For how groups and membership work, see [Members, roles & groups](/docs/admin/members-and-roles).

## Event types

Pick a type when you create the event:

- **Sport** — unlocks lineups, results, and per-player stats (see [Sport events](#sport-events)).
- **Social** — a non-competitive gathering.
- **General** — anything else.

## Draft vs published

An event can stay in **draft**, hidden from members, while you set it up. Members can't see it or RSVP until you **publish** it. Use draft to line everything up — group, type, timing, capacity — before it goes live.

## RSVPs

Once published, members of the group respond to the event:

- **In** — attending.
- **Out** — not attending.
- **Maybe** — undecided.

Members can also **flag a condition** alongside their RSVP — for example, marking themselves injured — so you have context when picking the squad.

## Picking the squad

As an organizer you build the squad from the members who responded. Each selected member is assigned a status:

- **Playing** — in the squad.
- **Reserve** — a backup.
- **None** — not selected.

Squad selection respects a **capacity** — the maximum number of Playing spots. You can't over-fill the playing group beyond that cap, which keeps selection honest to the format.

A **per-event organizer grant** lets you give one person the ability to co-admin a single event without granting them org-wide events permission. Use it to hand off one match or gathering to a helper without broadening their access everywhere. See [Members, roles & groups](/docs/admin/members-and-roles) for how permissions and grants fit together.

## Sport events

Sport events add competitive tooling on top of the basics above.

### Pitch lineup

Sport events include a **pitch lineup view** for placing players in **futsal positions** — goalkeeper, fixo, ala, and pivot — with **x/y placement** on the pitch. You can also set an optional **cosmetic formation label** (for example, a formation name) that's purely descriptive and doesn't change placement.

### Recorded result

After the game you record a **result**: the **score** and the outcome (**win, loss, or draw**). This becomes the event's official record.

### Per-player stats

Log **per-player stats** for the event — **goals** and **assists** — attributing performance to the players who were selected.

### Per-game MVP voting

Sport events support **per-game MVP voting**, which is distinct from [Weekly MVP voting](/docs/admin/mvp-voting). The differences that matter:

- **Only selected players** can vote and be voted for. The MVP ballot is limited to the squad, not the whole group.
- The **scheme is configurable**: either a **single MVP pick** or a **weighted 3-2-1** vote (three points to first choice, two to second, one to third). Your organization has a default scheme, and it can be set per event.
- Voting is **open for 48 hours after the event**, and organizers can **close it early**.
- **Results stay hidden until you publish the squad** — no one sees the MVP outcome before you release it.

Because per-game MVP is scoped to the players in a single match, treat it as a "man of the match" style award rather than the group-wide, week-over-week [Weekly MVP voting](/docs/admin/mvp-voting).

## A typical sport event, end to end

1. Create the event, choose the group, and set the type to **Sport**. Keep it in **draft** while you prepare.
2. Set the **capacity** for Playing spots.
3. **Publish** so group members can RSVP **In / Out / Maybe**, flagging any conditions.
4. Pick the **squad** — assign Playing, Reserve, or None within capacity.
5. Set the **pitch lineup** and, optionally, a formation label.
6. Play the game, then record the **result** and **per-player stats**.
7. Let selected players vote for the **per-game MVP** (single pick or 3-2-1). Close early if everyone's voted.
8. **Publish the squad** to reveal the MVP result.

## Related

- [Weekly MVP voting](/docs/admin/mvp-voting)
- [Members, roles & groups](/docs/admin/members-and-roles)
- [Running hackathons](/docs/admin/hackathons)
