The wxrks Editor's right-side menu is the icon bar you'll see the moment you open a file for translation or review. Every tab on it — Comments, Sous-Chef Suggestion, Suggestions, Instructions, QA Issues, Search TM, Glossary, Filter, Translation Change, Settings, and Review — is covered tab-by-tab, from a translator or reviewer's working point of view, in wxrks Editor Menu for Vendors.
This article assumes you've already read that walkthrough (or don't need to — you're setting things up, not translating). It focuses on the two pieces of the menu that a Project Manager or Account Admin is more likely to configure than to click through: the Sous-Chef Suggestion panel's tuning options, and how the Instructions a vendor sees inside the Editor actually get written and published from the project side.
💡 Who is this for? Project Managers and Account Admins configuring Sous-Chef or writing vendor-facing instructions before a project starts, plus anyone who wants a one-page map of what's on the Editor's side menu. If you're already inside the Editor translating or reviewing, wxrks Editor Menu for Vendors is the more useful article.
The menu, at a glance
Open or close the menu with the Show/Hide menu button in the Editor's top bar. Each icon opens a different tab in the panel next to it:
Comments — leave a note on a segment, visible to everyone with access to the work unit.
Sous-Chef Suggestion — generate a tone-and-style-adjusted AI suggestion for the selected segment. Covered in depth below.
Suggestions — Translation Memory, Machine Translation, Glossary, and AI suggestions for the current segment.
Instructions — project instructions and reference files, written from the project side. Covered in depth below.
QA Issues — automatic consistency checks. See How to use the wxrks QA Check Tool for the full walkthrough.
Search TM — search every Translation Memory linked to the project.
Glossary — search project Glossaries. Only visible if your account has the matching Glossary permission.
Filter — narrow the segment list by source/target text or by metadata (confirmed, locked, has warnings, and more), plus Find and Replace.
Translation Change — edits made to a segment in earlier workflow steps.
Settings — font size, line height, word spacing, and light/dark theme for your own reading comfort.
Review — opens the PDF QA Tool when the project includes an uploaded PDF for your language.
For what each of these looks like once you're actually working a segment, see wxrks Editor Menu for Vendors. For the rest of the Editor — the top bar, segment list, and file actions around this menu — see wxrks Editor.
Sous-Chef Suggestion, in detail
Sous-Chef is wxrks' AI writing assistant panel. Select a segment, tune a handful of style controls, and generate an AI suggestion shaped for that specific piece of content — a press release and a support macro don't need to sound the same, and Sous-Chef is built to let a translator dial that in per segment instead of accepting one generic AI suggestion for everything.
The Tone & Style Shelf holds every tuning control:
Domain — the text's subject area (e.g. "Documentation and Software"), so the suggestion respects the specific context of the content.
Formality — Informal, Neutral, or Formal.
Tone — Professional, Conversational, Persuasive, Technical, or Witty.
Audience — who the text is for (e.g. "Documentation or QA Team"), so the suggestion matches the reader's expected background.
Guideline — a free-text field for a specific instruction Sous-Chef should follow for this segment (e.g. "translate concisely and literally, preserving the file-label context").
Creativity Level — a slider from a more literal result to a more creative one.
After setting these, click Generate Insightful Translation. Sous-Chef will return a suggestion built from those choices. Adjusting these controls only changes what Sous-Chef suggests for you — it never modifies the segment's actual pre-translated content until you choose to apply a suggestion.
⚠️ This tab only appears when your account has AI-assisted suggestions enabled. If it's disabled at the organizational unit or account level, Sous-Chef won't be available.
Writing Instructions and attaching Reference Files
The Instructions tab inside the Editor is read-only for whoever's translating or reviewing — what they see there is written from the project side, on the Communication tab of the project's Overview page.
Messages — quick notes relayed to project managers and stakeholders (not shown to vendors in the Editor). Can be marked Private.
Instructions — a rich-text field (headings, bold/italic/strikethrough, lists, tables, images, links, and code blocks are all supported) for whatever a vendor needs to know before starting the work. This is exactly what shows up in the Editor's Instructions tab, so anything written here should be written with the translator or reviewer as the reader. Click Save Instructions to publish it.
Project Notes — internal notes for the project team, not visible to vendors.
⚠️ Instructions only become visible to vendors once the project is approved, since approval is what creates the tasks they work from. You can write and save instructions either before or after approval — they just won't be visible in the Editor until the project has been approved.
Reference files for the project are attached from the Reference Files tab next to Communication, and show up alongside the Instructions in the Editor's Instructions tab.
Related articles
wxrks Editor Menu for Vendors — the full per-tab walkthrough from a translator or reviewer's perspective.
wxrks Editor — the rest of the Editor's layout: the top bar, segment list, and file actions.
Project Overview — the rest of the project settings, including Reference Files.