> For the complete documentation index, see [llms.txt](https://docs.paradime.io/app-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.paradime.io/app-help/products/settings/environment-variables/copy-workspace-variables-across-workspaces.md).

# Copy Workspace Variables Across Workspaces

If you manage more than one Paradime workspace, the **Copy** button on the Workspace tab replicates your current workspace's variable set into one or more other workspaces in a single operation — useful for promoting a configuration from staging to production, or keeping per-region workspaces in sync.

{% hint style="warning" %}
This action only applies to the **Workspace** tab. Bolt Schedules, Code IDE per-user, and Agent variables are **not** copied.
{% endhint %}

#### Steps

1. From any page in the Paradime application, click **Settings**.
2. Navigate to **Workspaces → Environment Variables**.
3. Open the **Workspace** tab.
4. Click **Copy**.
5. Select one or more target workspaces from the list.
6. Confirm.

<div data-with-frame="true"><figure><img src="/files/C2mGbKqZ12d7guae3LDq" alt=""><figcaption></figcaption></figure></div>

#### How the copy behaves

* **Eligibility:** Only workspaces where you have **admin write access** to workspace variables appear as eligible targets. The current workspace is always excluded from the list.
* **Atomic replace:** Each target workspace's variable set is **fully replaced** with the source's — variables present in the target but not in the source are removed. There is no merge or diff.
* **Auto-redeploy:** Bolt schedules in each target workspace are automatically redeployed so running schedules pick up the new values.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.paradime.io/app-help/products/settings/environment-variables/copy-workspace-variables-across-workspaces.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.