Community
QwenWorkA forum organised by task, not feature
Seven sections, one rule that matters: state the outcome you wanted. Threads that start with a goal get answers; threads that start with a complaint get agreement.
Sections
| Section | For | Not for |
|---|---|---|
| First steps | Install problems, first task, workspace choice | Feature requests |
| Documents & reports | Long-form output, structure, formatting | Spreadsheet formulas |
| Sheets & data | Multi-file analysis, formula preservation | Chart design opinions |
| Decks | Narrative, layout, speaker notes | Template downloads |
| Team rollout | Permissions, shared agents, quota | Individual account issues |
| Automation | Triggers, idempotency, failure paths | Reverse-engineered endpoints |
| Off-topic | Anything else | Support tickets |
Three rules
- State the outcome, then the obstacle. 「I need a two-page summary from this transcript, the output loses the action items」 gets help. 「It is bad at summarising」 does not.
- Paste the input, not a description of the input — with identifiers removed.
- Mark the answer that worked. A thread without a resolution is a thread the next person has to re-open.
What does not belong here
- Account, billing and licence questions — those go to the vendor, not a community.
- Download links. Answering with a re-upload helps one person and endangers the rest.
- Screenshots containing client data. Redact before posting, including in image form.
Who actually answers
Sections are read by people running the same software in the same kind of organisation, not by a support desk. An answer that worked for one company is evidence, not policy — check it against your own isolation rules before you copy it. Threads that reach a working resolution get summarised into the wiki within a release cycle, which is why the wiki reads like a list of conclusions rather than a conversation.
Structured questions with a resolution are worth more than chat. If you want a threaded archive, see Discussions.