Skip to main content
Workspace sharing is available in Qualia Cloud. Desktop (local) workspaces live on your machine and cannot be shared.
Sharing gives other people access to a cloud workspace in one of three roles. Viewers see everything in the workspace — files, notebooks, chats and their full history, tasks, knowledge — but cannot change anything: they can’t edit or run notebooks, use the terminal, or modify files. Commenters can do everything viewers can, and can also leave comments on notebook cells and knowledge cards. Viewers and Commenters can also chat: they can create their own chats in the shared workspace and message the agents in them. Those chats are read-only too — the agent can read files, search the workspace, and browse the web, but it has no tools that write, execute code, or run shell commands. They can also participate in another member’s chat when its creator enables collaboration; that agent uses its creator’s permissions and usage. See Chats in shared workspaces. Editors can edit files and folders, writeups, tables, tasks, and knowledge; leave comments; and run agents and pipelines. Their agents can edit and execute notebooks, including creating and updating live figures. Editors can also preview and export the workspace. The owner’s account pays for Editor usage. Pipelines and their schedules belong to the person who created them. Other workspace members do not take over those definitions or schedules. Runs use the creator’s current access and charge the workspace owner. Scheduled runs require the creator to retain Editor or Owner access. Owners and Editors can take turns editing and running a notebook. Use the editing status menu in the notebook toolbar to request or hand over control. Agents and running cells continue during handoff. Editors can ask their agents to run shell commands. The integrated terminal remains available only to the workspace owner. Only the owner manages workspace sharing, deletion, workspace settings, billing, and credentials. Editor access is assigned to specific people; joining through an organization or public link always grants Viewer access.

Share a workspace

You must be the workspace’s owner to share it, and your own email address must be verified. Signing in with Google verifies it automatically. Organization SSO does the same when the address belongs to a domain the organization has verified. If you verify in another browser tab, return to the share dialog; it updates automatically within a few seconds.
1

Open the share dialog

Click Share at the top right of the workspace.
2

Add people by email

Type one or more email addresses — paste a list and each valid address becomes its own entry. Incomplete addresses stay in the input for you to correct before sharing. Use the arrow keys and Enter to choose a suggestion. Choose Viewer, Commenter, or Editor, optionally add a message, and click Send at the bottom of the dialog. Cancel clears the invitation draft and returns to the access list. Every address you send to appears under People with access, and everyone you add is emailed a link to the workspace.To share without emailing anyone, clear Notify people by email. The message box disappears and Send becomes Share; access is granted the same way, but you’ll need to tell recipients yourself. You can still email them later with Send email again.The address does not need a Qualia account yet. Someone without one sees their email address in the list, with Hasn’t opened this yet beneath it, until they sign in with that address. Change anyone’s role, send the email again, or remove them from the menu next to their name.If you belong to an organization, your admins can restrict sharing to members of the organization; the dialog tells you if an address is not allowed.
3

Or choose who can join with a link

Under General access, choose who can join. The menu only shows settings available for this workspace:
  • Restricted: no one can join through a general link. People already listed under People with access keep their access.
  • Organization: only current members of the workspace’s organization can join through the link, as viewers. This option is hidden for personal workspaces. Membership is checked directly; sharing an email domain does not qualify someone as a member.
  • Public: anyone signed in to Qualia who has the link can join as a viewer. A Qualia account is still required.
Switching settings invalidates the previous link. It does not remove anyone already listed under People with access, including people who joined through an earlier public link.
4

Send the link

Copy the Sign-in link shown in the dialog. If an older link cannot be displayed, use Reset link to invalidate the old URL and create a new one.
If an organization administrator disables external sharing, Public is hidden. Previously created public links also stop admitting new people outside the organization. Existing members retain their access; organization members can still join. General access shows the effective Organization audience for those links. Use Reset link to generate a new organization link. If your share dialog offers Published to the web, turn it on and copy the Public view link. Anyone with that link can view the published workspace without signing in. They cannot edit, run code, comment, or send chat messages. Turn publishing off to revoke public viewing. An unavailable or replaced link shows This view link is no longer available.

Receiving a shared workspace

Open the invitation email’s Open workspace link and sign in with the email address the owner invited. If the owner shared without notifying you, there is no email: sign in with the invited address and find the workspace under Shared with me.
  • If you already use Qualia with that address, the workspace opens (or is waiting under Shared with me on the Workspaces page).
  • If you have no account yet, sign in with that address — creating an account is free — and the workspace opens once you’re in. The sign-in page names the workspace and the address it was shared with so you can pick the right account.
  • If you’re signed in as a different address, Qualia says so in place of the workspace and offers to switch accounts or go back to All workspaces. There is no way to request access for a different address; ask the owner to share with it instead.
  • If you signed in with GitHub or Apple, your address is not yet verified, so Qualia asks you to verify it before opening the workspace. The Workspaces page and the workspace selector also mention when shared workspaces are waiting on that. Confirming the verification link brings you straight to the workspace.
  • If the owner stops sharing while you have the workspace open, or deletes it, you return to the Workspaces page with a note saying why.
While people are viewing your workspace, a presence indicator in the title bar shows who is currently connected.

Seeing who is looking at what

Avatars in files and chats show which teammates are viewing them. Hover for names. Switching away from a file or browser tab clears your presence there.
Viewers can see workspace files, chats, notebook outputs, and knowledge. Share only workspaces whose contents are appropriate for that audience.

Viewing a shared workspace

Workspaces shared with you appear under Shared with me on the Workspaces page, attributed to their owner, and among the recent workspaces in the title bar’s workspace selector once you have opened them. While one is open, the title bar shows Viewing, Commenting, or Editing, matching your role.
  • Notebooks are live. The current editor’s typing, structural edits, agent edits, and execution outputs stream in as they happen. Opening or reconnecting to a notebook also catches up with the current editor’s unsaved draft.
  • Chats are live. Any open chat streams in real time, whoever its author is — you can watch another member’s conversation with an agent as it happens. When the creator chooses Everyone in this workspace in Chat access, everyone with workspace access can respond. The agents list also updates live as chats are created, renamed, finished, or deleted.
  • Tasks and knowledge show their state as of when you opened them; close and reopen a view to refresh it.
  • Files open read-only for Viewers and Commenters, with a refresh indicator when they change on disk.
  • Presence is mutual. The avatars inside files and chats show you which members have them open, and the same avatars show them what you are looking at.
  • New findings can be accepted or rejected by Owners and Editors. Viewers and Commenters can see findings awaiting review and start chats about them.
To remove a shared workspace from your picker, use its Leave action.

Comments

Comment uses the same ghost-button shape as Project and Kernels. Hover and selected controls keep matching corners inside an evenly inset toolbar. See All shows its count in a compact, regular-weight chip. In Comment mode, the titlebar and its menus retain their normal cursor and controls. Task cards in the task map support hover outlines, comment threads, and pins. Their threads appear in See All. Comment stays solid orange while Comment mode is active. See All uses a softer shaded background while its list is open; both states can be active together. The active Comment control uses solid orange with white content. See All is a text button without a chat icon. Pins, outlines, thread cards, and the comments list appear only in Comment mode. Posting a comment keeps the mode active; leaving it hides them. Read-only viewers can open See All directly to enter the mode and read comments. Comments attach threads of discussion to notebook cells, knowledge cards, and task cards. Everyone with access to a workspace sees its comments; the owner and commenters and editors can write them.
  • Leave a comment with Comment in the top-right titlebar (bottom-right on mobile). Comment mode outlines whatever the pointer is over; click it and write. The orange toolbar reveals See All and an exit button. Press Esc or use the exit button to leave comment mode.
  • Commented things carry pins — one avatar per open thread, clustered in a corner badge visible in Comment mode. Hover the cluster to spread the pins apart, then click one to read that conversation and reply; click it again to close it.
  • Resolve a thread with the check in its header. Resolving hides its pin; replying to a resolved thread reopens it. The owner, any editor, and any commenter can resolve or reopen any thread.
  • See All, inside the orange Comment toolbar, shows every thread in the workspace — including resolved ones and comments on things that are not currently on screen, such as cells in other notebooks. Selecting one jumps to it when possible; a thread whose target is gone opens right in the list.
  • Edit or delete your own comments from a comment’s hover menu. Owners and Editors can delete anyone’s comment; deleting a thread’s last comment removes the thread.
Comments update live for everyone with the workspace open.

Chats in shared workspaces

Every chat belongs to the person who created it. All chats in a workspace are visible to everyone with access. By default, only its creator can message it. The creator can click the small person/people Chat access button beside the chat tabs and choose Everyone in this workspace to let everyone with workspace access participate, including viewers and commenters. Choose Only you to restrict messaging to the creator. Only the creator can change this setting; chats default to creator-only messaging. Everyone with workspace access can still view the chat. The button shows one person for creator-only messaging and a highlighted group when everyone can message. Hover or focus it for the current audience. If you are not the creator, its popover shows Only the creator or Everyone in this workspace as a read-only selection. The workspace Owner and Editors can stop, rename, or delete any chat in the workspace. Collaboration does not grant Viewers or Commenters rename or delete access. Only the owner can change Notify in Slack, and Slack updates are available only for owner-created chats. With collaboration off, viewers and commenters see an author-only notice without a Stop button in chats created by someone else. The Agents section’s bulk Stop control affects chats you created, or all chats if you own the workspace or are an Editor. Bulk Resume affects your own chats. Use a collaborative chat’s individual controls to stop or resume an agent created by someone else. For chats created by a viewer or commenter:
  • The agent is read-only. It can read workspace files and attachments, look up tasks and knowledge, and search or fetch from the web. Tools that write anything — file edits, notebook cells, code execution, shell commands, task or knowledge updates, external integrations — are not available to it.
  • Usage is billed to the viewer. Model usage in a viewer’s chat counts against the viewer’s own plan, not the owner’s.
  • Chats are standalone. Viewer chats cannot attach notebooks or run code.
When a workspace is shared — or has chats created by someone other than the owner — the agents list shows who created each chat.

Working together in a chat

Messages identify their sender. Everyone with workspace access can read the full conversation, attachments, tool calls, and results, including earlier history.
  • Permissions and billing: The agent uses its creator’s permissions. Owner- and Editor-created chats can edit files and run code, and bill the workspace owner. Viewer- and Commenter-created chats stay read-only and bill their creator.
  • Controls: Participants can stop or resume the agent and change its model and research style. Only the creator approves commands or changes other chat settings.
  • Questions: Any participant can answer; the first accepted answer is used and labeled with that person’s name. Drafts stay private until submitted.
  • Queue: Messages sent while the agent works wait in a shared queue. You can edit, remove, or Send now your own queued messages. Collaborative queues cannot be reordered. Stopping the agent keeps the queue; sent messages cannot be edited or deleted. If processing fails, use Send now to retry your message.
  • Typing and reads: Indicators show who is typing and who has seen each message. Hover over avatars for names.
  • Ending participation: Disabling collaboration removes collaborators’ queued messages and prevents new sends. Removing workspace access also removes that person’s queued messages. If the creator loses access, collaboration and active work stop.

Managing access

Removing an Editor or changing them to Viewer or Commenter stops their agents and background jobs. Stopping their notebook code can also interrupt other code running in the same notebook; work in other notebooks continues. Their scheduled pipelines require editing access to run again.
  • Remove a person with Remove access in the menu next to their name. They lose access to the workspace, including open sessions.
  • Removing someone while general link access is enabled prompts you to also reset the link, because anyone eligible to use it could otherwise come back. Choosing Remove and reset link does both in one step; nobody else who already joined is affected.
  • Removing an address that hasn’t opened the workspace yet simply deletes the share; signing in with that address afterwards grants nothing.
  • Send email again, in the menu next to a person’s name, re-sends the “shared with you” email. It can be sent once a minute per person, and each account can send at most 50 share emails a day. Sharing an address again from the box at the top does the same thing, and updates their role if you picked a different one.
  • Reset link, in the General access menu, invalidates every previously copied URL and copies the replacement once. People who already joined keep their access; remove them individually if needed.
  • Restricted, in the same menu, switches the link off so nobody new can join. Existing viewers keep their access.
  • Organization admins can turn off Allow sharing with people outside this organization on the organization page. New email invitations and link joins are then limited to organization members, including joins through previously created public links. People already listed keep their access.
  • Removing a workspace owner from their organization disables that owner’s sharing links and removes access grants for workspaces in that organization. It also removes that person from workspaces shared with them by other members of the organization, disconnects their sessions, and stops their active chats.
  • Canceling an enterprise subscription applies the same cleanup to every remaining member before returning their accounts to the free plan.
  • When a personal account joins an organization, Qualia disables sharing links and removes grants from its personal workspaces before changing its organization scope. The workspace data is retained privately, but sharing must be configured again if the person later returns to a personal account.
The top-right Share button uses the same ghost styling, corners, icon size, and spacing as Project and Kernels. It opens Share workspace. Owners and Editors can also edit text files together in Cloud. Everyone sees one shared draft; agent tools continue using the saved file. Notebook editing uses handoff controls. Rich-text writeups do not support simultaneous editing.