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

# Invite collaborators

> Invite someone to one site or add them to your organization with the right role.

Choose the narrowest access that lets someone do their work. A site invite grants access to one site. An organization invite adds the person to your organization, but site access is still set separately.

## Invite someone to a site

```bash theme={null}
fimo invite
fimo invite --email "jane@acme.com" --role edit
fimo invite --project <project-id> --email "jane@acme.com" --role view
```

| Site role | What it allows |
| - | - |
| `view` | Read-only access to the site |
| `edit` | Edit code, content, and assets, and use AI chat |
| `full` | Manage site settings, sharing, and publishing |

Use `view` for someone who reviews work without editing it. Use `full` only for people who need to manage access or publish.

## Invite someone to an organization

```bash theme={null}
fimo invite --target organization --email "alice@acme.com" --role member
fimo invite --target organization --email "alice@acme.com" --role admin
fimo invite --target organization --email "alice@acme.com" --resend
```

Organization roles are:

* `member`: can create sites and view organization members
* `admin`: can manage organization members, settings, and sites
* `owner`: has full control of the organization

> [!WARNING]
>
> An organization role does not define a person's access inside every site. Set site access separately in each site's
> sharing settings.

`--resend` works for organization invitations only. The CLI asks you to review and confirm every invitation unless you pass `--yes`.

## Review, merge, and publish access

* Give reviewers `view` access when they only need to inspect work.
* Give contributors `edit` access when they need to make changes.
* Give site leads `full` access when they need to manage sharing, settings, or publish.
* Contributors with `edit` access can merge approved Branches.

Organization membership alone does not grant merge or publish access.

## What's next

> [card] [Collaboration overview](/docs/collaboration/overview.md)
>
> Choose the right path for access, review, merge, and publish.

> [card] [Organizations](/docs/collaboration/organizations.md)
>
> List members and switch the CLI's active organization.

> [card] [Sharing in Studio](/docs/studio/collaboration.md)
>
> Invite people and change site access in the dashboard.


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