Sharing and invites
Choose the right audience: one thread, your workspace, or a read-only public page.
Every share is one of two actions: adding a person to your Workspace, or publishing a read-only copy of a Thread. Pick the one that matches the audience you mean.
| Action | What it does | Who it is for |
|---|---|---|
| Invite to workspace | Makes a person a member with a role, and every conversation there comes with it | Collaborators |
| Publish | Creates a clean read-only public copy of the Thread | Anyone with the link |
#Share within your workspace
Your workspace is the sharing boundary. Everyone in it shares its conversations. Invite people in a thread's menu takes you to the workspace members. Add someone there and the conversation comes with it. There is no per-thread invite link.
Before you add someone, read what they will see. A new member can read the whole history of the conversations they join.
Under Settings → Workspace → Members, the switch People here can steer Atoi in conversations they're added to decides whether members can direct Atoi. It is on by default. Atoi runs on the conversation owner's connection, and the receipt says so. A member never brings their own key.
#Invite someone to your workspace
Membership is for people you work with every day. Roles control administration. An email match is not membership. The person has to accept.
#Publish a page
Publish creates a clean public copy of the thread and shows you its link and visibility. Opening Publish creates the share, and there is no separate confirmation step. Read the thread before you open it. If the copy had to leave anything out, a receipt on the sheet says what changed. Visitors can read. They cannot join anything.
Use the sharing checklist below before you publish.
The Apple apps and Android show sharing screens, but publishing does not work there yet, and the CLI and MCP have no publish command. Workspace membership lives in the web app's settings. This guide stays Preview until publishing works the same way on every client.
#Revoke the right thing
- Remove a member under Settings → Workspace → Members to end that person's access. Their messages stay.
- Set a publication back to Private to take the public page down.
Both take effect without a separate confirmation, so choose the exact access you mean to end.
#The sharing checklist
Run this checklist whenever a thread crosses an access boundary.
#1. Arrive and sign in
Sign in and open the Thread from Ideas or search. Confirm that it is the exact Thread you intend to share, then read its complete history rather than only the last answer.
#2. Finish the decision and proof loop
Answer every Ask that changes the audience, scope, or source. If the work became a Task, wait for its terminal state and read Result, Changes, Checks, and Proof. A confident message does not replace the Task Receipt.
Remove keys, private files, personal data, internal screenshots, and any message that the audience should not receive.
#3. Choose the boundary
Choose one action before you create a link:
- Invite to the Workspace when a person should read and take part in its conversations.
- Publish when anyone with the link should read a frozen, view-only copy.
An invite does not create a public page. A public share does not make its viewer a member.
#4. Add someone to the Workspace
Open Invite people from the Thread menu and add the person as a Workspace member. See Share within your workspace for what they will see and how the steer switch works.
#5. Publish a read-only copy
Open Publish conversation from the Thread menu and select Public. The sheet shows the public link and whether Atoi published a clean copy with anything removed. Read the owner-visible redaction Receipt before you copy the link.
The public page is a snapshot. Visitors can read it, but they cannot join the Thread or steer Atoi from that page.
#6. Test the recipient's route
Open /share/<share> in a signed-out window. Confirm the title, owner, messages, outputs, and redactions. A link that works only in your signed-in browser does not prove the public route works.
#7. Revoke the exact access
Revoke through the same control you used, as described in Revoke the right thing, then test the old link. Removing one kind of access does not remove the others.
#On each client today
Publishing a conversation or a message works on the web and in the TUI. Both create an explicitly public share and show you a redaction Receipt. The signed-out public page always opens in a browser.
Read Security and privacy for how Atoi handles the data behind a share.
Was this useful?