> For the complete documentation index, see [llms.txt](https://broker-docs.tiger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://broker-docs.tiger.com/english-2/referral-program/teams.md).
# Teams
Some partners offer their referrals the opportunity to join their team.
The button to manage your request for joining or leaving a team is located in the [Profile menu](https://account.tiger.com/profile):
### How to apply for team membership?
When you click the **"Send request"** button, a modal window with the terms and conditions will appear. To submit your request, you need to review and confirm your agreement with them.
{% hint style="success" %}
The team owner sets the criteria for joining the team and is responsible for reviewing membership requests.
{% endhint %}
### What information does the team owner see about its members?
The partner whose referral code you are linked to can view your statistics — such as trading volume and the amount of commission paid.
Additionally, the team owner has access to:
* Profitability statistics of team members over a specific period in the **Leaderboard** section.
* The ability to set a commission discount for your account.
* Viewing risk manager events and the set drawdown limit if this tool is enabled for your account.
---
# 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://broker-docs.tiger.com/english-2/referral-program/teams.md?ask=&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.
.png?alt=media&token=602af186-8205-4426-992d-d5ac0904c9d4)
.png?alt=media&token=50806088-5f6c-4f1a-9ed3-7dbc2554505c)