> For the complete documentation index, see [llms.txt](https://help.craftsmanplus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.craftsmanplus.com/company-settings/users.md).

# Users

Add, edit, and remove the people in your company, set their roles, and choose who can manage your team.

The **Users** tab is where company admins manage their team: add people, set what they can do, reset passwords, and remove or restore access.

To get there, open **Company Settings** from your profile menu in the top right and select **Users** from the left navigation, under **Account**.

{% hint style="info" %}
Only company admins can open Company Settings and the Users tab. Your company's first admin is set up by CRAFTSMAN+. From then on, admins can make other people admins. See [Roles & Permissions](/company-settings/users/roles-and-permissions.md).
{% endhint %}

***

### Active Users

The **Active Users** list shows everyone in your company, with their **Role** and whether they're an **Admin**. Click the **Name** column to sort by name. Use **Search Users...** to find people by name or email.

Changes to a role or the Admin toggle save right away.

* **Role:** choose **Creator** or **Viewer**. See [Roles & Permissions](/company-settings/users/roles-and-permissions.md) for what each one can do.
* **Admin:** turn this on to let someone manage users in Company Settings. Admin works alongside a role, so a Creator or a Viewer can be an admin.

Each row also has buttons to **Edit User**, **Reset Password**, and **Remove User**.

{% hint style="info" %}
You can't change your own role or admin access, or remove yourself. Another admin has to do it.
{% endhint %}

***

### Adding a User

1. Click **+** (**Add User**) next to **Active Users**.
2. Enter their **First Name**, **Last Name**, and **Email**.
3. Click **Confirm**.

The new user is added as a **Viewer** with Admin off, and they're emailed a link to set their password. Change their role or turn on Admin if they need more access.

If the email is already in use, you'll see a warning. If the person was removed from your company, restore them from **Removed Users** instead.

***

### Editing a User

Click **Edit User** to change someone's name or email, then click **Confirm**.

***

### Resetting a Password

Click **Reset Password** and confirm. The user's current password stops working right away, and a reset link is sent to their email.

***

### Removing and Restoring Users

Click **Remove User** and confirm to remove someone. They lose access to CRAFTSMAN+ right away, and they move to the **Removed Users** list. If they were a Creator, their Creator seat is freed up.

To bring someone back, click **Restore User** on their row in **Removed Users**. Restored users come back as a **Viewer** with Admin off, so set their role and admin access again if they need it.


---

# 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://help.craftsmanplus.com/company-settings/users.md?ask=<question>&goal=<user_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.
