# Automatic Configurations

Secrets are encrypted variables created for protecting your confidential data. After finishing the settings of your secret, you can use it with the format `{{ secret. keyname }}` in workflows. The value of secrets will not be displayed explicitly in YAML files or any code so that your data security will be guaranteed when using automatic workflows in Action.

### Access your secrets <a href="#accessing-your-secrets" id="accessing-your-secrets"></a>

* Entering the Dataset Overview page, click **Actions** to the Action Details page, and then click **Configure** to create or manage your secret.

![](/files/jfn2xWOpiPzXjoO90g66)

* You can also click **Settings** on the Datasets Overview page, then click **Action Configuration** to manage your secrets.

![](/files/ECdriitJ0FHvIKIyjWxD)

### Create Your Secrets

* Click **Create Secret**
* Type a name and enter the value for your secret in the input boxes.

![](/files/F6aAXL6TZUuxsHAlpRJa)

* Then click **Create** to finish the setting.

![](/files/jT8FbfZJNjxy023RwzUB)

### Name Your Secrets <a href="#naming-your-secrets" id="naming-your-secrets"></a>

* Secret names can only contain alphanumeric characters (\[a-z], \[A-Z], \[0-9]) or underscores (\_). Spaces and other special characters are not allowed.
* Secret names must not start with a number.
* Secret names are case-sensitive.
* Secret names must be unique at the level they are created at. (For example, a secret created for a dataset must have a unique name in this dataset.)
* Secret names can contain a maximum of 40 characters and a minimum 2 characters.
* No limits for the value of a secret.

### Permissions

* Only administrators of a dataset can create, delete, and update secrets for that dataset.
* Members of a dataset can only copy secrets used in that dataset.
* The value of a secret is only displayed during the creation step, after that all users cannot see the explicit value.

### Manage Secrets

* All the secrets will be displayed in the secret management list, including their names, updating time and all the history operations. You can update or delete secrets in this list.

![](/files/DgOAFONeY1K1JY2lrD1d)

### Update Secrets

* Select the secret that should be updated from the secret management list, and then click **Update** in the operation bar. Enter a new secret value in the pop-up window. Click **Update** to complete the procedure. The updated secret value will be automatically referenced when you use it the next time.

![](/files/yKgSBztk3Zw0jhbJYsEv)

### Delete Secrets

* Select the secret that you want to delete from the secret management list and click **Delete** in the operation bar.&#x20;
* Click **Delete** again in the pop-up window to confirm your operation.

![](/files/e1HZcp3rEooECUg0Rbg1)

{% hint style="info" %}
Deleting a secret may cause workflows using the secret to not work properly, so please be cautious.&#x20;
{% endhint %}

### Use Secrets

* To use a secret, you need to go to the secret management list to copy its name.

![](/files/DM6YY6hjRxwySTLzuVoY)

* Once the name is copied, you can use it with the format`{{ secret. keyname }}` in the YAML file of a selected workflow.

![](/files/xtz1XDL5KQSWpverX3ux)

&#x20;


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.graviti.com/guide/tensorbay/action/automatic-configurations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
