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

# Collaboration

> Invite people, set project access, review changes, merge a Branch, and publish with clear ownership.

Collaboration in Fimo has two separate layers. Organizations group people and projects. Project roles decide what each person can do inside a specific project.

## Choose the right access

<CardGroup cols={2}>
  <Card title="Invite to one project" icon="diagram-project" href="/docs/collaboration/invite">
    Give a client, reviewer, or contributor access to one project.
  </Card>

  <Card title="Invite to an organization" icon="building" href="/docs/collaboration/organizations">
    Add a teammate to the organization, then set project access where they need it.
  </Card>
</CardGroup>

<Warning>
  Organization membership does not automatically grant every project permission. Check the project's sharing settings
  before someone reviews, edits, merges, or publishes.
</Warning>

## Move work from review to production

<Steps>
  <Step title="Invite the right people">
    Give reviewers `comment`, contributors `edit`, and project leads `full` access. [Compare project
    roles](/docs/collaboration/invite#invite-someone-to-a-project).
  </Step>

  <Step title="Review changes">
    Review the Branch preview and use `fimo status` or `fimo diff` to inspect changes. [Open the Branches
    guide](/docs/environments/overview).
  </Step>

  <Step title="Merge the Branch">
    Merge approved changes into the target Branch. Resolve conflicts when Fimo cannot combine a change automatically.
    [Follow the merge workflow](/docs/environments/overview#work-with-branches).
  </Step>

  <Step title="Publish from main">
    Publish after `main` contains the approved work. [Choose deploy or publish](/docs/deploy/overview).
  </Step>
</Steps>

Contributors with `edit` access can merge approved work. Publishing requires `full` project access. If Fimo blocks an action,
ask someone with **Full access** to perform it or update your role.

## Manage usage

AI credits, bandwidth, schedule compute, and agent-hours belong to the organization's usage. They do not replace project access controls.

<Card title="Understand billing and credits" icon="coins" href="/docs/collaboration/billing-and-credits">
  Learn what each metric measures and where to check current usage.
</Card>

## What's next

<Columns cols={3}>
  <Card title="Sharing in Studio" icon="table-cells" href="/docs/studio/collaboration">
    Invite people and manage project access visually.
  </Card>

  <Card title="Branches" icon="code-branch" href="/docs/environments/overview">
    Review and merge isolated Branches.
  </Card>

  <Card title="Deploy & publish" icon="cloud-arrow-up" href="/docs/deploy/overview">
    Preview work and publish it to production.
  </Card>
</Columns>