Skip to main content

​
Description

A profile is a single login: an account on the specified Infisical instance, and the organization you chose for it. Each profile keeps its own session, so you can work in several organizations at the same time. The organization is a setting on a profile, not part of its identity. To use another organization for a single command, pass --org. To change the default organization for a profile, run infisical profile set-org.

​
How a profile is selected

Every command selects a profile in this order:
  1. The --profile flag.
  2. The INFISICAL_PROFILE environment variable.
  3. A directory that you bound to a profile, with infisical profile bind or during infisical init.
  4. The default profile for the machine, set with infisical profile use.
The first one that applies wins. If an override hides a bound directory, the CLI reports which profile it used and why.
Your first login creates a profile for you. The name comes from your account and organization, for example [email protected].

​
Sub-commands

infisical profile list

List every profile on this machine, with its account, organization, instance, and session state.
The current profile is marked with an asterisk.
Show which profile a command run in the current terminal or directory will use, and why it was selected.

​
Flags

Print only the profile name. Use this in a shell prompt.
Create a profile for another organization without logging in again. The new profile reuses the account and instance that you’re signed in to.
If you omit --org, the CLI will ask you to pick an organization.

​
Flags

Also make the new profile the default for this machine.
Also pin this terminal to the new profile. Run the command through eval, because a command can’t change the environment of the shell that started it.
Make a profile the default for this machine. The default applies when no flag, no environment variable, and no bound directory selects a profile.
To choose a profile for one terminal, use infisical profile pin. To choose one for a directory, use infisical profile bind.
Pin the current terminal to a profile. Other terminals keep the profile that they already use.The command prints an export statement. Run it through eval to apply it to the shell that you’re in.
In PowerShell, run infisical profile pin globex | Invoke-Expression. In cmd.exe, or in a script, set INFISICAL_PROFILE=globex yourself.
Remove the pin from the current terminal. The terminal falls back to a bound directory, or to the default profile.
Bind a directory, and every directory under it, to a profile. Commands that run inside it select that profile with no flag and no environment variable.
If you omit the path, the CLI binds the current directory. If bindings overlap, the nearest one wins.infisical init also offers to bind a directory, if you have more than one profile.
The binding is stored in your own configuration, never in the repository, so it doesn’t affect anyone else who clones the project.
Remove the profile binding from a directory.
If you omit the path, the CLI removes the binding that covers the current directory.
Set the organization that a profile uses by default. The change persists for future commands.
To use another organization for a single command, pass --org. To keep a second organization available as its own profile, run infisical profile new.
Rename a profile. The stored session, the default-profile setting, and any directory bindings follow the new name.
Update any terminal that you pinned to the old name. The pin holds the old name, so those terminals no longer find the profile.
Delete a profile and remove its stored session. The CLI revokes the session on the server as well.

​
Flags

Remove the profile without revoking its session on the server.

​
Global flags

These flags work on every command, not only on infisical profile.
Use a specific profile for this command.
The profile flag can be substituted with the INFISICAL_PROFILE environment variable.

​
Examples