# Connections and checks

> Give a workspace its own Anthropic or ElevenLabs key, and use the Checks tab to confirm the workspace is ready to make videos.

Source: https://demovexa.com/docs/workspaces/connections-and-checks

The **Connections** tab lets one workspace use its own Anthropic or ElevenLabs key instead of the studio's. The **Checks** tab shows whether the workspace has what it needs to make videos.

Both are in **Workspace settings**. To open it, click the workspace switcher in the sidebar and choose **Workspace settings**.

## Connections

By default, every workspace uses the keys you set in **Settings**. Give a workspace its own key when its usage should be billed to a different account, such as a client's.

The tab has two rows: **Anthropic (Claude)** and **ElevenLabs**. Each row says "Uses the studio's key …" until you change it.

### Use a workspace's own key

1. Open the **Connections** tab.
2. In the **Anthropic (Claude)** or **ElevenLabs** row, click **Use its own key**.
3. Paste the key.
4. Click **Test for this workspace** to check it works.
5. Click **Save changes**.

### Go back to the studio's key

1. In the row, click **Use the studio's key**.
2. Click **Save changes**.

### How keys are chosen

When the workspace has its own key, DemoVexa uses it. Otherwise it uses the studio's key from **Settings**.

> [!IMPORTANT]
> A workspace with its own Anthropic key always uses the API, even if the studio runs Claude through your Claude login. Every call is billed to that key at API prices.

Workspace keys are stored like the studio's keys: in your computer's password store (macOS Keychain, Windows Credential Manager or the Linux keyring), never shown in full again, and only sent to Anthropic and ElevenLabs.

## Checks

The **Checks** tab tests the workspace and shows the result of each check, with how to fix anything that fails. Click **Check again** after you fix something.

| Check | What it looks at |
|---|---|
| Code folder | The app code folder set on the **App & docs** tab |
| Git | The code folder's git repository, which the Ideas page reads |
| Docs / how-to guides | Your docs and how-to guides |
| Modules | The workspace's modules |
| App packages | The app's packages. Only shown when videos use the app's own UI components. |

### Fixing common problems

- **Code folder:** set the folder on the **App & docs** tab. Use the full path, or click **Choose folder…**. See [App and docs](/docs/workspaces/app-and-docs).
- **Git:** install Git if it's missing. See [Install](/docs/getting-started/install).
- **Docs / how-to guides:** set the **Docs folder** on the **App & docs** tab, or leave it empty so DemoVexa looks for it.
- **Modules:** click **Detect with Claude** on the **Modules** tab. See [Modules](/docs/workspaces/modules).
- **App packages:** run `npm install` in your app's folder.

> [!NOTE]
> These checks cover one workspace. Checks for the whole studio, such as Claude, ElevenLabs, the database and rendering, are in **Settings**. See [Settings](/docs/settings/settings).

## Related

- [Workspaces](/docs/workspaces/overview)
- [Settings](/docs/settings/settings)
- [Troubleshooting](/docs/help/troubleshooting)