Translators Finally Get a Progress View of Their Own
This is the one a lot of you have been asking for. Segment status has always been shared across the whole workflow, which is exactly right for a manager watching the big picture and quietly frustrating for the translator or reviewer trying to keep track of their own work in the same job.
Now every linguist gets a private progress view, per job, that nobody else touches. You mark your own progress as you go, managers keep relying on the shared overall status, and the two never collide. It is the kind of small change that makes a long job feel manageable, and it is the first thing your translators will notice when they open the CAT editor. The behavior is documented in the progress tracking guide, and it is off by default, so you turn it on when you are ready.
Two more touches make the editor feel sharper the same day. Terminology lookups now find a match whatever the capitalization, so a translator working on a heading never misses an approved term again. And every editor link finally reads "Open editor," instead of the old patchwork of "Conduct work" and "View work."
Oversight Reports That Tell Managers the Whole Story
If you run delivery, this is your release too. Two new Excel reports land in Business Reports for managers. The Oversight Report gives you one row per job with its full status history, the suppliers who declined it, the assigned supplier's last login, and your project custom fields. The File QA Oversight Per Language report shows, for every file and target language, whether a QA check ever ran, when, and by whom.
That is the level of visibility a localization manager usually has to build by hand in a spreadsheet, now ready out of the box. Two existing reports also gain optional columns: S410 can surface supplier rates, quote units, currency, service, and pricelist, and S300 can show when an order first reached Results Approved and how long that took. Both are off by default at the template level, so nothing you already rely on changes until you choose to add them.
Your Invoice Data, Locked Down Tight
Here is a quiet one that finance teams will appreciate. The API v2 invoice endpoint now enforces the exact same editing rules as the interface, closing a gap where an API call could make a change the screen would have refused. It blocks edits to aggregation child invoices that used to corrupt aggregated totals, edits to approved invoices by users who should not touch them, and edits made in limited or external contexts.
It is a deliberate, backward-incompatible change for any integration that leaned on the old gaps, and it is the right kind of strict: it keeps your finance data honest. On the same theme, two new per-project settings let a manager override the global status-sync rule and the default visibility of created supplier invoices, covered in the supplier invoices guide, and Report S410 now leaves the Order ID blank for cancelled orders on Codyt jobs, matching Standard.
Workflows That Stop Waiting on Each Other
Two fixes here restore automation your team counts on. In Standard projects that mix a pivot-language workflow with a direct workflow for other languages, the direct language's revision job used to sit and wait for the pivot translation to finish before it could start. Now independent language tracks run exactly as you configured them, with no invented cross-language dependency and no manual cleanup afterward. Separately, with auto-consolidate to the master memory turned on, dependent workflow steps had stopped advancing after the second step. They now run start to finish on their own, in both Standard and Codyt projects.
Also in This Release
The rest sharpens reliability and clarity right across the platform. The Access Rights page now renders in your interface language instead of English only, with clearer descriptions and clickable links to the rights each permission depends on. AI flow parameters across the machine translation connector, the QA AI Analysis rule, and Pricelist Service screens now use the right control for each setting, a spinner, a dropdown, a checkbox, with the recommended default shown until you override it, so future default updates reach configurations you have not customized. If you use single sign-on, Wordbee can now keep accounts aligned with your identity provider automatically: when someone moves company, the old account is deactivated, a new one is created, and the move is recorded in the event log, with no admin step in between. It is part of how Wordbee handles enterprise security at scale, and it is available on request. Supplier service ratings now show for static supplier groups too, and the supplier services column is renamed Rating and Comments to match what it always showed.
The fixes run deep. Translation memory consolidation now skips files with no assigned target language and keeps approval status matched to its translation, so nothing ever looks approved that was never verified. Autopropagation copies a translation to every repeated segment even when the source carries leading or trailing whitespace, like a Word footer. Documents that used to fail silently when marked for online translation now retry cleanly, and Standard workflows that begin with a source-only step can be marked for online translation without errors. The QA popup, when skipping green segments, now shows only the latest run. Inline placeholders survive at segment boundaries in the XML and HTML parser. And the retired Lingua Custodia machine translation provider is removed cleanly, so its old configuration pages no longer crash.
That is a lot of ground for one release, and it is exactly the pace we want to keep. The full technical notes for 2026.2.10.0 live on help.wordbee.com. If private linguist progress or the new oversight reporting sounds like something your team needs, talk to us and we will show you how it works, or explore the Wordbee platform and see the rest for yourself.