Provider Connections
Connect Linear, Jira, and other project management tools to FlyDocs through the portal.
Provider connections let FlyDocs manage issues in your existing project management tool. You configure the connection once in the portal, and every team member's CLI uses it through the relay API. No individual provider keys scattered across machines. The portal is the source of truth for all provider configuration — each workspace resolves its provider, team, status mapping, and credentials from the server.
Supported providers
| Provider | Status | Auth Method |
|---|---|---|
| Linear | Fully functional | API key |
| Jira | Fully functional | OAuth |
| Trello | Coming soon | -- |
| Notion | Coming soon | -- |
| ClickUp | Coming soon | -- |
| Asana | Coming soon | -- |
Connecting Linear
- Navigate to Settings in the portal sidebar
- Select Connections
- Click Add Linear
- Enter your Linear API key (generate one from Linear Settings → API)
- Save — the portal validates the key and fetches your teams
Connecting Jira
- Navigate to Settings → Connections
- Click Add Jira
- Complete the OAuth authorization flow
- Select your Jira site and project
Jira uses OAuth rather than a static API key. The portal handles token refresh automatically.
One connection per provider
Each organization can have one connection per provider type. If your org connects to Linear, all workspaces in that org use that same Linear connection. Provider connections are org-scoped, not workspace-scoped.
Credential security
Provider tokens are encrypted with AES-256-GCM before storage. They are decrypted only per-request when the relay API needs to call the provider. FlyDocs never stores plaintext credentials.
Revoking a connection in the portal immediately deletes the encrypted token. There is no grace period or soft delete.
How the relay works
The FlyDocs relay API sits between your CLI and the provider. When a script
runs — say, issues.py create — the request hits the relay,
which translates it into the provider-specific API call.
- Linear — GraphQL API calls
- Jira — REST API calls
The relay currently handles 38 route files and 49 HTTP handlers. It
normalizes the differences between providers so the CLI scripts don't need
to know which provider is configured. A create issue call works
the same whether your org uses Linear or Jira.
Testing your connection
After connecting a provider in the portal, verify it works from your project:
flydocs sync flydocs sync validates your API key, checks the relay
connection, and confirms the provider is reachable. If anything is
misconfigured, it tells you what to fix.
Next
- API Keys — generate keys for CLI-to-cloud authentication
- Team Management — manage who has access to your org and workspaces
- Billing and Plans — understand what's included in each tier