Manual
QwenWorkThe manual in reading order
Six chapters, each one a thing you do rather than a feature you have. Skim the table and jump.
1. First run
After sign-in you choose a workspace. Personal space is private and carries the free quota; an organisation gives you its models and its file policies. Files do not move between the two, and the choice is remembered per device. Institutional users should join the organisation on day one — migrating later means recreating documents.
2. Producing a document
Type an instruction, or attach material and describe what to do with it. Prefer the second. Once a draft exists, editing happens in the preview: select a paragraph, ask for a change, accept or reject. Whole-document rewrites discard your earlier corrections, so work section by section.
3. The file space
| Area | Holds | Who sees it |
|---|---|---|
| Conversation history | Every task and its output | You, and anyone you share the thread with |
| File space | Generated and uploaded files | Depends on the folder's sharing setting |
| Trash | Deleted files for 30 days | Only you |
4. Sharing
- Share a file, not a folder, when the recipient needs one thing.
- Link sharing creates an external URL that survives the removal of the person who made it — review them.
- Sharing into another workspace copies the file; later edits do not sync back.
5. Administration
Admins manage members, roles, model access and quota. Two settings deserve attention on day one: whether guests can be invited at all, and which models members may use. Everything else can be tuned later without breaking work in progress.
6. When something breaks
- Check whether the client can reach the API — a proxy that intercepts TLS looks like a login bug.
- Try one generation from the web client in the same browser. If it works, the problem is the desktop install.
- Clear the local cache, which fixes most white-window and stuck-preview cases.
- If it persists, file a ticket with the timestamp and the task ID.