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

# Connect a provider

> Connect a workspace to GitHub, Slack, Zoho Desk, Jira, or Linear.

# Connect a provider

## What this does

A connector lets one workspace use a provider account. The provider sends credentials directly to `agentsfleet` after browser approval.

Use a secret instead when you must paste a static API key yourself.

## Before you begin

You need administrator access to the workspace and provider account. Supported providers are GitHub, Slack, Zoho Desk, Jira, and Linear.

## Steps

1. Open **Settings → Integrations** in the dashboard.

2. Choose a provider and click **Connect**.

3. Approve the requested access on the provider's website.

4. Return to the dashboard and approve the fleet's integration grant.

The workspace owns the connector. Each fleet needs a separate approved grant before it can use the connection.

## Verify it works

```bash theme={"theme":"vesper"}
agentsfleet connector list
```

```text theme={"theme":"vesper"}
<varies>
```

The provider state should be `connected`. A fleet without an approved grant cannot use the connector.

## Common problems

`not_connected` means the browser setup did not finish. Start the connection again from the dashboard.

`reconnect_required` means the provider rejected a saved credential. Reconnect the provider, then retry the fleet action.

When an expiring access token is rejected, the next connector call uses the saved refresh token. A revoked refresh token requires reconnection.

One GitHub App installation can belong to only one workspace. Another workspace receives `403` and keeps no new connection.

## Remove or undo

Revoke the application from the provider's account settings. The next connector call fails and the dashboard asks for reconnection.

Remove any fleet integration grants that should no longer use the provider. Revoking a connector does not delete fleet history.

## Related pages

* [Secrets](/fleets/secrets)
* [Webhooks](/fleets/webhooks)
* [Error registry](/api-reference/error-codes)