# Users

The Users page gives administrators an overview of all registered users in the organisation. From here you can review user details and update their profile information.

To access it, go to **Settings** → **Users** → **Users** under the Organization Settings section of the sidebar.

## Adding users

Users can be added one at a time, or in bulk by importing a CSV file.

### Add a single user

1. Click **Add new user** above the user list.
2. Fill in the user's details in the form.
3. Save to create the user.


### Import users from CSV

Administrators can add multiple users at once by uploading a CSV file, instead of creating each user individually.

1. Click **Import users from CSV** above the user list.
2. Download the CSV template if needed — it is generated dynamically based on the user fields configured for the organization, so it always matches the expected format.
3. Fill in the template with the users to be added and upload the file.
4. The platform validates each row and field. If any errors are found, precise row-level and field-level messages are returned so issues can be identified and corrected before importing.
5. Once the import succeeds, the results are reported immediately and the user list refreshes automatically to show the newly added users.


#### CSV field formats

Some fields in the CSV template must follow a specific format:

| Field | Expected format |
|  --- | --- |
| **timeZone** | IANA format (e.g. `Europe/Rome`) |
| **dateTimeFormat** | One of: `dd/MM/yyyy | HH:mm`, `dd/MM/yy | HH:mm`, `dd-MMM-yy | HH:mm`, `dd-MMM-yyyy | HH:mm`, `dd MMMM yyyy | HH:mm`, `yyyy-MM-dd | HH:mm`, `yyyy-MMM-dd | HH:mm`, `yyyy MMMM dd | HH:mm`, `MMM d, yyyy | HH:mm`, `MMM-dd-yyyy | HH:mm`, `MMMM d, yyyy | HH:mm`, `MM/d/yyyy | HH:mm`, `dd.MM.yyyy | HH:mm`, `dd. MMMM yyyy | HH:mm`, `dd.MM.yy | HH:mm` |
| **languageCountry** | BCP 47 language code (e.g. `en-US`) |
| **phoneNumber** | Must include the country prefix (e.g. `+39...`) |


## How to view user details

1. Find the user in the list (use the **Search users** field to filter by name or email).
2. Click **Details** on the user's row.
3. The User Details page shows the following information:
  - **Given Name** and **Surname**
  - **Email**
  - **Phone Number**
  - **Interface language** — the UI language the user has configured
  - **Timezone**
  - **Date and time format**
  - **Country**
  - **Roles**


## How to edit a user's information

1. Open the user's detail page by clicking **Details**.
2. Click **Edit** (pencil icon) at the top of the form.
3. Update the relevant fields.
  1. Roles can be adjusted too. Remove roles from a user or add roles to grant more permissions.
4. Save your changes.


## Searching for users

Use the **Search users** field (top right of the list) to filter users by name or email. Results update as you type.

## Delete users

By clicking on the bin icon you can delete users from the organization. This action is permanently and cannot be undone.

## User list columns

| Column | Description |
|  --- | --- |
| **Given Name** | The user's first name |
| **Surname** | The user's last name |
| **Email** | The user's email address, used for login and notifications |
| **Phone Number** | The user's phone number, used for SMS-OTP authentication |
| **Enabled** | Checked if the user is enabled |


### Column Enabled

The Users list in Organization Settings shows an Enabled column for every user. It tells you whether the user account is currently active (enabled) or blocked (disabled).

| Value | Meaning |
|  --- | --- |
| Enabled | The account is active. The user can log in and use the system. |
| Disabled | The account is blocked. The user cannot log in. |


The column is informational only. You cannot enable or disable a user from the Users list.

Currently, a user can be enabled or disabled only through the Namirial admin portal, which is accessible only to authorized Namirial staff.

## User Details

## Service Accounts

The **Service Accounts** tab, next to **Users**, lets organizations generate, rotate, and revoke API access credentials for their integrations directly from the NSE interface, without requiring Back Office configuration.

A service account is an account used to authenticate integrations and automated processes against the Integration API. Unlike a regular user, a service account does not sign in through the standard login flow — it authenticates using a **Client ID** and credentials generated when the account is created.

The **Service Accounts** list shows all service accounts configured for the organization:

| Column | Description |
|  --- | --- |
| **Client ID** | The unique identifier used by the service account to authenticate against the API |
| **Email** | The email address associated with the service account |
| **Enabled** | Shows if this specific service account is enabled or disabled |
| **Actions** | Contextual actions available for the service account (⋯ menu) |


If no service account has been created yet, the list shows **No service accounts here yet.**

### Creating a service account

1. From the **Service Accounts** tab, click **New Service Account**.
2. In the **Create service account** dialog, enter:
  - **Name** (required) — an internal, descriptive name for the service account (e.g. `my-service-account`).
  - **Email** (required) — an email address associated with the service account (e.g. `service@example.com`).
3. Click **Create** to generate the service account, or **Cancel** to discard it.


Once created, the service account appears in the list with its generated **Client ID**, ready to be used to authenticate API calls.

### Searching for service accounts

Use the **Search** field (top right of the list) to quickly locate a service account by name, client ID, or email.

### Managing service accounts

In the last column **Actions** it is possible to rotate the secret as well as disabling access when a service account is no longer needed. If **Rotate secret** is clicked a dialog will be displayed that the current secret of the client Id will stop working immediately. This means that every integration using it must be updated with the new secret. After accepting the dialog the new secret will be displayed.

> **Note:** Rotating or disabling a service account immediately invalidates its credentials. Any integration still using them will no longer be able to authenticate against the API.