Teams
What this section is for
Teams are how humans organize around a shared purpose. A team is either a department (top-level, like Build or Kitchen) or a sub-team that lives under exactly one department. Each team can have coordinators, named role slots, and optionally a @nobodies.team Google Group plus a linked Shared Drive folder.
A few teams are system teams (Volunteers, Coordinators, Board, Asociados, Colaboradors, Barrio Leads) — the app manages those automatically, so you cannot join or leave them by hand. Some teams are also hidden: privacy-sensitive groupings visible only to admins.
Key pages at a glance
- Teams directory (
/Teams) — landing page; your teams, other departments, system teams. Anonymous visitors see only teams with a public page. - Team detail (
/Teams/{slug}) — description, members, coordinators, sub-teams, join/leave. - My teams (
/Teams/My) — your teams with Leave / Manage buttons. - Birthdays (
/Teams/Birthdays) — teammate birthday calendar (month + day). - Roster (
/Teams/Roster) — cross-team view of named role slots. - Members admin (
/Teams/{slug}/Members) — members, join requests, role assignments. - Edit team page (
/Teams/{slug}/EditPage) — markdown and calls-to-action for a department's public page. - Roles (
/Teams/{slug}/Roles) — define named role slots. - Early Entry (
/Teams/{slug}/EarlyEntry) — grant festival early-entry access for a team (only shown when the team has Early Entry enabled). - Summary, Create, Edit — admin pages at
/Teams/Summary,/Teams/Create,/Teams/{id}/Edit. - Sync — system-team and Google sync admin pages live under the Google controller:
/Google/SyncSettings,/Google/SyncResults,/Google/SyncSystemTeams(POST, Admin only).
As a Volunteer
See the teams you're in
Go to /Teams/My. Each card shows your role (Member or Coordinator) and a Leave button for user-created teams. System teams appear here too but have no Leave button.
Browse and discover teams
Open /Teams. "My Teams" sits at the top, "Other Teams" below with pagination. Each card shows name, short description, member count, and whether it requires approval. Click through to the team detail page for the full description, coordinators, and (for departments) the public page content.
![TODO: screenshot — Teams directory showing "My Teams" at top and "Other Teams" cards below with member counts and approval badges]
Join a team
On the team detail page, click Join. Open teams add you immediately and grant Google Group / Drive access on the next sync. Teams that require approval create a pending join request (with an optional message); you can withdraw it any time. You cannot have two pending requests to the same team.
Leave a team
From /Teams/My or the team detail page, click Leave. Your membership is soft-removed and Google access is revoked on the next sync. You cannot leave system teams.
See teammates
On a team detail page you can see other active humans on the team. Basic profile info follows the normal Profiles rules.
Your team's resources
Joining a team automatically gives you access to the team's @nobodies.team group email and (where set up) its Shared Drive folder. Find the Drive folder via Teams → your team → Resources. Don't share Drive links directly with people who aren't on the team — add them through Humans so access is tracked, and so it goes away cleanly when their role ends. Email setup is covered in Email; the sync mechanics are in GoogleIntegration.
When and where you arrive on site (2026)
Your coordinator gives you a specific arrival date — not a range, not "come when you can". A date. Site is near Castejón de Monegros, Huesca, Spain; the nearest train station is Sariñena (~30 minutes away). An ORG bus service runs on key arrival days; details land closer to Elsewhere.
| Date | Who arrives |
|---|---|
| ~12 June | Placement crew only |
| 15 June | First crew: Barrio Support, Cantina, Power, Production & Logistics |
| 22 June | Set-up week — most departments start arriving |
| 29 June | Pre-event week — barrios and artists arrive |
| 7 July | Gates open |
| 13–22 July | Strike. Stay as long as you can. |
Don't arrive earlier than your confirmed date without checking — early arrivals consume kitchen and infrastructure capacity before they're ready.
On-site contacts (2026)
| For | Who |
|---|---|
| Role questions | Your team coordinator |
| Shift questions or changes | Frank, Nurse, or Hardcastle (vol-coord), or your coordinator |
| Production, logistics, vendors | Daniela — daniela@nobodies.team |
| Welfare and wellbeing | Malfare / Participant Wellness |
| Information, lost and found | No Info (on-site information point) |
| Emergency | Radio — channel given on arrival |
Related sections
- Profiles — team membership feeds profile cards and visibility.
- Shifts — rotas are owned by a department or sub-team; coordinator/manager status drives shift management.
- Camps — camps are team-owned; team membership feeds camp planning.
- GoogleIntegration — how team membership maps to Google Groups and Shared Drive folders.
- Governance — Board and tier roles feed the Board and Colaborador/Asociado system teams.
- Glossary — coordinator, manager, department, sub-team, system team definitions.