> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/getting-started/features/customer-engagement-platform/settings/team.md).
# Team
The **Team** tab lists the members of your team who have access to the project currently selected, along with the permissions they hold.
Use the platform selector at the top of the page to switch between the iOS, Android and Website apps of your project: access is granted per app, so the list changes from one platform to the next.
Users with the **Administrate** permission can change who reaches the selected platforms with the **Edit access** button.
{% hint style="info" %}
This tab controls **who can reach a given app**. The permissions themselves — Administrate, Review, App, Campaign, Privacy — are shown here for reference but are set from Manage Team.
{% 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 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://doc.batch.com/getting-started/features/customer-engagement-platform/settings/team.md?ask=&goal=
```
`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.