> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paradime.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Environment Variable Overrides

> Override environment variables per Bolt schedule. A schedule inherits workspace and environment values, and its own override wins for that specific job.

Environment variable overrides let a schedule use different values without changing your workspace configuration. A schedule resolves each variable through a cascade, so you set a value once at the broadest level and override it only where you need to.

## How a value is resolved

For each variable, Bolt takes the most specific value available, in this order:

1. **Schedule override** — the value you set on this specific schedule. If present, it always wins.
2. **Environment value** — the value set for the environment this schedule runs in (for example, production).
3. **Workspace default** — the base value configured in workspace settings.

In other words, a schedule inherits the workspace default, an environment-specific value can override that default, and a schedule-level override ultimately wins for that job. If you leave the schedule override empty, the schedule falls back to the environment value, and then to the workspace default.

<Warning>
  **Prerequisites**

  * **Admin access** is required to override environment variable values on a schedule.
  * The variable must first exist in [workspace settings](/products/settings/environment-variables/bolt-schedule-env-variables) before it can be overridden on a schedule.
  * Only **UI-based schedules** currently support overriding environment variable values.
</Warning>

## When to override

* **Environment-specific configuration** — different values for development, staging, and production schedules.
* **Schedule-specific parameters** — custom thresholds, limits, or settings for one schedule.
* **Testing and debugging** — temporary value changes without touching the workspace default.
* **Multi-tenant deployments** — client-specific configuration within the same workspace.

## Set an override

1. In the **Bolt UI**, open the schedule you want to edit.
2. Go to the **Environment variable overrides** section.
3. In the **Override** column, enter a new value for the variable. Leave it empty to keep the inherited value (the environment value, or the [workspace default](/products/settings/environment-variables/bolt-schedule-env-variables)).
4. Click **Deploy** to save.

Overrides only affect the schedule where they are set. The workspace default and other schedules are unchanged.

<Card title="Define this as code" icon="code" href="/products/bolt/creating-schedules/schedules-as-code/configuration-reference#environment-variable-overrides" horizontal>
  Set the `env_overrides` list of `key`/`value` pairs.
</Card>


## Related topics

- [Configuration Reference](/products/bolt/creating-schedules/schedules-as-code/configuration-reference.md)
- [Bolt Environment Variables](/products/settings/environment-variables/bolt-schedule-env-variables.md)
- [Environment Variables in Commands](/products/bolt/creating-schedules/environment-variables-in-commands.md)
- [bolt.run.completed](/developers/webhooks/bolt-run-completed.md)
- [bolt.run.started](/developers/webhooks/bolt-run-started.md)