> For the complete documentation index, see [llms.txt](https://wiki.datadike.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.datadike.com/pam/administration/identities/users-and-groups.md).

# Users and groups

Register the people who use the solution, group them, and control activation, expiry, and authentication requirements.

## What this is and when to use it

A user is someone who signs in to the solution — not a credential on a target. That distinction matters: the whole point of privileged access management is that a person authenticates as themselves and the solution supplies the target credential.

Groups exist so that authorizations can be written once for a team instead of once per person. Prefer granting to groups; it is the difference between an access review that takes an hour and one that takes a week.

{% hint style="info" %}
Users can be local to the solution or provisioned from a directory. For LDAP, Active Directory, Radius, and OAuth, see [LDAP and Active Directory](https://wiki.datadike.com/pam/administration/identities/ldap-and-ad.md).
{% endhint %}

## Before you start

* The **SYSADMIN** profile, or an organization administrator.
* The groups you intend to use, created beforehand — assigning at creation is easier than retrofitting.

## Steps

1. Open **Users › Users**.
2. Click **Create**.
3. Fill the identity: **Name**, **Username** (unique — it is the login), and **Email**, which is used for notifications, password recovery, and directory integration.
4. Assign the **user groups**. These define the scope of permissions the user will receive through authorizations.
5. Assign the **profiles** — what the person may do inside the console. See [Roles and permissions](https://wiki.datadike.com/pam/administration/identities/roles.md).
6. Set an **expiry date** if the access is temporary. Contractors and audits are the usual case, and setting it at creation is the only reliable moment.
7. Save.

## What you should see

![The Users screen](https://1085357737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7xzJyi9JVzRwnV6JzUho%2Fuploads%2Fgit-blob-17f2cd5b82def62d2ba0ad1dd1a4a1499a4487de%2Fusers-and-groups.png?alt=media)

**1** How many users the current filter returns. **2** One user row.

The user appears in the list. Two columns tell you whether they can actually sign in: **Activation** and **Expired**. Both must be right — a user can be active and still blocked by an expiry date in the past.

## How to verify it worked

1. Ask the user to sign in, or sign in as them.
2. Confirm the console shows the areas their profile should allow.
3. Confirm they see the assets their authorizations grant. If the profile is right and no assets appear, the problem is the authorization, not the user.

## Bulk actions

The **More actions** menu operates on the selected users:

| Action              | What it does                                                                                                    |
| ------------------- | --------------------------------------------------------------------------------------------------------------- |
| Remove selected     | Clears the selection or detaches from a grouping. **Does not delete the user** and does not change their status |
| Deactivate selected | Blocks sign-in while keeping permissions and data. Reversible                                                   |
| Activate selected   | Restores access to previously deactivated users                                                                 |
| Delete selected     | Permanently removes the users, their permissions, and associated data. **Not reversible**                       |
| Update selected     | Bulk-edits groups, profiles, tags, or applied policies                                                          |

{% hint style="warning" %}
**Remove** and **Delete** are not the same thing, and they sit next to each other. Remove clears a selection; Delete is irreversible. When in doubt, deactivate instead — it blocks access and keeps everything recoverable.
{% endhint %}

The toolbar also offers **Invite user**, to bring in a user from another organization, plus **Import** and **Export** in CSV and XLSX.

## Field reference

The user table carries far more columns than are shown by default. The ones that decide behavior:

| Field                             | What it means                                                              |
| --------------------------------- | -------------------------------------------------------------------------- |
| Username                          | The login used to authenticate. Must be unique                             |
| Email                             | Notifications, password recovery, and directory integration                |
| User groups                       | The groups the user belongs to, which define permission scope              |
| Source                            | How the account was provisioned — Local, LDAP/AD, OAuth                    |
| Organization role                 | Role at organization level, such as Operator or Auditor                    |
| System role                       | Granular role in the solution, such as Global Administrator or Log Auditor |
| Organization admin                | May manage the whole organization                                          |
| Super admin                       | Maximum permission across the entire system, including global settings     |
| Activation                        | When off, no login is possible                                             |
| Expired                           | Blocks the account after the expiry date                                   |
| MFA                               | Whether multi-factor authentication is required                            |
| MFA virtual bound                 | Whether an OTP app or device is linked                                     |
| Public key authentication allowed | Whether login by public key is permitted                                   |
| Needs password update             | Forces a password change on the next sign-in                               |
| Login blocked                     | Temporary block after failed attempts                                      |
| Valid                             | Internal flag indicating the account is in a consistent state              |

Informational columns include creation and update dates, last login, last API key use, last password change, creator, last updater, phone, Slack ID, tags, and a free-text comment.

## Common errors

| Symptom                                                 | Cause                                             | Fix                                                                                                                                         |
| ------------------------------------------------------- | ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| The user cannot sign in although the account looks fine | **Activation** off, or an expiry date in the past | Check both columns, not just activation                                                                                                     |
| Sign-in refused after several attempts                  | **Login blocked** after failed attempts           | Wait for the block to lift, or clear it                                                                                                     |
| The user signs in but sees nothing                      | No authorization covers them                      | The user record is not where access is granted. See [Authorizations](https://wiki.datadike.com/pam/administration/access/authorizations.md) |
| A directory user reappears after deletion               | The account is provisioned from a directory       | Remove or disable it at the source, not here                                                                                                |

## Related pages

* [Roles and permissions](https://wiki.datadike.com/pam/administration/identities/roles.md) — what a user may do in the console
* [Authorizations](https://wiki.datadike.com/pam/administration/access/authorizations.md) — what a user may reach
* [LDAP and Active Directory](https://wiki.datadike.com/pam/administration/identities/ldap-and-ad.md)
* [Multi-factor authentication](https://wiki.datadike.com/pam/administration/identities/mfa.md)
