Skip to main content
The short video below walks through secret referencing and importing, covering how to reuse a “base” secret’s value across others and how to pull secrets from another environment or folder into the current context.

​
Secret referencing

Infisical’s secret referencing functionality makes it possible to reference the value of a “base” secret when defining the value of another secret. This means that updating the value of a base secret propagates directly to other secrets whose values depend on the base secret. Secrets dashboard with values revealed, showing references highlighted inside them Since secret referencing reconstructs values on the client side, any client (user, service token, or machine identity) fetching secrets must have proper permissions to access all base and dependent secrets. Without sufficient permissions, secret references won’t resolve to their appropriate values. For example, if secret A references values from secrets B and C located in different scopes, the client must have read access to all three scopes containing secrets A, B, and C. If permission to any referenced secret is missing, the reference will remain unresolved, potentially causing application errors or unexpected behavior. This is an important security consideration when planning your secret access strategy, especially when working with cross-environment or cross-folder references.
Hold Cmd (Mac) or Ctrl (Windows/Linux) and select a reference to jump to the secret it points at.

​
Syntax

When defining a secret reference, interpolation syntax is used to define references to secrets in other environments and folders. Suppose you have some secret MY_SECRET at the root of some environment and want to reference part of its value from another base secret BASE_SECRET located elsewhere. Then consider the following scenarios:
  • If BASE_SECRET is in the same environment and folder as MY_SECRET, then you’d reference it using ${BASE_SECRET}.
  • If BASE_SECRET is at the root of another environment with the slug dev, then you’d reference it using ${dev.MY_SECRET}.
Here are a few more helpful examples for how to reference secrets in different contexts:

​
Secret imports

Infisical’s Secret Imports functionality makes it possible to import the secrets from another environment or folder into the current folder context. This can be useful if you have common secrets that need to be available across multiple environments/folders. To add a secret import, select the chevron next to Add Secret, then select Add Secret Import. Add Secret Import dialog Each import appears above the secrets on the dashboard, labeled with the environment and path it pulls from. In the example below, /backend and /third-party are both imported into the current folder. Secrets dashboard listing two imports above the secrets Hover over an import to reach its controls: select the trash icon on the right to delete it, or drag the handle on the left to reorder it. An import row hovered, showing the drag handle and the trash icon Order matters. If two imports carry a secret with the same name, the value from the bottom-most import wins.

​
Relative reference resolution in imported secrets

Only available on the V4 Secrets API (/api/v4/secrets). v3 and below always resolve local references against the source environment.
When you import secrets from one environment into another, the imported secrets may contain references like ${KEY} that point to other secrets. Relative resolution changes how those local references are looked up: Resolution order for ${KEY} inside an imported secret (e.g. staging imports from dev):
  1. Look in staging (current environment)
  2. If not found, look in dev (source environment)
  3. If still not found, expand to an empty string
This lets you override any imported key simply by defining it in the destination environment.

​
Example

Fetching staging’s imported DB_URL via v4 → postgres://stg-db.internal/myapp The ${DB_HOST} local reference resolves to staging’s value. Without relative resolution (v3), it would resolve to dev’s DB_HOST instead.

​
Behavior notes

  • The current-env-first rule applies at every depth of recursive expansion, not just the top level. If an imported secret references another secret that references another, each ${KEY} at every level checks the current environment first.
  • Import-chain lookup: when looking for a key in an environment, Infisical also searches that environment’s one-level-deep imports. If prod imports from /shared and /shared has KEY, a ${KEY} reference in a prod context will find it.
  • Permissions: read access is enforced at every step. If the calling identity lacks access to any secret in the chain, the request returns 403.
Only one level of imports is searched during reference expansion. If prod imports /shared, and /shared imports /base, secrets in /base aren’t visible.

​
Cross-project secret sharing

Cross-project secret sharing is a paid feature.If you’re using Infisical Cloud, then it’s available under the Pro Tier. If you’re self-hosting Infisical, then you should contact [email protected] to purchase an enterprise license to use it.
Cross-project secret sharing allows secrets to be referenced or imported across different projects within the same organization. This is useful when multiple projects share common infrastructure secrets (such as database hosts, API keys, or service URLs) without duplicating them.

​
Enabling cross-project secret sharing

Cross-project sharing is controlled by an organization-level toggle. An organization admin must enable it before any cross-project references or imports can be created:
  1. Go to the Secrets Management product page. The Secrets Management product page
  2. Select Product Settings. The Product Settings page
  3. Turn on Cross-project secret sharing. Product Settings with the cross-project secret sharing toggle on
When this toggle is disabled, all cross-project references resolve to empty strings and cross-project imports are ignored.

​
Project grants

A Project Grant is the authorization mechanism that controls which projects can access secrets from a given source project. Grants are created from the source project (the project that owns the secrets) and specify:
  • Source environment and folder path: the specific location in the source project being shared.
  • Target project: the project that is allowed to reference or import secrets from that location.
The key benefit of project grants is that users in the target project don’t need any permissions in the source project. As long as a grant exists from the source project to the target project for a given folder, users in the target project can create cross-project references and imports for that folder. To create a new grant:
  1. Go to Project Settings in the source project. Project settings for the source project
  2. Select the Policies tab. The Policies tab, showing the Cross-Project Secret Sharing section
  3. Under Cross-Project Secret Sharing, select Share Secrets. The Cross-Project Secret Sharing section with no linked projects yet
  4. Under Environments & folders, choose the environment to share from, then type a folder path and select Add. Under Share with projects, choose the project that should get access, then select Share. The Share Secrets panel with an environment, a folder, and a target project chosen

​
Cross-project references

You can reference secrets from a different project using the @project-slug prefix. This allows you to compose secret values across projects without duplicating them.
Cross-project references aren’t recursively expanded. If the referenced secret in the source project itself contains a cross-project reference to yet another project, that nested reference won’t be resolved. Only same-project references within the source secret are expanded.

​
Cross-project imports

You can also import secrets from a different project entirely. Cross-project imports work the same way as regular imports, but the source environment and folder belong to another project within the same organization. To create a cross-project import:
  1. Select the chevron next to Add Secret, then select Add Secret Import. The Add Secret menu, showing Add Secret Import
  2. Select Another Project. The Add Secret Import dialog with Another Project selected
  3. Choose the source Project, Environment, and Folder path, then select Create Import. The dialog filled in with a source project, environment, and folder
  4. The import appears at the top of the secrets dashboard, labeled with the project it pulls from. The secrets dashboard showing the new cross-project import
Cross-project imports aren’t transitive. If the source folder in the foreign project has its own cross-project imports (pointing to a third project, or back to the original project), those nested cross-project imports won’t be followed. Only imports that stay within the same source project are resolved recursively.