> For the complete documentation index, see [llms.txt](https://docs.hackle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hackle.io/en/cohort/export-cohort.md).

# Export Cohort

The Cohort detail page lets you view the Cohort's conditions and the list of users included in the Cohort.

You can modify the Cohort's conditions. After changing the conditions, click the 'Save' button in the top right area to apply the changes.

## User Information Included in a Cohort

Below the Cohort's conditions section, you can view information about the users included in the Cohort.

You can see how many unique users belong to this Cohort based on the identifier selected in 'User Identifier Basis'.

The table on the screen shows up to 500 user identifier values. The 'Last Updated' field in the top right of the table indicates the last time the Cohort was queried with the configured conditions.

## Exporting a Cohort

Click the **'Download (.csv)'** button at the top right to receive the full user list of the Cohort as a CSV file via email. The file delivery may take approximately 10 minutes.

![](https://143363954-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyAVlNQhS253reum0Ce94%2Fuploads%2Fgit-blob-5f0fe8357ce38d0ab72a935c5386bcdda6084169%2F05847c0-Cohort_Detail_Page_f092fca164c64967.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.hackle.io/en/cohort/export-cohort.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.
