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

# Share a project

> Share a Newly v2 project with other people, choose their access level, and transfer ownership.

You can share a project in Newly v2, at app.newly.app and in Newly for Mac, with specific people. Sharing works one project at a time. Each person gets an access level that decides what they can do.

## Share a project

The project's owner and anyone with **Admin** access can share it.

<Steps>
  <Step title="Open the project">
    Open the project you want to share.
  </Step>

  <Step title="Open sharing">
    Select the share icon at the top of the sidebar. In the Mac app you can also go to **Settings** → **People**, which appears when a project is open.
  </Step>

  <Step title="Add the person">
    Enter the person's email address and choose an access level.
  </Step>

  <Step title="Confirm">
    Select **Share**. Newly checks the address and asks you to confirm who it belongs to. Select **Yes, share**.
  </Step>
</Steps>

The person must already have a Newly v2 account. If they don't, you see "No Newly account for" followed by the email address. Ask them to [sign up](/get-started/sign-in) first, then share again.

<Note>
  In the Mac app, the share icon appears only for projects saved to Newly's cloud. People with **Can view** access don't see the share icon. People with **Can edit** access can see who has access but can't change it.
</Note>

## Access levels

| Level        | What they can do                     |
| ------------ | ------------------------------------ |
| **Admin**    | "Can prompt, edit and manage people" |
| **Can edit** | "Can prompt and edit"                |
| **Can view** | "Can read the chat and the files"    |

Some things need **Admin** access or the owner:

* **Stopping, finishing, archiving or deleting a chat.** A **Can edit** member who tries sees "Only an admin of this project can stop, finish, archive or delete a session."
* **Adding people, changing access and removing people.**

**Can view** is read-only. If a viewer tries to change anything, including sending a message, they see "This project is shared with you for viewing. Ask an admin of the project for edit access."

To change someone's level, select their current level next to their email address and pick a new one. To remove them, pick **Remove from project**. The owner can't be removed.

If you have **Can edit** or **Can view** access and no longer want the project, ask an admin of the project to remove you.

## Who pays for a shared project

Every agent turn in a shared project uses credits from the **project owner's organization**, no matter who sent the message. People you share with don't spend their own credits on your project, and there's no per-person billing.

If you give people **Can edit** or **Admin** access, keep an eye on your balance. See [How credits work](/billing/how-credits-work).

## Transfer ownership

Only the owner can transfer a project, and only in the Mac app. The new owner must be someone the project is already shared with.

<Steps>
  <Step title="Open People settings">
    With the project open, go to **Settings** → **People**.
  </Step>

  <Step title="Pick the new owner">
    Under **Transfer ownership**, select the person's email address.
  </Step>

  <Step title="Confirm">
    Read the confirmation and select **Transfer ownership**.
  </Step>
</Steps>

After the transfer:

* The project moves to the new owner's account. In your project list it shows as shared with you.
* The new owner's organization pays for every turn from then on. Usage from before the transfer stays where it was billed.
* You stay on the project as an **Admin**, so you can still open it and work in it.
* Only the new owner can hand it back.

## Newly staff access

Newly staff can open your project to help you with a support request. They aren't listed in the project's people.

## Related pages

<CardGroup cols={2}>
  <Card title="Where your code lives" icon="code-branch" href="/code/where-your-code-lives">
    How several chats share the same code.
  </Card>

  <Card title="How credits work" icon="coins" href="/billing/how-credits-work">
    What uses credits and whose balance pays.
  </Card>

  <Card title="Delete a chat, project or account" icon="trash" href="/account/delete">
    What admins can delete and restore.
  </Card>

  <Card title="Projects, chats, Remote and Local" icon="folder-tree" href="/get-started/projects-and-chats">
    How your work is organized.
  </Card>
</CardGroup>