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

# Team

Employee roles and access to cabinet sections

The account owner invites employees and assigns a role. The role determines which sections are visible and what can be done.

## Roles

| Role                    | Who is it               | Access                                              |
| ----------------------- | ----------------------- | --------------------------------------------------- |
| **Integrator**          | Configures agents       | All sections except **Team** and **Payments**       |
| **Manager**             | Works with clients      | **Messages** and editing Q\&A in the knowledge base |
| **Manager (read-only)** | Views agents' responses | Only **Messages**, cannot reply to requests         |

**Team** and **Payments** are available only to the account owner.

## How to invite

**Step 1.** In the menu, open **Team**.

**Step 2.** Enter the employee's email and select a role.

**Step 3.** The employee will receive an invitation and log in to the account with their permissions.


---

# 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://docs.athenachat.ai/documentation/documentation-en/features/team.md?ask=<question>&goal=<endgoal>
```

`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.