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

# Sharing & collaboration

> Invite people to a site and manage their access from Fimo Studio.

Use the sharing panel to decide who can open a site, leave feedback, edit it, or manage it.

## Invite someone

**1. Open sharing**

Open the site and click **Invite** in the header. On a phone, it is in the site menu.

**2. Choose an access level**

Enter one email address, then choose **Can view**, **Can edit**, or **Full access**.

**3. Send the invitation**

Click **Invite**. The invitation stays in the sharing panel while it is pending.

After someone accepts, the site appears in their **Sites** list with a **Shared** badge, whichever access level you gave them.

| Access level | Use it when someone needs to |
| - | - |
| **Can view** | Open the site without making changes |
| **Can edit** | Edit content and assets, and use AI chat to change code |
| **Full access** | Manage settings, sharing, and publishing |

## Change or remove access

Open **Invite** again. Use the menu beside a person or pending invitation to change the access level or remove it.

You need permission to manage the site before Studio shows these controls. If you cannot open the sharing settings, ask someone with **Full access** to update them.

## Set access for your organization

The **Everyone in your organization** row sets a site access level for organization members. Choose **No access** to avoid granting site access through organization membership.

Organization owners and admins always have **Full access** to every site in the organization. A site's sharing settings cannot lower it, so a site stays manageable after the person who created it leaves. If someone stops being an owner or admin, the access they were given on each site applies again.

> [!WARNING]
>
> For other members, organization membership and site access are separate. Adding someone to the organization as a
> member does not by itself prove that they can review, edit, merge, or publish every site. Members only see the sites
> they have access to in the **Sites** list.

## Review and publish work

Give reviewers **Can view** when they only need to inspect work. Give contributors **Can edit** when they
need to make changes. Merging Branches and publishing require **Full access**.

For the branch review and merge workflow, see [Branches](/docs/environments/overview.md). For the final go-live step, see [Deploy & publish](/docs/deploy/overview.md).

## What's next

> [card] [Collaboration overview](/docs/collaboration/overview.md)
>
> Follow the path from invite to publish.

> [card] [Invite via CLI](/docs/collaboration/invite.md)
>
> Send site or organization invitations from the command line.

> [card] [Version history](/docs/studio/version-history.md)
>
> Restore an earlier site version.


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