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

SectionForNot for
First stepsInstall problems, first task, workspace choiceFeature requests
Documents & reportsLong-form output, structure, formattingSpreadsheet formulas
Sheets & dataMulti-file analysis, formula preservationChart design opinions
DecksNarrative, layout, speaker notesTemplate downloads
Team rolloutPermissions, shared agents, quotaIndividual account issues
AutomationTriggers, idempotency, failure pathsReverse-engineered endpoints
Off-topicAnything elseSupport tickets

Three rules

  1. 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.
  2. Paste the input, not a description of the input — with identifiers removed.
  3. 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

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.