Docs

Dashboard

The FlyDocs web portal at app.flydocs.ai. Organization overview, workspace management, and onboarding for new teams.

The FlyDocs portal at app.flydocs.ai is the cloud dashboard for managing your organization, workspaces, team members, and provider connections. It complements the CLI — you configure your cloud environment here, then use flydocs connect in your project to link the two.

What you see when you log in

After signing in, the dashboard shows your organization overview: a list of workspaces, their linked projects, and team activity. If you belong to multiple organizations, you can switch between them from the header.

New users who haven't joined an organization yet will see a prompt to create one. The portal uses Clerk for authentication and organization management, so org creation follows their standard flow — name your org, set a slug, and you're in.

Sign-up flow

Pricing-page CTAs pass tier intent to the portal. The flow:

  1. Sign up via Clerk (GitHub OAuth). Tier intent persists through email verification.
  2. Create your organization — name and slug. The org is the top-level container for workspaces, members, and billing.
  3. Plan picker at /onboarding/plan — Solo or Team, pre-selected from URL param. Switch tiers, choose monthly or annual, set seat count for Team (default 3, minimum 3, maximum 20).
  4. Stripe Checkout — real card collection, real payment. PLASTR LTD appears on the statement.
  5. Workspace Get Started — five-card checklist (described below).

Workspace Get Started

After Stripe Checkout, you land in your workspace at /[workspaceSlug]/get-started. The page has five cards in order:

  1. Connect a Provider — Linear or Jira. Auto-checked if completed during onboarding; otherwise nudges you to settings.
  2. Add Repos & Generate Context — auto-checked from workspace state once you've connected a Git provider and run a scan.
  3. Create Your API Key — inline generation. Click the button, the fdk_ key appears with a copy button, you confirm "I've saved it."
  4. Install & Initialize — copy-paste CLI block. When step 3 just minted a key, the command embeds it: flydocs init --key fdk_xxxxx.
  5. Run /onboard — the /onboard slash command in your IDE (Claude Code, Cursor) generates project context and orients the agent.

Below the cards, an "I'm Set Up" button marks setup complete and redirects to the workspace overview.

Invited member

Users who accept a team invitation land directly on the workspace Get Started page. The flow is lighter — your admin has already configured the provider and Git connections, so the first two cards are usually pre-checked. You generate your API key, install the CLI, run /onboard, and start working.

Dark mode

The portal supports Light, Dark, and System themes via next-themes. Toggle from the header. Your preference persists across sessions.

Navigation

The portal organizes settings into three scopes:

  • Org settings — members, connections, billing, general org configuration
  • Workspace settings — workspace members, linked projects, provider mapping
  • Account settings — API keys, profile, personal preferences

The header provides quick access to org switching, notifications, and an admin-only invite button for adding team members from anywhere in the portal.

Next