> 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/accounts/managed-accounts.md).

# Managed accounts

Register, test, and maintain the credentials the solution uses to authenticate on your assets.

## What this is and when to use it

A managed account is a credential on an asset that the solution stores and supplies on the user's behalf. **Accounts › Accounts** is where they are registered, tested, edited, and removed.

There are two kinds, and they behave differently:

| Kind                | Where it comes from                                    | Behavior                                   |
| ------------------- | ------------------------------------------------------ | ------------------------------------------ |
| **Common account**  | Registered by hand, or brought in by a collection task | Static — it exists until you remove it     |
| **Virtual account** | Created by an authorization rule at connection time    | Dynamic — it exists because a rule says so |

This page is about common accounts. Virtual accounts are configured on the [authorization](https://wiki.datadike.com/pam/administration/access/authorizations.md) that creates them.

## Before you start

* The asset already registered under **Environment › Assets**.
* The credential itself — password, SSH key, token, access key, or API key.
* **MFA enabled** on your own account to reveal a secret or export accounts.

## Steps

1. Open **Accounts › Accounts**.
2. Click **Create**.
3. Select the **asset** the credential belongs to.
4. Fill the **username** and the secret — password, SSH key, or another supported type.
5. Set **su/sudo** if the account must elevate after login.
6. Mark **Privileged** if the account holds administrative rights on the target.
7. Choose the **Identity type** of the account; see [Identity types](#identity-types).
8. Save.
9. Select the account and click **Test selected** to confirm it authenticates.

{% hint style="info" %}
To attach the same credential to many assets at once, use **Add from template** instead of registering it repeatedly. See [Account templates](https://wiki.datadike.com/pam/administration/accounts/account-templates.md).
{% endhint %}

## What you should see

![The Accounts screen, listing the credentials registered against each asset](https://1085357737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7xzJyi9JVzRwnV6JzUho%2Fuploads%2Fgit-blob-ba45857b0b023400a382b80991e839c30ddc919e%2Fmanaged-accounts.png?alt=media)

**1** How many accounts the current filter returns. **2** One account row, with its asset and the date it was last updated.

The account appears in the list against its asset, with the date of the last update. The side panel offers two trees to filter by — **Asset tree**, the folder structure, and **Type tree**, by platform category.

## Identity types

Managed accounts belong to non-human identities: the people are the users of the solution. The **Identity type** says which kind of identity owns the account, and **Accounts › Accounts** has one tab per type, next to **All**:

| Tab                      | Identity type        | Accounts it holds                                                       |
| ------------------------ | -------------------- | ----------------------------------------------------------------------- |
| **Machines**             | **Machine**          | AD computer accounts, servers, devices and network equipment            |
| **Applications**         | **Application**      | Applications, service principals and API identities                     |
| **AI agents**            | **AI agent**         | AI agents, copilots and autonomous agents                               |
| **Workloads & services** | **Workload/service** | Service accounts, containers, Kubernetes, jobs and automation pipelines |

An account created from one of these tabs gets that tab's type. The type can be changed later by editing the account. Accounts created without a type are classified as **Machine**.

## How to verify it worked

Registering a credential does not prove it works on the target.

1. Select the account and run **Test connectivity** from its **Quick update** panel, or **Test selected** from the toolbar.
2. Open a session to the asset using that account. A successful login is the only proof that the stored secret and the target agree.
3. If the account is meant to be privileged, confirm it carries the **Privileged** marking.

An account that saves cleanly and fails the connectivity test is the normal result of a wrong password or a missing protocol — not of a wrong registration.

## Toolbar

| Control           | What it does                                     |
| ----------------- | ------------------------------------------------ |
| Create            | Registers an account by hand                     |
| Add from template | Brings the credential in from a template         |
| Test selected     | Tests connectivity of the selected accounts      |
| Clear secret      | Wipes the stored secret of the selected accounts |
| Update selected   | Bulk-edits the selected accounts                 |
| Delete selected   | Removes them                                     |
| Upload / Export   | Bulk import and export, CSV or XLSX              |
| Tags              | Filters by tag                                   |
| List preferences  | Chooses the visible columns                      |

## Account details

Clicking an account's name opens its page, with two tabs:

* **Basic** — ID, Name, Username, Secret type, Tags, Switch from, Asset, Version, Source and Source ID, Connectivity, Organization, LDAP account, Active, Has secret, creation and update dates, Created by, Description
* **Activities** — the change history of this account

The **Quick update** panel on the right holds the three actions used most: **Active**, **Privileged**, and **Test connectivity**.

## Password history

Every stored secret is versioned. The account keeps its previous values with the date and time each was recorded, so a credential changed outside the solution can still be recovered from the version that was in force.

## Common errors

| Symptom                                                    | Cause                                                | Fix                                                                  |
| ---------------------------------------------------------- | ---------------------------------------------------- | -------------------------------------------------------------------- |
| Connectivity test fails                                    | Wrong secret, or no management protocol on the asset | Check the secret, then confirm the asset has SSH or WinRM registered |
| The account cannot be rotated                              | The asset's only protocol is RDP                     | Rotation needs a management channel. Add WinRM or OpenSSH on Windows |
| The secret cannot be revealed                              | MFA is not enabled on your account                   | Enable MFA and retry                                                 |
| The same credential exists on many assets and drifts apart | It was registered per asset instead of as a template | Move it to a template                                                |

## Related pages

* [Account templates](https://wiki.datadike.com/pam/administration/accounts/account-templates.md)
* [The credential vault](https://wiki.datadike.com/pam/administration/accounts/vault.md)
* [Rotate credentials](https://wiki.datadike.com/pam/administration/accounts/rotation.md)
* [Collect accounts from an asset](https://wiki.datadike.com/pam/administration/accounts/discovery-of-accounts.md)
* [Authorizations](https://wiki.datadike.com/pam/administration/access/authorizations.md) — where virtual accounts are defined
