Docs

Sign up and connect FlyDocs to Linear or Jira

Create your FlyDocs account, connect your PM tool, and link your first project. Five minutes from signup to your first connected workspace.

Get your account set up and connected to your PM tool. Five minutes from signup to your first connected project.

Step 1: Create your account

Sign up at app.flydocs.ai using GitHub OAuth. You'll be prompted to create an organization, the top-level container for your team's workspaces, members, and billing.

One account, one org. If you're joining an existing team, ask your admin for an invite link instead.

Step 2: Connect your PM tool

From the portal dashboard, navigate to your organization settings and connect your project management tool. FlyDocs supports:

  • Linear via personal API key (Linear → Settings → API)
  • Jira via OAuth

Linear uses a personal API key you generate in Linear's settings. Jira uses OAuth, which authorizes FlyDocs to read and write issues, transitions, comments, and labels on your behalf. One connection per organization; all workspaces under that org share the same provider connection.

Provider credentials are encrypted at rest using AES-256-GCM and decrypted only per-request when the relay API communicates with your PM tool. FlyDocs never stores plaintext provider tokens.

Step 3: Set up a workspace

Create a workspace in the portal. A workspace is the scoped container that maps your PM provider team to your repos, members, and configuration.

During workspace setup, you'll:

  • Select your provider team. The Linear team or Jira project this workspace maps to.
  • Configure status mapping. Map FlyDocs canonical statuses (Ready, Implementing, In Review, Done) to your provider's workflow states.
  • Set up labels. Map FlyDocs issue type labels (feature, bug, chore, idea) to your provider's labels, auto-created if they don't exist.

This configuration is set once and applies to every repo and team member in the workspace. See Workspaces & Topology for the full conceptual model.

Step 4: Generate an API key

Go to Account > API Keys in the portal. Click Create New Key, give it a name, and click Generate.

Copy the key immediately. It's shown once and can't be retrieved later. Keys use the fdk_ prefix:

api key 
fdk_a1b2c3d4e5f6g7h8i9j0...

This key authenticates your CLI against the relay API. It doesn't carry configuration; config lives on the workspace. One key works across all your workspaces. See API Keys for the full security model.

Step 5: Link your project

In your project directory, run flydocs init:

terminal 
cd your-project
flydocs init

The init command will:

  1. Prompt for your API key. Paste the fdk_ key from step 4.
  2. Authenticate against the relay and list your available workspaces.
  3. Prompt you to select a workspace.
  4. Create .flydocs/config.json with your workspace ID.
  5. Pull server-managed skills, hooks, and commands into your project.
  6. Detect your stack and generate project context.

Your API key is stored globally at ~/.flydocs/credentials, not in the project directory. The workspace ID is committed to the repo so every team member resolves the same configuration.

Verify the connection

Run flydocs sync to confirm everything is connected:

terminal 
flydocs sync

Your terminal shows the workspace name, provider status, and the number of skills and hooks pulled from the server. If you see the workspace name and a green provider status, you're connected.

What's connected now

Your AI coding tool has the full workflow. Here's what that means:

  • Issue operations flow to your PM tool. Creating, transitioning, commenting, and closing issues writes directly to Linear or Jira through the relay API.
  • Session memory carries forward. The SessionStart hook injects your previous session summary so the agent picks up where you left off.
  • Server-managed skills keep everyone aligned. Every team member gets the same skills, hooks, and enforcement. No manual distribution, no version drift.
  • Config changes take effect immediately. Update a status mapping or label in the portal, and every CLI session resolves the new config on the next request. No re-initialization required.

Prefer to stay offline?

FlyDocs works without a cloud account. Use flydocs init --tier local for file-based issues, full enforcement, and no network requirements. You can connect a cloud account later without losing local work. See Local Mode for details.

Next

Install the CLI: set up the FlyDocs CLI and initialize your project.