> 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/coaches/manage-coach-tiers/export-coaching-sessions-from-the-coaches-page.md).

# Export Coach Sessions

### Overview

Owners and now Coaches can download a CSV from the **Coaches** page of the Admin Dashboard. The **Export** button is on the top right of the Coaches page (to the left of **My Settings** when the signed-in user has a Coach Profile).

#### Owner / Admin export

Anyone with the **Owner**, **Club Owner**, **Admin**, or **PodPlay Admin** role can export coaching activity for the club.

* Open **Coaches** in the Dashboard
* Click **Export**
* Choose a date range (**Current month**, **Previous month**, or **Custom**)
* Click **Export** in the modal to download the CSV

The Owner / Admin CSV includes sessions for **all Coaches** in range, with revenue and transfer amounts, plus location, court, event name, event type, and a link to each session.

#### Coach export

Coaches can export a CSV of **only the sessions they worked**.

* Sign in as the Coach and open **Coaches**
* Click **Export** (left of **My Settings**)
* Choose a date range and download the CSV

The Coach CSV includes date, duration, location, court, event name, event type, and a link to each session. It does **not** include revenue or transfer amounts — Coaches review earnings in Stripe.

{% hint style="info" %}
To learn more, read about [Exporting Data](https://docs.podplay.app/owners-playbook/data-and-security/export-data#exporting-the-coach-robot-page).
{% 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/coaches/manage-coach-tiers/export-coaching-sessions-from-the-coaches-page.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.