> ## Documentation Index > Fetch the complete documentation index at: https://docs.threetone.in/llms.txt > Use this file to discover all available pages before exploring further. # Environment variables > Manage workspace values and credential references, understand production fallback, and verify environment-specific configuration. Workspace environment variables hold a value or resource reference for each named environment. Use them to keep integration configuration together. They do not create infrastructure or replace workspace permissions. Recording pending for Configure environment values. No playable video is available yet. ## Value types | Type | Stored value | Use it for | | - | - | - | | String | A nonempty string. | Configuration such as a service URL. | | Secret | A `{secret_id}` reference. | A secret stored through the supported workspace credential workflow. | | Auth Connection | An `{auth_connection_id}` reference. | A workspace authentication connection. | Secret and connection references must belong to the same workspace. Do not put a raw credential into a String value, a prompt, or a recorded example. ## Create a variable You need permission to manage environment variables in the active workspace. Go to [Developers > Environment variables](https://threetone.in/app/developers/environment-variables), then select **Add variable**. In **New variable**, set **Name** and **Type**. Names use 1 to 64 letters, numbers, or underscores. Choose the value type before creating the variable. Enter the required **production** value or select the corresponding workspace reference. The variable must have a production value even when you also use another environment. Select **Save**, then reopen the variable and confirm its type, label, and production value or reference. Screenshot pending for workspace environment variable values. This illustration shows no actual secret or connection details. ## Add an environment value Use **Create environment** and **New environment** to add values to existing variables. An environment name starts with a lowercase letter and contains lowercase letters, digits, underscores, or hyphens, up to 64 characters. An environment is a set of value keys. It does not provision a deployment, database, server, or separate workspace. When a variable lacks a value for the requested environment, the resolver falls back to its production value. Confirm that this fallback is appropriate before testing an integration. Creating an environment updates variables separately. If part of the operation fails, refresh the page and inspect which values were saved before retrying. ## Update or remove an override Open the variable or environment detail and use **Edit value** to update it. Use **Remove value** to remove a nonproduction override. Production cannot be removed. Removing an override restores production fallback for that variable and environment. The current public contract provides create, list, get, and update operations. It does not provide a variable deletion, rename, or type-change endpoint. ## API operations | Task | Reference | | - | - | | Create a variable | [Create environment variable](/api-reference/agents-platform/create-environment-variable) | | List values | [List environment variables](/api-reference/agents-platform/list-environment-variables) | | Inspect one variable | [Get environment variable](/api-reference/agents-platform/get-environment-variable) | | Change supplied environment keys | [Update environment variable](/api-reference/agents-platform/update-environment-variable) | An update merges the supplied environment keys. A `null` value removes a nonproduction key. The list endpoint supports cursor pagination and filters; an environment filter returns explicitly stored matches, not the resolved production fallbacks. ## Frequently asked questions Every variable must have a production entry because it is the fallback. Use safe test values and review what the integration will actually resolve before making a request. No. It only adds configuration values. Create and secure infrastructure separately when your application requires it. Use the Secret reference type and supported credential storage for secrets. Do not store raw credentials as ordinary text. Refresh and inspect each variable. Retry only the missing or incorrect values so you do not assume every update succeeded. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.