> For the complete documentation index, see [llms.txt](https://help.reekolect.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.reekolect.ai/reekolect-resource-center/how-reekolect-works/teams/team.md).

# Team

This page contains all the necessary information about the "Teams" sections.

#### Teams

The Teams section provides an overview of all team members, allowing you to manage their roles, permissions, and account access.

**Key Features:**

* **Status:** If a team member's status is **active**, they can access the account. If marked **inactive**, their access is restricted.
* **Actions:** You can edit team member details, modify roles, and remove members if necessary.
* **Role:** Displays the assigned role of each team member.

This section also allows you to add new team members and define their roles and permissions.

**How to Add a Team Member:**

1. Click on the **Add Team Member** button.
2. Enter the team member’s details, including **name, email, and phone number**.
3. Choose a **Role** for the team member.
4. Set **Lead Visibility** to define whether they can view all leads or only their assigned ones.
5. Configure **Lead Assignment Permissions** based on available options.
6. Create a **password** and upload a **profile icon** for the team member.
7. Click **Add Team Member** to finalize.

Next, we will explore how to create a new role and modify the permissions and details of existing roles.


---

# 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://help.reekolect.ai/reekolect-resource-center/how-reekolect-works/teams/team.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.
