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.
Secrets overview
The Secrets Overview page captures a bird’s-eye view of secrets and folders 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 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 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.
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.
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 amain 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.
- 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.
Secret reminders don’t work with personal overrides.