> 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/events/create-an-event/manage-attendees/names-of-customers-on-events.md).

# Names of customers on Events

By default, Customers signed up for an Event are visible to other Customers in the **Attendees** section at the bottom of the Event page in the App, showing first name and first initial of last name.

See [Attendee List and Spots Left Configuration](/events/create-an-event/attendee-list-and-spots-left-configuration.md) for the full setup guide, including how **Public Attendee List** works independently from **Show Spots Left**.

#### Customer controls their own visibility

If a Customer does not want their name visible:

1. Open the **Account** tab in the App
2. Tap **Preferences**
3. Open **Social Settings**
4. Turn off name visibility

When a Customer turns this off, their name is not shown on the Event. The Event still shows how many players are signed up.

#### Admin controls for a specific Event

To turn off name visibility for an entire Event:

1. Open the Event in the Dashboard
2. Go to **Advanced Features**
3. Toggle off **Public Attendee List**

When disabled, the App shows the total number of players rather than individual names. This does not affect whether Customers see how many spots are left — use the separate **Show Spots Left** toggle for that.

**Public Attendee List** is automatically disabled for Kids Only Events.

\[SCREENSHOT NEEDED: Advanced Features section with Public Attendee List toggle]


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.podplay.app/events/create-an-event/manage-attendees/names-of-customers-on-events.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.