> For the complete documentation index, see [llms.txt](https://ynteq.gitbook.io/ynteq-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ynteq.gitbook.io/ynteq-docs/setting-up-ynteq/add-team-members.md).
# Add team members
In Ynteq, you can create individual accounts for each team member. Every account comes with its own role, making it easy for everyone to access just the features they need.
### Creating accounts
Within the Ynteq environment, the admin user has access to the **Settings** option in the bottom-left menu. From there, you can manage your team members. Simply click the blue **Add Member** button to create a new account by entering the following details:
Once you fill in the details and create the account, new members will receive an email allowing them to log in and get started on their own.
### Different roles
Ynteq comes with three standard roles: the **Admin**, who has the most access; the **Technician**, focused on completing work orders; and the **Operator**, focused on submitting work requests. For more details, you can visit the **User Management** page.
---
# 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://ynteq.gitbook.io/ynteq-docs/setting-up-ynteq/add-team-members.md?ask=&goal=
```
`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.