> For the complete documentation index, see [llms.txt](https://docs.eventication.com/event/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventication.com/event/planning/stations.md).

# Stations

A group of Substations is a Station

## The overview

The overview page of stations has a bunch of information. By default it shows the allowance of who can join a station, volunteers or groups or both. Use the selector box to see other views that can be interesting for your event.

* **Number of members**: A list of all the stations and their substations with the total number of people having shifts in them.
* **Job fill**: All substations and a percentage of the fill of all their jobs.
* **Zones**: An overview of all the zones that are attached to the substations. Click a **Yes** or **No** to toggle.

## How we work

Our planning module is divided in 3 levels.

1. **Stations**: A collection of locations with the same properties. Some examples:
   * Bars
   * Exits
   * Food trucks
   * Parking
2. [**Substations**](https://docs.eventication.com/event/planning/stations/substations.md): The actual location where work can be done. Some examples:
   * *Bars*:
     * Bar 1
     * Bar Tequila
     * Main Beer Bar
   * *Exits*:
     * Main exit
     * Exit at \<street name>
   * *Food trucks*:
     * French Fries
     * The fish truck
   * *Parking*:
     * Parking 1
     * VIP parking
3. [**Jobs**](https://docs.eventication.com/event/planning/stations/substations/jobs.md): The timing of certain work at a substation. Some examples:
   * *Bar Tequila*:
     * Cup wash from 1pm to 4:30pm, needs 2 people
     * Front bar from 20pm to 3am, needs 1 person
   * *Main exit*:
     * Guard from 3pm to 10pm, needs 5 people
   * *VIP parking*:
     * Scan parking cards from ... to ..., needs 1 person
     * Guide exit from ... to ..., needs 3 people

This should allow you to enter the event planning into our system.

***

## Details

The details of the station like name and description.

**Allow association groups**: Allow groups to select jobs in this station. Can be edited per substation too.

**Allow members**: Allow individual members to see this station. Can be edited per substation too.

**Can be picked in the shiftpicker?**: If you have a shiftpicker where they can choose this station (or a substation or this station), you can toggle this setting. If you turn this off, then this station will not be possible for your individual members to choose. It will not even be visible for them.

***

Every station can have [Requirements](https://docs.eventication.com/event/planning/stations/requirements.md), [job requests](https://docs.eventication.com/event/planning/stations/job-requests.md) and members who [prefer](https://docs.eventication.com/event/planning/stations/preferred.md) to work there.

{% hint style="danger" %}
The platform will prevent you from removing a station that contains a significant amount of data. If you need to remove these objects, [contact us](https://www.eventication.com/contact_us), or empty them out before attempting to remove them.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.eventication.com/event/planning/stations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
