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
| Role | Can do | Cannot do |
|---|---|---|
| Member | Create and edit in shared spaces, use shared agents | Change quota, see other members' personal space |
| Space owner | Manage members of that space, delete files | Change organisation billing |
| Admin | Invite, remove, set model access, see usage | Read an individual's personal space files |
| Guest | Access a specific shared folder | See 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
- Removing a member does not remove files they already shared. Shared links have their own lifetime and have to be reviewed separately.
- Quota is consumed by the workspace, not per seat. One heavy user can exhaust the month for everyone.
- The active workspace is remembered per device. A shared machine may open in the previous user's workspace.