For stores not using WebOps, secrets is handled through the VTEX IO CLI secrets plugin. To enable secrets management, an empty vtex.env file need to be present in the project root. The key-value pairs is stored in the secrets.revealed.json file, then encrypted into secrets.hidden.json before being committed to the main branch. For stores using WebOps, this workflow has been deprecated, and secrets are managed directly through the WebOps interface.

1. In the Key field, enter the name of the secret, which serves as its unique identifier (example: VTEX_API_TOKEN, NEXT_SECRET_KEY). In the Value field, enter the corresponding sensitive information you want to store (example: the actual token, key, or password).

   Secrets accessible in the browser (client-side) must start with the prefix NEXT_PUBLIC_. For all other secrets, use other names without this prefix.

2. Click Add. A pop-up with New Secret added successfully will open. Then, you'll see the message Secrets have changed. Changes will take effect in the next successful deployment. alongside a Redeploy button.

   When creating multiple secrets, make sure you include all of them before proceeding to the next step. This prevents synchronization errors.

3. Click Redeploy to redeploy your website with the updated secret configuration. You’ll see the message Redeploying with secret changes, then a pop-up with Deployment created successfully will open.
4. Follow the deployment status in the Deploys tab of the WebOps dashboard.
   During the build process, any secrets registered through WebOps will be transformed into environment variables within the code, automatically loading them into the process.env object. You can access these values in your code using process.env.VARIABLE_NAME. Remember to replace VARIABLE_NAME with the name you assigned to your secret in the Key field.
   The secret created will be available in the Current Keys section.

1. Go to the Current Keys section.
2. Alongside the secret you need to update, click ⋮, then click Edit.
3. Click Update. A pop-up with Secret updated successfully will open. Then, you'll see the message Secrets have changed. Changes will take effect in the next successful deployment. alongside a Redeploy button.
4. Click Redeploy to redeploy your website with the updated secret configuration. You’ll see the message Redeploying with secret changes, then a pop-up with Deployment created successfully will open.
5. Follow the deployment status in the Deploys tab of the WebOps dashboard.

1. Go to the Current Keys section.
2. Alongside the secret you need to update, click ⋮, then click Delete.
3. Validate the secret you want to remove.

   This action can’t be undone.

4. Click Delete secret. A pop-up with Secret deleted successfully will open. Then, you'll see the message Secrets have changed. Changes will take effect in the next successful deployment. alongside a Redeploy button.
5. Click Redeploy to redeploy your website with the updated secret configuration. You’ll see the message Redeploying with secret changes, then a pop-up with Deployment created successfully will open.
6. Follow the deployment status in the Deploys tab of the WebOps dashboard.

If you tried to create, update, or delete a secret and received the error Failed to create/update/delete secret. Please, try again., repeat the process. If the problem persists, open a ticket to VTEX support.