> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/settings/user-management/managing-users.md).

# Managing Users

Users with the `Manage Users & Permissions` permission can create, update, disable, enable, or delete user accounts.

## **User Statuses**

SeaLights distinguishes between different user statuses:

* **Active:** User can log in.
* **Inactive:** User cannot log in (temporarily blocked).
* **Deleted:** User account is removed and cannot log in.

{% hint style="info" %}
SSO users are provisioned as active upon their initial login. To permanently remove an SSO user, an Admin must ensure they are blocked within the organization's Identity Provider; otherwise, deleting them from SeaLights settings will only result in their re-creation on the next login.
{% endhint %}

User accounts managed directly by SeaLights (not via SSO) have a password status:

* **OK:** User can log in with their current password.
* **Temporary:** User must change their password upon first login.
* **Temporary-Expired:** User cannot log in until an administrator resends a temporary password.
* **Reset-Code:** User can log in after setting a new password using a confirmation code.
* **Reset-Code-Expired:** User cannot login until admin resets password or user uses forgot password.

***

## **Creating a User**

### Adding Individual User Accounts

1. In the `Users` list under `Users & Permissions`, click `Create User`.
2. Provide the user's first name, last name, email address, and assign a role.
3. Optionally, grant the user with specific permissions.
4. Click "Create".&#x20;
5. Optionally, assign the user to specific groups.

Upon creation, new users receive a welcome email with their username and a temporary password. This initial password allows them to log in, but they will then be immediately required to create a new, secure password.&#x20;

The temporary password has a 15-day expiry; should it expire, an administrator with `Users & Permissions` privileges can resend the welcome email to issue a new temporary password.

### Creating Multiple Users (Bulk Upload)

You can add multiple users simultaneously using a CSV file:

1. In the `Users` list under `Users & Permissions`, click `Bulk Create Users`.
2. Download the `Blank CSV Template` provided in the dialog.
3. Open the downloaded CSV file and fill in the details for each new user. Make sure not to remove the column headers. You'll need to provide:
   1. **Email address**
   2. **First name**
   3. **Last name**
   4. **Role** (e.g., `user-limited`, `user`, `user-admin`, or `user-devops`). \
      A handy `Lookup` button is available in the dialog to show valid role values.
   5. **(Optional) Groups:** A list of group names separated by `$$` (e.g., `GroupA$$GroupB`). \
      Use the `Lookup` button in the dialog to show a list of existing groups in your organization.
   6. **(Optional) Permissions:** A list of specific permissions separated by `$$`. \
      Use the `Lookup` button in the dialog to show valid permission values.
4. Save your completed CSV file.
5. If you've included group names in your CSV that don't yet exist in SeaLights and want them created automatically, check the **"Create group if... "** box in the  `Bulk Create Users`  dialog.\
   ![](/files/vMi9YoGIZ9FyG7tpVW1G)
6. Click on `Attach CSV File`  to select your saved file and press the `Upload` button.
   1. If any errors occur during the upload, you'll receive detailed feedback for each affected row.

Upon creation, new users receive a welcome email with their username and a temporary password. This initial password allows them to log in, but they will then be immediately required to create a new, secure password.&#x20;

The temporary password has a 15-day expiry; should it expire, an administrator with `Users & Permissions` privileges can resend the welcome email to issue a new temporary password.

***

## **Updating a User**

1. In the `Users` list, find the user using the search bar or by navigating the list.
2. Click on the user name.
3. You can update their first name, last name, role, permissions, and assigned groups.

***

## **Disabling/Enabling a User**

To temporarily block or restore a user's access:

1. In the `Users` list, locate the user.
2. Hover over the user and click the toggle switch, on the action buttons column.\
   ![](/files/GQaNOqsTqyX2GsiIK1si)
3. Confirm the action when prompted.

To enable an inactive user:

1. Hover over the user and click the toggle switch, on the action buttons column.\
   ![](/files/FepM888aYbQCDsJSoKqP)
2. Confirm the action when prompted.

***

## **Deleting a User**

Deleting an account permanently removes the user's access.

1. In the `Users` list, locate the user.
2. Hover over the user and click the delete button.
   1. This action is available only after disabling the user.
3. Confirm the deletion when prompted.

***

<figure><img src="/files/xxnnWpjgNHnBw4RtKgGO" alt=""><figcaption></figcaption></figure>


---

# 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.sealights.io/knowledgebase/settings/user-management/managing-users.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.
