Skip to main content
Everything in the Playground — chats, projects and the files attached to them — can be shared with fine-grained control.

​
Scopes

ScopeWho can seeTypical use
private (default)Only the creatorPersonal experiments, drafts
workspaceEvery active member of the workspaceReference threads, shared research
usersA specific list of members you pickReview before a broader roll-out

​
Permissions

Within each scope you can grant read or write:
  • read — can view messages and files, cannot reply
  • write — can send messages (uses shared credit balance)
Only the owner can change sharing settings, rename or delete — regardless of other members’ permissions.

​
Sharing a chat

Open the chat → click Share in the top-right → pick scope and permission. If you pick “users”, select individuals from the workspace list.
Shared users will see the chat appear in their Shared tab. They can send messages if granted write access, or unsubscribe to remove it from their view.

​
Sharing a project

Projects support the same scopes. Every chat inside inherits — unless the chat explicitly overrides its own scope. Example: Project “Marketing Copy” is workspace-shared. Chat “Q4 launch copy” inside it stays workspace-shared by default. You can override a single chat to private if you start drafting something sensitive.

​
Cascade to files

Files attached in a chat automatically inherit access through that chat. If you give Bob access to a chat and that chat has 3 image attachments, Bob can load and download them. If Alice uploads a file but never attaches it to any accessible chat, Alice is the only one who sees it.

​
Forking

Anyone with access to a chat can fork it — create a new chat owned by them, starting from any point in the thread. The new chat is private to the forker by default.

​
Bookmarks

Bookmarks are per-workspace, not per-user — anyone with access to a chat can bookmark messages from it; the bookmark appears in their personal Bookmarks tab.