> For the complete documentation index, see [llms.txt](https://docs.reo.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reo.dev/user-management/invite-a-teammate-to-reo.dev.md).
# Invite a teammate to Reo.Dev
Invite your team to Reo.Dev to give them access to hot accounts with in-depth context of developer activity.
**Step 1:** Click on **'Users'** under settings in the left navigation panel.
**Step 2:** Click on the **Invite** option
\
**Step 3:** Enter the new team member's credentials. Choose whether to assign the new member as an **Admin** or a **User** during the invitation process. Each role has distinct permissions and access levels within Reo.dev.
**Learn More About Roles:** [Check out this guide](/user-management/roles-and-permissions-admin-vs-user.md) to understand the detailed differences between Admin and User roles, including their permissions and capabilities.
**Step 5:** Click **Invite**. The new team member will receive an invitation via email to access Reo.Dev.
\
**Seats Overview** – Here, you can see a summary of your total seats, additional seats, and how they're distributed between admins and users.
**Seats Usage** – Here, you can track how many of your allocated seats are currently in use.\
\
From the actions column, you can edit user details (name, designation and role) delete users and also resend the invite.
---
# 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.reo.dev/user-management/invite-a-teammate-to-reo.dev.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.
**Learn More About Roles:** [Check out this guide](/user-management/roles-and-permissions-admin-vs-user.md) to understand the detailed differences between Admin and User roles, including their permissions and capabilities.
**Step 5:** Click **Invite**. The new team member will receive an invitation via email to access Reo.Dev.
\
**Seats Overview** – Here, you can see a summary of your total seats, additional seats, and how they're distributed between admins and users.
**Seats Usage** – Here, you can track how many of your allocated seats are currently in use.\
\
From the actions column, you can edit user details (name, designation and role) delete users and also resend the invite.