> For the complete documentation index, see [llms.txt](https://docs.violetlabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.violetlabs.com/resources/administrative/invite-your-team.md).
# Invite your team
Navigate to your user icon and select **Users & Groups:**
## Import Users
To import a list of users to Violet, click **CSV Import**. Upload a file in the specified format to create the users.
## Create a Single User
Click +**Invite User** to create a new user, then fill in their first name, last name, and email address. They'll receive an email prompting them to verify their email address and create a password.
Click **+Group** to create a new user group.
To edit a user's information, click the edit icon in that user's row.
To remove a user, click the trash can icon.
### Guest Users
If a user is external to your organization and you need to limit their access to data in Violet, check the **Invite the user as a guest?** button when adding the user**.**
Add external users to user groups and to the [Programs](/features/programs.md) they are assigned to, giving them read-only access to that program's [Requirements](/features/requirements.md) and the ability to view and leave comments on requirements.
Guest users are *not* members of the "All Users" user group.
---
# 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://docs.violetlabs.com/resources/administrative/invite-your-team.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.
