AI That Shows Its Work
For most of the past year the honest complaint about AI in a translation pipeline was not whether it worked, but whether you could see it working. This release answers that directly. When an AI agent handles a job, the AI Agent Work Status popup no longer sits on a single "Executing" line: it now shows live progress such as "Processing... 42%" and keeps refreshing while it is open, so you can tell the difference between a job that is nearly done and one that is stuck. The same visibility now covers document preparation. When an AI engine runs the machine translation phase of preparing files, the Prepare Files popup reports the percentage completed per target language instead of a static "Counting..." message that gave no sense of movement.
The AI also gets better at drawing on the right knowledge. In an MT Hive order form, segments are first filled from the memories and term bases listed on the form, and whatever is left goes to machine translation. When that step uses an AI engine, the AI now draws on exactly those memories and term bases, so its output follows the client's own terminology and past work rather than starting from scratch. Resources are always resolved from the order's own form, never borrowed from another client.
Two smaller changes make agents easier to live with at scale. A supplier can now give each AI service an optional alias, so two "Translation" services, one tuned for legal content and one for life sciences, are finally distinguishable at a glance wherever the AI icon appears. And custom instructions written the natural way, across several lines with tabs and a bulleted list of guidelines, now run correctly in AI flows instead of failing before producing any translation, post-edit, or quality check. If you want the fuller picture of how AI suppliers fit into a workflow, the AI-powered suppliers guide on help.wordbee.com walks through the setup.
AI on Your Terms
Visibility is one half of trust; control is the other. A new "Disable AI assistants for project" option lets administrators and project managers switch off the Editor's AI features for a single project while keeping AI available everywhere else. When it is on, the AI suggestion and rephrase button and the AI filters disappear for translators on that project, so you can offer a client work that carries no AI involvement without changing how your other projects run. The setting can be preset on order form templates and captured in project templates, so new projects inherit it automatically, and it applies to both Standard and Codyt projects. The disabling AI assistants documentation covers where the option lives.
Control also means an AI check that does not quietly move your work forward. You can now run an AI quality check on a job that is in progress and the job keeps its status: the check reports its findings and leaves the workflow exactly where it was, instead of pushing the job to Completed. That holds wherever the check starts, whether from the Editor, the QA panel, a Codyt workflow, or a batch job.
Cleaner Documents In, Cleaner Counts Out
Some of the most valuable work in a release is invisible when it goes right. Wordbee already kept Word text hidden by direct formatting or by a paragraph style out of translation, but text hidden through a character style still slipped in. Character styles are now recognized too, so confidential or instructional content stays out of your projects and out of your word counts however the author chose to hide it. Documents already parsed keep their current content until a new version is parsed. The Word configuration options page explains the full set of rules.
Excel gets two related improvements. Cells that hold nothing but a placeholder, a variable, or text marked non-translatable used to drop out of the Editor entirely, leaving translators without their surrounding context. A new option, off by default, shows those cells as locked read-only rows with the target pre-filled to match the source, so translators see the context without being able to change content that should not move. The option covers all three Excel configuration types. Alongside it, monolingual Excel configurations now expose the "Content is html" section, so you can see whether the setting is on and switch it off instead of it sitting hidden and unchangeable; both are documented in the Excel configuration options reference.
Formatting that runs across sentence boundaries used to trip up pre-translation. When bold, italic, or colored text continued from one segment into the next, DeepL pre-translation could leave whole groups of segments untranslated while the job still reported success. Wordbee now prepares those segments correctly before sending them, so they translate and keep their original formatting, and if one segment genuinely cannot be translated only that segment is left blank and the batch continues. The usual failure notifications now report anything that remains, so a silent gap no longer passes for a clean run.
Versions, Memories, and the Right Person for the Job
Repetitive setup work is where project managers lose their afternoons, and several changes here give that time back. When a client sends an updated document in a Standard project, the Create New Version step now offers two options: copy the previous version's workflow and its assigned suppliers so you do not rebuild and reassign by hand, and complete and archive the previous version so its jobs close, the old file moves into a Past Versions subfolder, and the new file takes over the original name. Both are off by default, so keep them unticked when you need to deliver both versions. The versioning guide for Standard projects covers each option.
Memories behave more predictably too. Manual "Consolidate project memory" now honors the translation memory's "Merge Languages" setting, the same way automatic consolidation at the end of a workflow already did. Where manual consolidation used to fold regional languages such as en-US or fr-FR into their base language regardless of the setting, a memory configured to keep regional languages now preserves and creates them, and an explicit choice in the consolidation popup always takes precedence.
Finding the right person got faster on both ends of the assignment. A search box at the top of the Set Worker popup narrows a large supplier company's list to the names matching what you type, so you no longer page through an entire roster to reach one translator. A new "Matching languages only" checkbox, off by default, filters that same list to people whose services cover the job's source language, target language, and task, including regional and wildcard matches, with exact language-pair matches keeping their green flag. Both appear in Job Details and in the Assign Jobs wizard, which is where teams staffing work across many suppliers will notice them most. Finally, a new workspace setting lets you choose whether a supplier's linked invoice is deleted when a Codyt job is reassigned or unassigned, but only when no work had started and the invoice is not shared; jobs in progress, completed, or cancelled always keep their invoices.
Orders and Notifications That Fit the Chain
Collaboration breaks down when the system tells the wrong people the wrong things, and three changes tighten that up. The permission that lets an external supplier see order references and client details already worked on the Standard lists, but the two Codyt lists hid the Order Reference and Order Id columns from every external user, even one who held the permission. Those columns, and the order reference search filter on the Codyt jobs tab, now follow the same access rules as everywhere else.
Comment notifications got more precise as well. Each additional manager on a project is configured for a particular language pair, but the notification list used to offer every additional manager regardless. It now honors that configuration, so commenting on a Spanish translation no longer surfaces a manager who only covers Japanese, while the primary manager, who covers the whole project, stays listed. And in outsourced three-party orders, order messages and the proposal-accepted and work-in-progress events are now decided from each recipient's own position in the outsourcing chain rather than a single global label, which closes two gaps where notifications either failed to reach the right party or arrived only by accident. No notification default changed, an explicit opt-out always wins, and ordinary two-party orders are unaffected.
Also in This Release
A handful of smaller fixes round out 2026.3.7.0. Report S410 now shows the client Order ID on every job row whether the order is active or canceled, matching what S400 already did; you can read the details on the report S410 page. Order creation now copes gracefully with files whose name does not match their content, such as an image saved with an .xml name, either completing the order or rejecting the file with a clear "format not supported" message instead of leaving creation stuck. The Manage Counts and Cost popup on Codyt jobs now scrolls when it has many count rows, so Save and Cancel stay reachable with the mouse. You can run a QA check from a job's page in Standard projects even when the job is Completed, with your permission to work on the job being all that matters. And the Add Resource popup now opens reliably on accounts with very large libraries by loading the list in pages rather than all at once.
The full technical notes for 2026.3.7.0 live on help.wordbee.com, with configuration steps and screenshots for each item. If any of these changes will reshape how your team works in Wordbee, talk to our team before you roll them out. We would rather walk you through setup than let a release stumble in production.