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

# User Management

User Management is available to Platform Admins under Administration → Users. It covers the full user lifecycle — creating accounts, managing roles, onboarding teams in bulk, and controlling access.

***

### Who can use User Management

User Management is exclusively admin-facing.

### Creating a single user

1. Go to **Administration → Users**.
2. Click **Create user**.
3. Fill in the required fields:
   * First name and last name
   * Email address (must be unique across the platform)
   * Role (select from system or custom roles)
   * Department *(optional)*
4. Choose whether to send the invitation immediately using the **Send invitation email now** toggle.
   * **On** — the user receives an invitation email as soon as you save.
   * **Off** — the account is created with Pending status. You can send the invitation later from the user's kebab menu (⋮).
5. Click **Create**.

> ℹ️ If the email address already exists, an inline error is shown and no duplicate record is created.

***

### Importing users from a CSV file

Use bulk import to onboard large teams from an ERP export or spreadsheet in one action.

#### Download the template

Before uploading, click **Download template** to get `users_import_template.csv`. The template includes all required columns and one example row.

#### Required columns

| Column        | Required | Description                                                          |
| ------------- | -------- | -------------------------------------------------------------------- |
| `email`       | Yes      | Must be a valid email and unique                                     |
| `first_name`  | Yes      | Max 80 characters                                                    |
| `last_name`   | Yes      | Max 80 characters                                                    |
| `role`        | Yes      | Must match an existing system or custom role name (case-insensitive) |
| `send_invite` | No       | `true` or `false` — defaults to `true` if omitted                    |

#### Upload and preview

1. Go to **Administration → Users**.
2. Click **Import users**.
3. Select your `.csv` file (max 1,000 rows / 5 MB).
4. Review the preview table:
   * ✅ **Valid rows** — ready to import
   * ⚠️ **Warnings** — importable but worth reviewing
   * ❌ **Errors** — must be fixed or skipped (invalid role, missing field, etc.)
   * 🔁 **Duplicate** — email already exists, will be skipped
5. Fix errors inline or check **Skip invalid rows**.
6. Click **Import** to run on confirmed rows only.

After import completes, you receive a confirmation email with a summary of how many users were created.

> ⚠️ Rows with emails matching existing users are automatically excluded — they are not re-created or updated.

***

### Filtering and finding users

Use the **Role** filter above the Users table to narrow the list by access level. This is useful for auditing who has Admin access or checking role assignments after a bulk import.

***

### Managing invitations

#### Send or resend an invitation

1. Find the user in the table.
2. Click the kebab menu (⋮) on their row.
3. Select **Send invitation** (never invited) or **Resend invitation** (Active status).
4. Optionally add a personal message in the confirmation modal.
5. Click **Send**.

A toast confirms the invitation was dispatched.

> ℹ️ Invitation links expire after **7 days**. Resending generates a new token and invalidates the previous one. Users who click an expired link see: *"This invitation has expired. Contact your administrator."*

### Changing a user's role

#### Inline (single user)

Click the role dropdown directly in the user's table row and select a new role. The change saves immediately. If it fails, the dropdown reverts and an error toast is shown.

#### Bulk role change&#x20;

Select multiple users using the checkboxes, then choose **Change role** from the bulk action bar. Confirm the new role in the modal to apply it to all selected users.

***

### Deactivating users

Deactivation prevents a user from logging in without deleting their account, event history, or activity records. Deactivated users can be reactivated at any time.

#### Deactivate a single user

1. Click the kebab menu (⋮) on the user's row.
2. Select **Deactivate**.
3. In the confirmation modal, optionally toggle **Sign out active sessions immediately**.
4. Click **Confirm**.

The user's status changes to **Inactive** and their row appears at reduced opacity in the table.

#### Bulk deactivation

Select multiple users and click **Deactivate** in the bulk action bar. All selected users are deactivated and their sessions invalidated.

#### Reactivating a user

Click the status dropdown on an Inactive user's row and change it to **Active**. The user will need to use their existing password or request a reset to log back in.

> ⚠️ You cannot deactivate the last Platform Admin. Assign another user as Admin first.

***

### Password and MFA management

#### Reset a user's password

1. Click the kebab menu (⋮) on the user's row.
2. Select **Reset password**.
3. Confirm the recipient email in the modal.
4. Optionally toggle **Force sign-out all sessions**.
5. Click **Send**.

The user receives a password reset email with a one-time link valid for **24 hours**.

#### Reset a user's MFA

1. Click the kebab menu (⋮) on the user's row.
2. Select **Reset MFA**.

MFA is unlinked immediately. The user will be prompted to re-enrol on their next login if MFA is required by your company policy.

***

### Email notifications

The following emails are sent automatically based on user management actions.

| Trigger                                     | Recipient                | Link expires                  |
| ------------------------------------------- | ------------------------ | ----------------------------- |
| User created with invite                    | New user                 | 7 days                        |
| Invitation resent                           | Pending user             | 7 days (old link invalidated) |
| Password reset triggered by admin           | User                     | 24 hours                      |
| MFA reset by admin                          | User                     | N/A — informational           |
| User deactivated *(if notify toggle is on)* | Deactivated user         | N/A                           |
| Bulk import completed                       | Admin who ran the import | N/A                           |

***

### Activity log

All user management actions are recorded in the platform Activity Log with a timestamp, the actor who performed the action, and before/after values where applicable.

Logged actions include:

* User created, deactivated, reactivated, or deleted
* Password changed or reset
* MFA reset
* Role or permission assigned or removed
* Custom role created, modified, enabled, disabled, or deleted


---

# 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.fairmarkit.com/admin/users-and-permissions/user-management.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.
