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

# jstm connection

> Connect services to a workspace, test them, and see how a credential resolves.

Connections attach a service credential to a workspace so agents can use it. Every command in this group requires `--workspace` — credential resolution depends on which workspace is asking.

## `connection providers`

List the connector providers available to you.

```bash theme={null}
jstm connection providers
jstm connection providers --search slack
```

| Option           | Description              |
| ---------------- | ------------------------ |
| `--search`, `-s` | Filter providers by name |
| `--json`         | Emit as JSON             |

## `connection list`

List the connections for a workspace.

```bash theme={null}
jstm connection list --workspace acme-corp/finance
jstm connection list -w acme-corp/finance --json
```

<ParamField path="--workspace, -w" required>
  Workspace handle, UUID, or FQN.
</ParamField>

## `connection add`

Add a service connection, by OAuth or API key.

```bash theme={null}
jstm connection add slack --workspace acme-corp/finance
jstm connection add anthropic --workspace acme-corp/finance --api-key sk-ant-…
```

| Option              | Description                                                       |
| ------------------- | ----------------------------------------------------------------- |
| `--workspace`, `-w` | Required. Workspace to connect for                                |
| `--vault`, `-V`     | Vault to store it in. Auto-detected from the workspace if omitted |
| `--api-key`         | The key, for API-key providers                                    |
| `--no-browser`      | Print the OAuth URL instead of opening a browser                  |

OAuth providers open a browser. API-key providers take `--api-key`, or prompt for it.

This command has no `--json`.

## `connection test`

Run a live health check against a provider connection.

```bash theme={null}
jstm connection test slack --workspace acme-corp/finance
```

This actually calls the provider, so it catches an expired or revoked token that a listing would still show as present. No `--json`.

## `connection resolve`

Show the tier-by-tier credential resolution walk for a provider.

```bash theme={null}
jstm connection resolve github --workspace acme-corp/finance
jstm connection resolve github -w acme-corp/finance --json
```

This answers "which credential will my agent actually get, and why". It walks personal, workspace, and org vaults in order and shows what matched at each tier.

Reach for it whenever an agent behaves as though it has the wrong account.

## `connection remove`

```bash theme={null}
jstm connection remove slack --workspace acme-corp/finance
jstm connection remove slack -w acme-corp/finance --id 4d90c7e2-… --force
```

| Option              | Description                                                             |
| ------------------- | ----------------------------------------------------------------------- |
| `--workspace`, `-w` | Required                                                                |
| `--id`              | Credential id. Required when several credentials exist for the provider |
| `--force`, `-f`     | Skip the confirmation                                                   |

If exactly one credential exists for the provider it is removed directly. If several do, the command asks you to disambiguate with `--id` rather than guessing.

No `--json`.

## See also

* [Connect a service](/guides/connect-a-service) — walkthrough.
* [Credentials and vaults](/features/credentials-and-vaults) — where credentials live.