Where a conversation lives

Your own chats, projects, an organization's chats and Slack differ in who sees them, whose sign-ins and plan June uses, and what it remembers.

Where a conversation lives decides who can read it, whose sign-ins and plan June uses, and what it remembers. Here is each place side by side.

Who sees it, whose sign-ins, whose plan

A funding source set for the space pays for every turn there; without one:

Place	Who sees it	Whose sign-ins	Whose plan
Your own chat	You (unless you share a link)	Yours	Yours
Your project	You (unless you share a link)	Yours	Yours
An organization's chat	Every member	Whoever tagged or asked June	Theirs
An organization's project	Every member	Whoever tagged or asked June	Theirs
A Slack direct message	You	Yours	Your ChatGPT plan
A Slack channel thread	The channel	Whoever tagged June	Their ChatGPT plan

Yours and Theirs mean that person's own plan for its models, or June for June Models (Models and who pays). In Slack, without a funding source, only a ChatGPT plan answers: June Models and a Claude plan do not.
The space is your own or an organization's. A Slack workspace belongs to you or to an organization too.
A public channel in an organization's Slack workspace is also readable by the organization's members on the web.
Whose sign-in June uses has the rules behind the sign-ins column, steering included.

What June remembers

Place	Memory June reads	Memory June saves to
Your own chat	Yours	Yours
Your project	Yours and the project's	The project's
An organization's chat	The organization's	The organization's
An organization's project	The organization's and the project's	The project's
A Slack direct message	Yours	Yours
A Slack channel thread	The channel's	The channel's

Which memory each place reads and writes adds each place's Soul and when June saves on its own.

June's sandbox follows the same lines: your own chats share yours, each project has its own, an organization's chats share the organization's, and Slack has none.

Threads June starts stay in their place

When June starts a separate thread for part of the work, the new thread is born where its parent lives: in the same project, the same organization, with the same people able to read it. It runs as the person whose message started it, with their own model, and their plan unless the organization pays.

June starts threads only on the web and in the app, not in Slack, and within these limits:

at most 5 from one reply
at most 3 levels deep
at most 10 running at once for one person in one space (your own or an organization's), and 30 in one organization

A thread June starts does not start another in its own first reply.

A project stays where you created it

You choose a project's place when you create it: your own, or an organization's. It cannot move later. To take work into an organization, create a project there and add its instructions and files again; the old project's chats and memory stay where they were.

What June does not do

In shared places it does not answer unless tagged: @june in an organization's chats, a mention in a Slack channel. In your own chats and in a Slack direct message it answers every message.
It does not share memory between an organization's web chats and its Slack channels. What June learns in a channel stays with that channel, and in a channel it saves no personal facts.
It does not show an organization's chats to anyone outside it, or your own chats to an organization.
In an organization's chats and projects, it does not use the tools that act as you in the sandbox, and a schedule cannot be set up from its web chats.
In Slack, it does not run commands or files in a sandbox, or start a separate thread.
It does not run a step that needs your confirmation, in any place.