Flik
Web
The Flik web app is where you sign in, create and manage API keys, and manage organizations and membership. There is no issue-tracker UI in the browser; backlogs are managed via the CLI or MCP.
Organizations are central to Flik: they define who works together and where projects live. You create an organization (e.g. for your team or product), then add members and invite others by email. Projects you create via the CLI or MCP belong to an org; API keys are scoped to an org. The web app lets you create orgs, view members, send invites, and (from the Dashboard) switch between orgs when managing keys.
What the web app provides
| Area | Purpose |
|---|---|
| Dashboard | Entry point after sign-in; links to Keys and Organizations. |
| Keys | Create, list, rotate, and delete API keys. Keys are used by the CLI and MCP (and any custom client). |
| Organizations | Create organizations, view members, and send invites. Projects belong to an org. |
Authentication is handled by Clerk (sign-up, sign-in, session). The web server stores API keys and org data in MongoDB.
Key concepts
- API key — A long-lived secret (e.g.
flik_...) used as a Bearer token. One key per “identity” (human or agentic); create multiple keys for different tools or environments. - Organization — Tenant boundary. Projects are created under an org. Users get access via org membership or invites.
- Project — Created via CLI or MCP (not in the web UI). Projects are scoped to an org when using org context.
Next steps
- API keys — Creating keys, rotating, and best practices.
- Organizations — Creating orgs, members, and invites.