> For the complete documentation index, see [llms.txt](https://docs.arnica.io/arnica-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arnica.io/arnica-documentation/platform-operations/tenant-management/inviting-members.md).

# Inviting Members

To join an existing Arnica tenant, users must be invited. Any member of the tenant can add new users through the **Admin → Security → Users & Roles** page.

## How to invite a member

1. Navigate to **Admin → Security → Users & Roles**.
2. Enter the user's email address in the **Email** field.
3. Click **Invite**.

The invited user will receive a welcome email with a personalized link to set their password. Once they sign in, they will be redirected into your tenant.

For full details on managing users, roles, and permissions, see [Users & Roles](/arnica-documentation/platform-operations/security/users-and-roles.md).

## Supported permissions

Owners can invite additional members. Invited members can perform all administrative tasks except inviting additional members.

## Tenant membership

Each Arnica user can only belong to one tenant at a time. If a user needs to move to a different tenant, they must leave their current one first via **Profile menu → Edit Account → Leave**.


---

# 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.arnica.io/arnica-documentation/platform-operations/tenant-management/inviting-members.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.