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

# User Management

> Inviting, managing, and removing dashboard users.

Create and manage the accounts that can sign in to the dashboard, set each user's role, and scope what they can see through teams. This page requires the **manage users** permission .

***

## Summary stats

The top of the page displays headline counts:

* **Total accounts** — the number of user accounts in the system.
* **Admin count** — how many accounts hold the Admin (or Owner) role.
* **Temporary-password count** — accounts still using the temporary password set at creation (i.e., the user has not yet changed it under Settings).

## Filter bar

A filter bar at the top of the user list lets you narrow results quickly:

* **Search** — type a username, role, or team name to filter the list.
* **Role filter** — a dropdown to show only users with a specific role (Admin, Analyst, Responder, Viewer).
* **Team filter** — a dropdown to show only members of a specific team.
* **Result count** — an indicator showing how many users match the current filters.

***

## Roles and permissions

Each user has one role. The role picker includes an info tooltip describing each:

| Role | What it can do |
| - | - |
| **Admin** | Full access, including managing users, teams, and the audit log. |
| **Analyst** | Full data access and detection rule management, but no admin pages. |
| **Responder** | Like analyst, but cannot create, edit, or delete detection rules. |
| **Viewer** | Read-only access plus the AI query page. |
| **Owner** | Same as admin; fixed on the seeded account and cannot be assigned. |

The **owner** role is special: it's locked to the seeded account, can't be assigned to anyone else, and can't be changed, disabled, or deleted.

### Global vs scoped admins

A **global admin** (an admin or owner with no team) can see everything. A **scoped admin** is an admin assigned to one or more teams, they only manage their subtree, and must assign at least one in-scope team when creating or editing a user.

***

## Adding users

There is no email invitation. Hilt runs inside your own cloud account and has no mail server, so the dashboard never sends anything to a new user. You create the accounts and hand over the credentials on a channel you already trust.

**Add users** opens a drawer with:

* **Usernames**: one or more. Separate them with a semicolon or a new line. Each name is what that person types to sign in. Nothing is emailed.
* **Role**. A role is required. Viewer is read-only.
* **Teams**: which teams the users belong to, controlling the hosts they can see. Scoped admins must pick at least one.

Submitting creates every account immediately, each with its own random temporary password. The drawer then shows a ready-to-send message per person: sign-in URL, username, and temporary password. **Copy it before closing** — the password is stored only as a hash and is not shown again. If it is lost, use **Reset password** on that user.

Each account is flagged with a **temporary password** until the user sets their own under Settings.

***

The ⋯ actions menu offers (availability depends on whether the target is you, an owner, or another user):

| Action | Notes |
| - | - |
| **Rename user** | Change the username |
| **Edit role & team** | Change role and team membership (not available for the owner) |
| **Reset password** | Set a new temporary password |
| **Disable / Enable account** | Block or restore sign-in (not for the owner) |
| **Delete user** | Permanently remove the account (not for the owner) |

> [!NOTE]
>
> **Self-service restriction**: when viewing your own account, only the **Rename user** action is available. You cannot edit your own role, reset your own password from admin, disable, or delete your own account.

> [!NOTE]
>
> **Non-admin users** cannot rename other users. The rename action is only available to admins and the owner.

### Editing role and team

The edit drawer lets you change the role and team membership. For the owner, it instead shows a note that the owner role is fixed and offers nothing to change.

### Resetting a password

Sets a new temporary password (minimum 8 characters). The user must sign in again and should choose their own password under Settings.

### Disabling vs deleting

* **Disable** is reversible: disabled users can't sign in, but you can re-enable them anytime.
* **Delete** is permanent: it removes the account and all its sessions. Audit history keeps entries under the username, but the account can't be recovered.

Both actions ask for confirmation first.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.