> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kiwiflow.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Organizations and accounts

> Manage account access, project roles, organization billing, and referral attribution in hosted Kiwi.

An organization is the team and billing boundary. Each organization can contain multiple Kiwi projects, each with its own membership and roles.

## First use

Sign in at [Kiwi](https://www.kiwiflow.io/sign-up). On first use, Kiwi creates an organization from your profile name or email and initializes a project named **My first project**. If you already belong to an organization, use the membership and project access already granted to you. An organization member does not automatically receive access to every project.

## Membership and roles

Use **Members** in Kiwi to manage organization invitations and membership. Accepting an invitation makes the person an organization member; it does not grant access to every project.

In a project's **Members** area, a project Admin can assign current organization members one of these project roles:

| Role | Scope |
| - | - |
| Admin | Manage the project, workflow configuration, members, and project credentials. |
| Contributor | Perform eligible workflow steps. |
| Reviewer | Perform eligible review and verification actions. |

Project access and organization authority are separate. An organization Admin does not automatically gain access to a private project. A project Admin does not become an organization Admin or gain billing authority.

## Billing

Use **Billing** to view the organization's plan, status, and billing actions shown to you. An organization Admin manages billing access and makes changes through the available controls.

## Remote access and checker keys

Use **MCP & access** to see the hosted MCP connection details and manage project-bound MCP credentials. OAuth is the normal path for an existing agent environment. A project Admin can also issue an expiring read-only or workflow-write MCP key for one project. The secret is shown once; the key inventory contains nonsecret metadata only.

Checker keys are separate credentials for named CI check reports. A project Admin creates them in **Connections**, restricts their check IDs and expiry, then stores the one-time secret in the customer's CI secret manager. See [Remote MCP](https://docs.kiwiflow.io/remote-mcp.md), [Connections](https://docs.kiwiflow.io/connections.md), and [CI reporting](https://docs.kiwiflow.io/ci-reporting.md) for their permissions.

## Referrals

An organization Admin can create a stable referral link and view aggregate attribution counts. A valid code is recorded during the first eligible Kiwi organization Admin onboarding, before the organization has already been initialized or used to create projects. The first valid referral cookie lasts thirty days; opening another link does not replace a still-valid referral.

Existing organizations are not attributed later. A same-organization referral and a claimant using a code they created are ineligible. Counts report onboarding attribution only; Kiwi does not calculate payment or rewards from them, and the aggregate view does not expose another customer's identity.

For project membership and run permissions, see [Concepts](https://docs.kiwiflow.io/concepts.md). For a customer-facing overview of connecting an agent, see [Set up your agent](https://docs.kiwiflow.io/ai-quickstart.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.