> For the complete documentation index, see [llms.txt](https://docs.echevarrisports.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.echevarrisports.com/guia/en/step-by-step/crear-campamento.md).

# Create and publish a camp

## 1. Open the form

Go to **Camps** and click **New camp**.

![Step 1: the New camp button](https://310662894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtfEXMFEU0mFg84Ri6hx%2Fuploads%2Fgit-blob-a700a4f7a1e85eeefa951593332cec38bc6eaf8c%2Fcamps-new-btn.png?alt=media)

## 2. Fill in the camp

1. Under **Runs by** choose **Weeks** (summer, Easter…) or **Days** (birthdays, long weekends).
2. Enter the name, the venue, the first day and how many weeks or days it runs.
3. Set the places per day and the minimum and maximum age.
4. Choose how it's charged: per week or day, the whole camp, or in tiers (for example 1, 3 or 5 days). Leave the price empty to use the price list.
5. Click **Create camp**.

![Step 2: the New camp form](https://310662894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtfEXMFEU0mFg84Ri6hx%2Fuploads%2Fgit-blob-158474f1fc8d3c2cf2594e2c5d49b6b29188433a%2Fcamps-new.png?alt=media)

## 3. Set up the groups

1. Open the first week and go to the **Groups** tab.
2. In the **New group** box, enter the group's name (for example "Junior"), its capacity (**Max**) and the coach, and click **Add**.
3. Repeat for each group and each week.

![Step 3: the New group box](https://310662894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtfEXMFEU0mFg84Ri6hx%2Fuploads%2Fgit-blob-85f444e3f81f79b77a0e1c4e99001fafd7590a91%2Fcamp-new-group-btn.png?alt=media)

## 4. Publish it on the website

Go back to the camps list and click the switch on its card: it goes from **Not published** to **On the website**. From then on families can register on the `/camps` page.

![Step 4: the publish switch](https://310662894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtfEXMFEU0mFg84Ri6hx%2Fuploads%2Fgit-blob-520f87467c43782a78fc50352a4328e7125865dd%2Fcamp-publish.png?alt=media)

{% hint style="info" %}
The camps page's text (header, activities, a day at camp, FAQs…) is edited in the [website editor](/guia/en/website-sanity/paginas.md#campamentos-camps). Prices, weeks and places come from the CRM.
{% endhint %}

## 5. While registrations come in

* Registrations arrive in **Leads** (kind **Camp**) and in each week's **Children** tab.
* Check **Overview › Needs attention** every day: who hasn't paid, who has no group, what medical info needs review and who is missing pickup or photo consent.

  ![Step 5: Overview, what's missing](https://310662894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtfEXMFEU0mFg84Ri6hx%2Fuploads%2Fgit-blob-a8f0335144f4f9bc08a02e5f68bcc410f64245ee%2Fcamp-overview.png?alt=media)
* Sort the children into **Groups**: drag them, or tick them and use **Move to…**.

  ![Sorting the children into groups](https://310662894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtfEXMFEU0mFg84Ri6hx%2Fuploads%2Fgit-blob-cf62f79452af2fab180e2827ec32aa10ac6ba0b0%2Fcamp-groups.png?alt=media)
* When it's full, new registrations go to **Waitlist**. To give a place, use **Give a place from the waitlist**.

## 6. Camp week

Every morning, in **Attendance**, click **Check in** when each child arrives and **Check out** when they leave. The day-before, photos and closing emails go out on their own.

![Step 6: the day's attendance](https://310662894-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUtfEXMFEU0mFg84Ri6hx%2Fuploads%2Fgit-blob-ee6c270069112c8ed5f76c049a78e0cd6afd5db7%2Fcamp-attendance.png?alt=media)


---

# 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.echevarrisports.com/guia/en/step-by-step/crear-campamento.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.