> For the complete documentation index, see [llms.txt](https://docs.blockpi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blockpi.io/basic-tutorials/team-management/build-your-own-team.md).
# Build your own Team
## Create a team
{% hint style="info" %}
Once a Team is established, your account will automatically become a Team account, and you can send invitations to UID or email addresses to become your team members. Your team members can view and use all of your endpoints.
{% endhint %}
## Add member
Input BlockPI UID or an email address to invite your team member to join the team.
Once an invitation is sent, there will be a pending member on the list. After the member accept the invitation in his email, the status will be updated.
## Manage team
On the left, there will be a tab called 'Manage team.'
* 'Member info' allows you to view member information.
* 'Operation log' lets you see all members' operation records.
* The '+Add member' button adds team members.
At this point, in the Endpoint tab, you are viewing the team's endpoint list.
Just like the team owner, you can see the newly added 'Manage team' tab on the left and use other team features. The only difference is that only the team owner can add or remove members, while team members can choose to leave the team.
## Select login method
If you accept an team invitation, there will be multiple options at login. You can choose to log in to your personal account or the team.
---
# 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.blockpi.io/basic-tutorials/team-management/build-your-own-team.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.
