Infisical is the open-source platform for securing secrets, certificates, access, and AI Agents.
TypeScript acmeagentsai-agentscertificate-managementdevsecopsenvironment-variableskubernetesopen-sourcepampkipostgresprivate-caprivileged-access-managementsecret-managementsecret-managersecretssecrets-managementsecuritysecurity-toolsvault
---
title: "Secrets management projects"
sidebarTitle: "Projects"
description: "Learn about Infisical projects and how to manage secrets across environments."
---
A secrets management project in Infisical is a dedicated workspace for managing application secrets such as API keys, database credentials, configuration, etc. used by your applications.
Secrets are organized into a clear hierarchy of environments, folders, and individual secrets, making it easy to manage values across different stages of your development lifecycle (e.g., development, staging, production).
The short video below walks through Infisical projects, covering how secrets are organized into environments and folders, and the dashboard features available to manage them.
<br />
<div style={{ position: "relative", paddingBottom: "56.25%", height: 0, overflow: "hidden", maxWidth: "100%" }}>
<iframe
src="https://www.youtube.com/embed/3dPwEhCU00E"
title="YouTube video player"
style={{ position: "absolute", top: 0, left: 0, width: "100%", height: "100%", border: 0 }}
allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
allowfullscreen
></iframe>
</div>
<br />
## Project environments
Infisical lets you split secrets into environments (e.g., development, staging, production) for both visual and organizational structure. You can customize environments in project settings.
The short video below walks through how to use environments in Infisical.
<br />
<div style={{ position: "relative", paddingBottom: "56.25%", height: 0, overflow: "hidden", maxWidth: "100%" }}>
<iframe
src="https://www.youtube.com/embed/9foN4T3VP-s"
title="YouTube video player"
style={{ position: "absolute", top: 0, left: 0, width: "100%", height: "100%", border: 0 }}
allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
allowfullscreen
></iframe>
</div>
<br />

## Secrets overview
The **Secrets Overview** page captures a bird's-eye view of secrets and [folders](/documentation/platform/folder) across environments.
This is useful for comparing secrets, identifying if anything is missing, and making quick changes.

## Secrets dashboard
The **Secrets Dashboard** page appears when you select a specific environment to manage its secrets.

### Secrets
To add a secret, select **Add New** > **New Secret** at the top of the dashboard.
In a new project, you can fill the dashboard in one go by dropping a `.env`, `.json`, `.yml`, or `.csv` file onto the upload pane:

To upload more secrets later, select **Add New** > **Upload Secrets**, then upload a file or paste its contents.
To delete a secret, hover over it, select the three dot menu on the right, then select **Delete Secret**.

To delete several secrets at once, select their checkboxes, then select **Delete** at the top.

### Import nested JSON as folders
If the JSON you upload or paste through [Upload Secrets](#secrets) contains nested objects, the review step shows an **Import Nested Objects as Folders** toggle below **Overwrite Existing Secrets**. The toggle is off by default. With the toggle off, top-level keys with `null` values are skipped. Each other top-level key becomes one secret, and Infisical stores nested objects as JSON strings.
If you turn the toggle on:
- Each nested object becomes a folder inside the path you're uploading into (Infisical reuses folders that already exist)
- Each value in a nested object that isn't itself an object becomes a secret in that object's folder
- Arrays are stored as JSON strings, `null` as an empty value, and numbers and booleans as text
- **Overwrite Existing Secrets** still decides whether secrets that already exist are updated or skipped
For example, `{"data": {"item1": {"item2": "some-value"}}}` creates the secret `item2` with the value `some-value` in the folder `/data/item1`.
Folder names can only contain letters, numbers, dashes, and underscores (up to 255 characters). Secret keys can't be empty or contain a colon or forward slash. If any key breaks these rules, the review step lists it, and you can't upload until you fix the JSON.
### Search
To find a secret by name, type into the search bar.

Select the filter icon to narrow the list to one kind of resource, or to filter by tag. The resource types are folders, secrets, secret imports, secret rotations, dynamic secrets, honey tokens, and proxied services.

### Reveal values
To show every value at once, select **Reveal Values**.

### Download as .env
To export the secrets in the current folder as a `.env` file, select the download icon.
The short video below walks through tagging, comments, and personal overrides, three ways to organize, annotate, and customize secrets in the dashboard.
<br />
<div style={{ position: "relative", paddingBottom: "56.25%", height: 0, overflow: "hidden", maxWidth: "100%" }}>
<iframe
src="https://www.youtube.com/embed/bhprcVcIPMs"
title="YouTube video player"
style={{ position: "absolute", top: 0, left: 0, width: "100%", height: "100%", border: 0 }}
allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
allowfullscreen
></iframe>
</div>
<br />
### Tags
To group similar secrets, hover over a secret, select the three dot menu, then select **Annotate** and **Add Tags**.

### Comments
To leave context for your team, hover over a secret and select the comment icon.

### Personal overrides
Infisical employs the concept of **shared** and **personal** secrets to address the need
for common and custom secret values, or branching, amongst members of a team during software development.
To provide a helpful analogy: a shared value is to a `main` branch as a personal value is to a custom branch.
Consider:
- A team with users A, B, and C.
- A project with an environment containing a shared secret called D with the value E.
Suppose user A overrides the value of secret D with the value F.
Then:
- If user A fetches secret D, they get the value F.
- If users B and C fetch secret D, they both get the value E.
To set a personal value, hover over the secret, select the three dot menu, then select **Add Override**.
<Info>
Secret reminders don't work with personal overrides.
</Info>