> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/reservations/admin-creates-reservation/adjust-group-size.md).

# Admin Adjusts Group Size

### Overview

If a Customer booked a private Reservation for 4 people and wants to invite 5 people, that's 6 total people instead of 4, and the cost of the Reservation may change (depending on the up-charge your Club set in the Venue page of the Dashboard). Changing the `Group size` is a useful and easy way to update the cost of the private Reservation. This feature also applies when decreasing the `Group Size` for a booking for 4 people to 2 people.

### Admins Update Player Count

For any Club employee to change the Player count, they can:

1. Click on the Reservation
2. Notice the side panel appear
3. Select the `Group size`
4. Choose the new quantity of players
5. Notice any Reservation cost adjustments in the pop-up window
6. Finalize the change of `Group size`

At the end of the Reservation, when charges are processes, any new amount changed to the Customers in the Attendee list of the Reservation will be visible in the Purchases tab of the Reservation.

{% @supademo/embed url="<https://app.supademo.com/demo/cmovx7mc9042qu7akobfshqu3>" demoId="cmovx7mc9042qu7akobfshqu3" %}

This is the view from the Dashboard.

<figure><img src="https://29730733-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvxoNuJiMibWwb1kotX38%2Fuploads%2Fng4wILJ4gLuRCio52JOa%2FScreenshot%202026-06-08%20at%2010.47.16.png?alt=media&amp;token=9c5d69ca-94f4-4f85-85d5-0aefb5fd8759" alt=""><figcaption></figcaption></figure>

### Customers Update Player Count

{% hint style="warning" %}
This feature is not yet available.
{% 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.podplay.app/reservations/admin-creates-reservation/adjust-group-size.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.