For the complete documentation index, see llms.txt. Markdown versions of documentation pages are available by appending .md to page URLs.
Skip to content
September 22 — Documentation updated for compatibility with the latest PAM version (5.3.0).

Vault entries and folders

Credentials no automation manages: folders, sharing with named permissions, search, revealing behind MFA, the password history, and importing from a spreadsheet.

What this is and when to use it

Not every credential belongs to a managed asset. A certificate authority login, a supplier portal, a registrar, a licence account: things a team needs, that no rotation job can reach, and that otherwise end up in a spreadsheet, a text file or a browser.

Vault holds those. Each credential is an entry; entries live in folders; and both can be shared with named users and groups under explicit permissions. Revealing a secret requires a second factor, and every entry keeps the history of its previous passwords.

Every user has their own vault, tied to their identity in the console. There is no shared corporate vault: anything another person sees, they see because the owner shared it with them.

This is a different store from the secrets of managed accounts. A managed account's credential is held against an asset and is rotated, pushed and used to open sessions; see The credential vault. A Vault entry is held by a person, shared by hand, and never pushed anywhere. Use managed accounts for what the solution connects to, and Vault for everything else the team has to keep.

Vault does not fill credentials into websites opened outside DataDike PAM, the way a browser password manager extension does. An entry is used by revealing or copying it in the console. A credential that must be injected into a session, with the session recorded, belongs to a managed account.

Before you start

  • Vault is under Workbench › Vault. Every console user has one.

  • MFA configured for your user. Revealing or copying a password, deleting an entry and deleting a folder all ask for a second factor. See Multi-factor authentication.

The Vault screen

The Vault screen, with folders, credentials and the detail pane

1 How many folders and credentials the vault holds. 2 A folder, with its own count and its private state. 3 A credential shared with someone else. 4 New Credential, which opens the entry form.

The screen reads from left to right, from the widest scope to the detail:

Pane
What it shows
What you do there

Vault Folders (left)

The folder and credential counts, a search box, All Credentials, and every folder with its owner, date and sharing state

Create a folder (+), import credentials, and open a folder's menu (…)

Credential list (centre)

The entries of the selected folder, or of All Credentials

Search, and create a New Credential

Detail (right)

The fields of the selected entry, its ID, and its Metadata: who it is shared with, creation date, last update

Reveal and copy, share, edit, delete

The entry ID is the reference to quote when you contact DataDike support about a specific entry.

Folders

Every user gets a Default folder, created automatically. It cannot be renamed, changed or deleted, and it is where anything without an explicit folder lands.

Beyond that, you create folders freely with the + in the folder pane. Each folder shows its owner, its creation date, how many credentials it holds, and either State private or the number of active shares. Its menu (…) holds Share Folder, Rename and Delete folder.

Two behaviours are worth knowing before you organise anything:

  • An entry that arrives without a folder, such as an import row with the folder column empty, goes to your Default folder.

  • Deleting a folder does not delete its entries. They are moved to Default. That is deliberate, and it means a folder deletion is never a credential loss. The deletion still asks for a second factor.

Since a folder is the unit you share in one go, organise folders by the kind of access they hold: infrastructure, corporate SaaS, supplier portals. Sharing one folder then grants exactly one kind of access.

Entries

New Credential opens a form in three steps. Fields marked with an asterisk are required. Start it from All Credentials or from a folder where you may create entries; with the Default folder open, the console asks you to pick another view first.

  1. Credentials: the Username and the Password. The eye icon shows or hides the password, and the button next to it opens the password generator.

  2. Sharing: the users and groups who get the entry from the start, in Shared With Users and Shared With Groups. This step is optional; you can share later.

  3. General Information: the Folder Name, the Site or Application, the URL and a Description.

Create saves the entry, with its password encrypted, in the folder chosen.

Field
Required
What it holds

Site or Application

Yes

The name of the service

Username

Yes

The login or e-mail

Password

Yes

The secret. Stored encrypted

URL

No

Address of the service

Folder Name

Yes

Comes filled in with the folder open in the list, or with your Default folder. Any folder where you may create entries can be chosen, Default included

Description

No

Free note

The same owner cannot keep two entries with the same site and username.

Use the password generator for every new entry, and fill in the URL and the description even though they are optional: an entry that says what it opens is an entry nobody uses by mistake.

To move an entry to another folder, edit it and change Folder Name. Only the owner of the entry can change its folder.

Using an entry

Select an entry and the detail pane shows its fields, with the password masked.

  • Copy the username: the copy icon puts it on the clipboard directly.

  • Reveal or copy the password: either icon asks for MFA confirmation, then opens a window with the site, the username and the password, masked until you show it, each with its own copy button.

Reading a password in clear is a separate, read-only operation and requires MFA confirmation, regardless of the permission that granted access to the entry. Passing the normal login is not enough.

The icons at the top of the detail pane share, edit and delete the entry. Which of them you get depends on the permission you hold. Deleting an entry asks for confirmation and a second factor, and a deleted entry cannot be recovered.

Finding an entry

The search box above the list, Search in followed by the name of the open folder, filters the entries as you type. It matches the site, the username, the URL and the description, and ignores capitals. To search the whole vault, open All Credentials first.

The folder pane has its own search box, which filters the folders by name.

Sharing

An entry or a folder is shared with users, with groups, or with both. Each share carries up to four permissions, and they are cumulative. The share window labels them View, Create, Edit and Delete; the tables below use their technical names.

Permission
What it allows

can_view

See the folder or entry, and copy or reveal its secret behind MFA. The default when nothing is specified

can_create

Create entries inside the folder. Only meaningful on a folder

can_update

Edit the entry

can_delete

Delete the entry

Three rules decide what someone can actually do:

  1. can_update and can_delete imply can_view. You do not have to grant view separately.

  2. Only the owner manages sharing. Nobody who received a share can re-share it, rename the folder, or change who else has it.

  3. Folder and entry permissions combine, and the more permissive wins. can_view on the folder plus can_update on one entry means the person edits that entry and only reads the rest.

The share window has two parts. Currently Shared With lists who already has access and with which permissions; Custodians is where you search for the users and groups to add. Nothing changes until you click Save. Removing a person takes effect on their next access.

Share at the narrowest scope that does the job: one entry rather than its folder, when one entry is what the person needs. Review Currently Shared With from time to time, and after anyone changes role or leaves.

Who can do what

Action

Owner

can_view

can_create

can_update

can_delete

See the entry in the list

Yes

Yes

Yes

Yes

Yes

See the entry detail

Yes

Yes

Yes

Yes

Yes

Reveal the secret, with MFA

Yes

Yes

Yes

Yes

Yes

Create an entry in the folder

Yes

No

Yes

No

No

Edit the entry

Yes

No

No

Yes

No

Delete the entry

Yes

No

No

No

Yes

See the folder

Yes

Yes

Yes

Yes

Yes

Create, rename, delete a folder

Yes

No

No

No

No

Change the folder's sharing

Yes

No

No

No

No

Password history

Every time the password of an entry changes, the previous value is kept. For each replaced password the history records:

Field
What it holds

Secret

The previous value

Date

When it was replaced

User

Who replaced it

The history is read through the API, behind the same MFA confirmation as a reveal: GET /api/v1/vault/vault-entries-secret/{id}/history/, where {id} is the entry ID shown in the detail pane. Anyone who can see the entry can read its history. See API for how a client authenticates.

This is what answers "what was this password in March", and it is also how a change made by the wrong person is undone.

Importing from a spreadsheet

Credentials already living in a spreadsheet, or exported from another tool, can be loaded in one pass.

  1. In the folder pane, click the upload icon to open Import credentials.

  2. Download the XLSX Template or the CSV Template. In the XLSX, the required columns are marked in red and the optional ones in blue.

  3. Fill it in, keeping the header. The headers are always in English, whatever the console language: Site or Application, URL, Username, Password, Folder name and Comment, which holds the description.

  4. Tick Update existing credentials if the file should overwrite entries you already have with the same site and username. Leave it unticked to only add: rows that match an existing entry are then skipped.

  5. Drag the file onto the window, or click to browse for it, and click Upload.

The result reports how many entries were created, updated and skipped, and lists any row that failed with its row number.

A folder named in the file that does not exist yet is created automatically. A row with no folder goes to Default.

Only .xlsx and .csv are accepted.

How to verify it worked

  1. Create an entry, share it with one colleague as can_view, and ask them to open it. Confirm they see it, and confirm the reveal asks them for a second factor.

  2. Ask the same colleague to try to edit it. They should not be able to. This is the check that catches a share granted wider than intended.

  3. Change a password and read the entry's history through the API. The previous value, the date and your username should be there.

  4. After an import, count the entries and open one from a folder the file created. A row whose folder name had a typo creates a folder, it does not fail, so a miscount is how you find those.

Common errors

Symptom
Cause
Fix

Someone can edit entries you meant them only to read

They hold can_update on the folder, which covers every entry in it

Move the permission to the individual entry

A share you added disappeared

Shares are replaced wholesale, not merged. A later update submitted without it removed it

Resubmit the complete list of shares

New Credential answers that the default folder does not allow creating a new credential

The Default folder is open in the list

Open All Credentials or another folder, and pick the folder in Folder Name

An entry is not in the folder you expected

It came from an import row with no folder, so it went to your Default

Edit it and change Folder Name

Entries survived a folder you deleted

That is the intended behaviour

They are in Default

The secret will not reveal

MFA is not confirmed, or not configured for the user

The import is refused

The file is not .xlsx or .csv, or it is corrupt

Re-export from the template

Imported rows were skipped

They match existing entries and Update existing credentials was off

Import again with the option ticked, if overwriting is what you want

A colleague cannot create entries in a folder you shared

can_view does not include creating

Grant can_create on the folder

Last updated

Was this helpful?