Workspace

QwenWorkWorkspace where team output converges

A shared drive with a chat box on top is not a workspace. What makes this one different is that the quota, the models and the file history belong to the organisation, not to whoever happens to be signed in.

Two layers that do not mix

Personal space and organisation space are separate stores with separate quotas. Files created in one do not appear in the other, and switching does not migrate anything. That sounds like a limitation until you consider the alternative: an employee's private draft suddenly visible to an admin, or an org document leaking into someone's personal archive when they leave.

Who can see what

RoleCan doCannot do
MemberCreate and edit in shared spaces, use shared agentsChange quota, see other members' personal space
Space ownerManage members of that space, delete filesChange organisation billing
AdminInvite, remove, set model access, see usageRead an individual's personal space files
GuestAccess a specific shared folderSee the workspace directory

Shared agents, concretely

A shared agent is a saved configuration — instructions, reference files, output template — that members invoke with their own inputs. The point is consistency: everyone producing a monthly report gets the same structure, because the structure lives in the agent, not in a document about the structure that nobody reads.

The part that surprises people

Setting up permissions for the first time? The permissions tutorial has the checklist.