> ## Documentation Index
> Fetch the complete documentation index at: https://docs.squadvault.xyz/llms.txt
> Use this file to discover all available pages before exploring further.
# Calendar and availability
> Schedule scrims and training, collect RSVPs, and plan around weekly availability.
Use the calendar to plan the week, then collect availability so you schedule when people can actually play.
For booked scrims, open [Scrims](/user-guide/scrims) — Mission Control for prep, lobby details, and results.
## Calendar
1. Open **Calendar**.
2. Check how prepared the week looks (status), then work through upcoming events and missing responses.
3. Create an event: scrim, training, meeting, or content.
4. Choose visibility:
* **Personal** — only you can see and edit it (available to every member, including players)
* **Team** — visible to that team’s members and staff
* **Organization-wide** — visible to everyone in the organization (managers)
5. Optionally link documents or tasks on shared (team / organization) events.
Personal events never appear for other members, coaches, or managers, and they do not trigger Discord notifications, availability reminders, or starting-soon alerts.
## Built-in reminders
Shared **team** events get automatic reminders when Redis is configured (the worker is running). Defaults:
* **24 hours before** training, scrim, match, or tournament: players who have not RSVP’d yet get an in-app and push nudge.
* **2 hours before** those types **and meetings**: the whole team gets “starting soon” in-app, push, and the Discord team channel.
Open a team workspace to change **hours**, **channels** (in-app, push, Discord channel, Discord DM), or a **custom message** per reminder. Saving reschedules upcoming events for that team. Reset restores the 24h / 2h defaults.
Custom text uses the same `{{path}}` placeholders as [Flows](/user-guide/flows#variables). Open **Custom message**, click a chip to copy it (and insert it into the title or body), then save. Empty fields keep the default copy.
`content` and `other` events are not on this schedule. Updating only linked documents or tasks does not send an “event changed” alert.
These built-in jobs are separate from [Flow templates](/user-guide/flows#templates) such as **Training Availability Follow-up** (−24h Discord blast) and **Scrim Starting Soon** (−1h Discord ping). If you activate those templates, the team can get both the product reminder and the Flow message. Use Flows when you want extra Discord copy or a different time; otherwise leave them off — or turn Discord off on the team reminder so only the Flow posts.
Everyone who needs a **shared** event can see it in one view — no more hunting through Discord threads.
When the event type is **Scrim**, clicking it opens the [Scrim workspace](/user-guide/scrims) instead of the generic edit dialog.
## Recurring events
Make an event repeat (for example a fixed training block) instead of creating each occurrence by hand. When you edit or delete a recurring event, SquadVault asks about scope:
* **This event** — only the occurrence you opened
* **This and following events** — the occurrence plus everything after it
* **All events** — the whole series
Use **this and following** for a schedule change from a certain week onwards, so past occurrences keep their history.
## Event RSVPs
Players respond to events with statuses such as available, maybe, unavailable, late, vacation, or sick. Anyone who has not answered yet shows as pending — use **Remind non-responders** on the event to send them a nudge, so you know the lineup before start time.
## Weekly availability
1. Open **Availability**.
2. Check team coverage (status), then respond, remind, or resolve gaps (work).
3. Players mark weekly two-hour slots when they can play.
4. Coaches and captains use the team heatmap to find the brightest cells.
Roster players see **anonymous counts** (how many people are free), not names — unless an owner or admin turns this off under [Organization settings](/user-guide/organizations#availability-heatmap). Staff still see who is available.
Plan scrims and training around the heatmap instead of long DM chains.
## Good defaults
* Create recurring training blocks early in the week.
* Ask for RSVPs on scrims at least a day ahead.
* Review the heatmap before locking a new scrim slot.
* After a scrim is booked, finish prep in [Scrims](/user-guide/scrims).