> For the complete documentation index, see [llms.txt](https://support.trybit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.trybit.com/account/team-access.md).
# Team and Access
Adding users and configuring restricted access to sections of your Trybit dashboard.
You can invite team members to your Trybit account and configure which sections of the dashboard they have access to — without sharing the account's main login and password.
### How to invite a team member
1. In your dashboard, open "Settings" → "Users."
2. Add a new user by email and choose a role.
3. A login password is sent to the invited team member's specified email.
{% hint style="info" %}
**Important:** the invited email must not already be registered with Trybit — otherwise adding them will fail.
{% endhint %}
### Configuring access rights
Regardless of the chosen role, you can manually open or close access to any specific dashboard sections for each team member. The list of available sections can be changed even after a team member has already been invited — not just at the time of adding them.
{% hint style="success" %}
If you have any questions or need help, you can contact our support via chat on the website and in your personal account, as well as reach us on Telegram. Support contacts are listed [on our website](https://trybit.com/support).
{% 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://support.trybit.com/account/team-access.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.
