# How to share a conversation or project

Create a read-only public link anyone can open, or invite teammates as viewers or editors on a paid plan, and know where shared work shows up.

There are two ways to put your work in front of someone else: a public link anyone can open, or a proper invite with a role. Which one you want depends on whether they should be able to touch anything.

## The read-only public link

Every plan can do this. Create a read-only public link to a conversation and send it wherever: the person on the other end views it anonymously, no GPTree account needed.

It's view-only, which makes it the right tool for showing a result to a client or dropping a finished thread into a group chat without worrying that anyone will change it.

## Inviting people with roles

On a paid plan (Pro, Team, or a Pro trial) you can invite specific people to a project or to an individual conversation. Each invite carries a role:

- Viewers can read.
- Editors can send messages and branch.

Sharing a project shares its documents along with it, which is usually what you want: the reference files travel with the work.

For the person you invite, everything shows up under "Shared with me". And they work from their own account, on their own plan, spending their own credits. There's no shared billing, so inviting five teammates to a heavy project won't drain your allowance (and your credits don't cover their messages either).

A practical way to choose between the two: reach for the public link when the conversation is done and you're presenting it, and for an invite when the work is still moving. An editor can branch off your thread and try their own angle without asking you to paste anything around, and that's the whole point of sharing inside GPTree rather than screenshotting it.

## Earlier context when you're shared on a branch

When someone shares a branch with you, that branch only makes sense alongside the thread it came from. So above the branch you'll see a collapsed panel, "Earlier context from the shared thread", holding the messages that led up to it. Those messages are read-only context: you can read them to follow the story, but they aren't yours to open or edit as their own conversations, because the share was for the branch, not for everything upstream of it. If a thread that led to your branch is very long, the panel shows the most recent portion of it rather than every message.

Two things we don't support yet: real-time co-editing and ownership transfer. Collaborators contribute through their own messages and branches rather than live cursors, and whatever you share stays owned by you. Plan around that before you hand a client-facing project to a teammate expecting them to take it over.