When writing custom functions, you might need to reference sensitive information such as API keys or login credentials. Using secrets, organizations can centrally define and manage these sensitive values.
Members of selected workspaces can then reference secrets in custom functions used in automation projects and deployments.
Organization admins can create and manage secrets.
In the header, click the initials icon and select Settings.
Click Secrets.
Click Add secret.
Configure the secret.
Name — A name for the secret. Names can contain alphanumeric characters or underscores and can’t be changed after saving.
Value — The secret value itself. You can enter text up to 45,000 characters in length or upload a file, such as certificate files. After saving, the input is encrypted and can’t be viewed again.
Workspaces — Which workspaces the secret is available to. To make the secret available to only some workspaces, use the input field to select from a list of all shared workspaces.
Description — Optional notes or details about the secret and its usage.
Click Add secret.
After creating a secret, you can update its value, workspace availability, and description. You can’t view a secret’s current value.
In the header, click the initials icon and select Settings.
Click Secrets to view the secrets list.
In the secret’s row, click the edit icon
.
Edit the secret’s value or other settings, then click Save.
Deleting a secret deletes its value, affecting any custom functions that reference the secret. For your convenience, when deleting a secret, the confirmation modal lists any deployments in which the secret is referenced.
In the header, click the initials icon and select Settings.
Click Secrets to view the secrets list.
In the secret’s row, click the delete icon 
.
Click Delete to confirm.
