> ## Documentation Index
> Fetch the complete documentation index at: https://documents.tmsone.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Inviting Users

TMS ONE supports two methods for adding users to your organisation or project: **manual creation** (you set up the account directly) and **email invite** (the user receives a signup link and completes their own registration).

***

## Organisation-level vs project-level users

There are two contexts where users are managed in TMS ONE:

| Context                | Where                    | Who manages it                    |
| ---------------------- | ------------------------ | --------------------------------- |
| **Organisation users** | Organisation admin panel | Client admin (organisation owner) |
| **Project users**      | Inside a project → Users | Project admin                     |

Both follow the same two-method approach, with slightly different fields.

***

## Inviting users to a project

### Navigate to Users

From the left sidebar inside your project, click **Users**. You'll see a list of all users currently on the project.

### Click Create User

Click the **Create User** button to open the invitation form.

### Choose an invitation method

You'll be presented with two tabs:

***

#### Option A: Add manually

Use this when you want to create the account yourself and share credentials directly.

<ParamField path="User Type" type="select" required>
  The user's role type within the project.

  * **Admin** — Full access to project settings and user management
  * **QA User** — Access to test cases, runs, defects, and other QA features
</ParamField>

<ParamField path="First Name" type="text" required>
  Minimum 3 characters.
</ParamField>

<ParamField path="Last Name" type="text" required>
  Minimum 3 characters.
</ParamField>

<ParamField path="Email" type="text" required>
  Must be a valid email address. Used as the login identifier.
</ParamField>

<ParamField path="Phone Number">
  Optional. Digits only, 10 characters.
</ParamField>

<ParamField path="Role" type="select" required>
  Assign a role to control what this user can see and do. Roles are configured in **Roles & Permissions**. Only active roles appear in this dropdown.
</ParamField>

<ParamField path="Password" type="string">
  A temporary password is auto-generated by the system. It is shown read-only — copy and share it with the user. They can change it after first login.
</ParamField>

Click **Save** to create the account.

***

#### Option B: Generate signup link

Use this to send an invitation email. The user clicks the link and completes their own registration.

<ParamField path="User Type" type="select" required>
  Admin or QA User — same as above.
</ParamField>

<ParamField path="Email" type="text" required>
  The email address the invitation will be sent to.
</ParamField>

<ParamField path="Role" type="select" required>
  The role that will be assigned when the user completes signup.
</ParamField>

Click **Send Invite**. The user receives an email with a link to complete their registration.

***

## Managing existing users

From the Users list you can:

| Action     | Description                                                                                              |
| ---------- | -------------------------------------------------------------------------------------------------------- |
| **Edit**   | Update the user's details, role, or user type. Toggle the **Active** switch to enable or disable access. |
| **Delete** | Permanently remove the user from the project                                                             |

<Warning>
  Deactivating a user (setting Active to off) prevents them from logging in but preserves their history — test cases they created, defects they logged, and runs they executed remain intact.
</Warning>

***

## Assigning users to a project at creation

When [creating a project](/qa/creating-a-project), you can pre-assign QA users using the **Assign User** multi-select field. Users assigned here are added to the project immediately on creation.

***

## What's next?

<CardGroup cols={2}>
  <Card title="Roles & Permissions" icon="shield" href="/admin/roles-and-permissions">
    Control what each user type can see and do
  </Card>

  <Card title="Creating a Project" icon="folder-plus" href="/qa/creating-a-project">
    Set up your first project and assign your team
  </Card>
</CardGroup>