> 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/substations.md).

# Substations

The locations

Substations are actual locations where work can be done.

### Details

Here you can change details of the substation like name and description.

**Allow association groups**: Allow groups to select jobs in this station.

**Allow members**: Allow individual members in this station. If you turn this off, some views at the moderator side will also be changed to not support individual members.

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

To duplicate this substation, click the <img src="https://55689121-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMH0qx2kDusOMcs9TvihF%2Fuploads%2Fgit-blob-58481b99fda0e9a247d87cb8e0957596df246543%2FScreenshot%202023-09-10%20at%2011.46.14.jpg?alt=media" alt="" data-size="line"> icon.

{% hint style="danger" %}
The platform will prevent you from removing a substation 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/substations.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.
