> For the complete documentation index, see [llms.txt](https://guide.distribute.gov.sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.distribute.gov.sg/organisers/setup-your-locations.md).
# Setup your locations
{% hint style="info" %}
**Locations** are places where your distributions will occur. They do not need to match real addresses — you can name them according to what works best for your campaign.
{% endhint %}
### How do I add locations?
Step-by-step guide
1. Click on the Locations tab
2. Click on Add Location
3. Enter the name of your new location
4. Click submit to confirm
{% embed url="" %}
### How do I bulk upload locations?
Step-by-step guide
1. Click on the Locations tab
2. Click on Bulk Upload Locations
3. Download the CSV template
4. Fill up the template and save as a CSV file (click into the interactive guide to understand what each column means)
5. Upload the completed CSV file
6. Click on Submit to bulk upload the locations
{% embed url="" %}
### How do I edit and delete locations?
Step-by-step guide
**Edit Locations**
1. Click on the Locations tab
2. Click on Edit under the Actions column
3. Type in your new location name
4. Click on Save Changes
**Delete Locations**
1. Click on the Locations tab
2. Click on Delete under the Actions column
3. Click on Delete to remove the location
{% embed url="" %}
---
# 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://guide.distribute.gov.sg/organisers/setup-your-locations.md?ask=&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.