Organizations

An organization in Flik is a workspace for a team or product. It has a name (e.g. "Acme Product") and a short slug (e.g. acme-product) used in URLs and when using the CLI or MCP. All projects and API keys are scoped to an organization; users get access by being members of that org. The web app is where you create organizations, view members, and send invites.

Why organizations

  • Multi-team — Separate backlogs per team or product by creating one org per team.
  • Access control — Invite members with a role (e.g. user, administrator). Admins can manage members and invites.
  • Scoping — When using the CLI or MCP with org context (FLIK_ORG or org argument), project list and project create operate inside that org.

Creating an organization

  1. Sign in and go to Organizations.
  2. Create a new organization and give it a name (e.g. “Acme Product”).
  3. A slug is derived from the name (lowercase, hyphens). It is used in URLs and in FLIK_ORG.

You become the first member with administrator role.

Members and invites

  • Members — List current members (user, role). Shown on the org page.
  • Invites — Admins can invite by email with a role. If SMTP is configured, an invitation email is sent; otherwise the invite is created and the UI can show “Invite created; email not sent.”
  • Revoke invite — Admins can revoke a pending invite from the org UI.

Organizations cannot be deleted in the current design. Members can be removed; see the API docs for member management if exposed.

Using org context in CLI and MCP

  • Set FLIK_ORG to the org slug (or id) in your environment or .flik file.
  • Project create requires org context; if missing, the API returns an error and may suggest valid org slugs.
  • Project list with org context returns only projects in that org; without org, you see projects across all orgs you belong to (and legacy user-owned projects).