Capture Terminology Without Leaving the Job
Every translator knows the moment. You settle on the right rendering of a difficult term, you know it belongs in the glossary, and saving it means leaving the job, opening the termbase, and losing your place. Most of the time the term never gets saved, and the next person solves the same problem from scratch.
This release closes that gap. In the Wordbee Editor, Add to TB/TM in the Edit menu and on the toolbar saves a term to a termbase or a segment to a translation memory without leaving the job. The entry opens in a small window over the grid, so you can keep selecting text while you fill it in, and it saves in your job's source and target languages. The documentation on adding terms and segments while translating covers the details. Terminology captured at the moment the decision is made is terminology the whole team can reuse.
Finding what is already stored improved in three ways. You can now wrap a search in quotation marks in the Memory Finder or Term Finder to match that exact word, so "constitution" no longer also returns "reconstitution"; the quotes apply to that one search and leave your selected mode alone. Lookups now find content stored under a regional variant of your job's language, such as English (United States) in an English job, in every search mode, while resources set to strict language variants still return only the exact language. And the automatic lookups that run when you select a segment always use Similar matching, so a Regex mode left over from an earlier search can no longer leave the panel empty. The Memory Finder panel documentation explains each mode.
An Editor Arranged the Way You Work
No two linguists reach for the same tools in the same order, and a toolbar built for the average user fits nobody exactly. You can now choose which tools appear on the quick toolbar while you work in a job and which live in the More tools menu. Open Preferences > Toolbars and drag tools between the two lists; the toolbar holds up to 15. The toolbars documentation and the preferences reference cover the options. It is a small change that removes a dozen small frictions a day, in the same spirit as the rest of the Editor.
Repeated content now has its own handle. The Filters panel includes a Repetitions filter for each target language, so you can hide repeated segments, show repetitions per document, or show them across the whole project including the first occurrence. A new icon in the segment grid marks the first occurrence of a repeated segment, which makes it obvious where the decision that propagates everywhere else actually gets made. The filters panel documentation lists the options.
Propagation itself follows your preference more faithfully. The "Propagate translations" setting now applies when you propagate by hand from the Edit menu, the toolbar, or a shortcut, not only when you save. If you chose "Overwrite existing", manual propagation also replaces different translations in repeated segments, which is what that setting always implied. The propagation documentation has the full behavior.
Quality Work That Stays Done
Quality assurance works best when the check sits one click from the text it is checking. The Run QA button in the QA panel now starts the check straight away, using the profile and settings already shown in the panel. You can follow progress, cancel it, and watch the panel refresh with the new issues when it ends, with no trip to another screen. The QA panel documentation covers the workflow, and our quality assurance overview shows where it fits in the platform.
Consistency issues now carry the number that makes them actionable. An issue from the Translations Consistency check shows how many different translations a repeated sentence has, for example "4 different translations in 9 segments", and an Apply filter button pulls exactly those segments into the grid so you can compare and correct them together. Knowing a sentence was translated four different ways is the difference between a warning you skip and a problem you fix.
Formatting tags received the deepest work in this release. Formatting such as bold text, links, and placeholders is stored as tags around your translated words, and misplaced tags are the usual reason a final file refuses to build. The QA check and Quick QA now find misplaced tags more accurately and faster, so you catch them before export instead of at delivery. Automatic fixes put formatting on the right words more often, never change your translated text, and leave the translation untouched and reported when a fix cannot be confirmed as safe. In QA profiles where "Check tag order" is off, tags can still change order, but tags nested differently from the source are now reported, because that nesting is what stops the file from being built. The QA categories and Quick QA check pages have the specifics.
Checks also count where they happen. The Work & Delivery tab now recognizes QA checks run inside a job, whether started from the Editor, run automatically at completion, or required by the workflow. The status column, the "Translation checked" filter, and the exported check details all show the most recent check, so a document checked thoroughly inside a job no longer reads as unchecked on the project view.
Bulk actions are where finished quality work tends to get undone by accident, so two changes protect it. Copy text, Memory translate, Pseudo-translate, Machine translate, and Find and replace now offer a "Skip confirmed segments" option, on by default for the actions that fill in translations and off for Find and replace. And when a batch action does change the text of a confirmed translation, its status returns to Neutral, exactly as it does when you edit by hand. That rule applies in Standard and Codyt projects, in both editors, and through the API, and it covers translation memories, termbases, and the source language column. Confirmed counts can drop after a batch run, which is the point: a confirmed status now means somebody confirmed the current text. The batch actions panel and find and replace pages explain each option.
Counting the Work Accurately
Pricing, supplier evaluation, and the business case for machine translation all rest on word counts, so three changes here affect what gets quoted and invoiced.
When a job is completed, Wordbee can now produce a second word count showing how much the translator changed the text they received. Unchanged sentences count as full matches and rewritten ones as no match, using your project's usual match categories, and you can switch between the standard analysis and the edit effort analysis on the job word count screen. For teams buying machine translation or post-editing, that turns a vague sense that the output was good this time into a number you can compare across jobs. The edit effort analysis documentation explains the method.
Word count profiles gained a "Not to translate" section with two optional rules: protect segments that contain only formatting, and protect segments whose source text matches patterns you define. During a word count in Standard and Codyt projects, Wordbee copies the source into the empty target of matching segments, then confirms and locks them, so translators never receive work that was never translation in the first place. The guide to protecting segments that must not be translated covers the rules.
A counting fix closes a gap that cost money. When the word count profile option "Do not machine translate identical repetitions" is on, the skipped copies now count as 100% matches or repetitions instead of No match, so analyses, quotes, and invoices apply your repetition rates to them. Our finance overview shows how counts flow through to quoting and invoicing.
Orders and Supplier Assignment
Assigning work in bulk is less fiddly now. When you assign several Standard jobs at once with "Select supplier", you can search the supplier company and worker lists and choose a worker from your own company, and jobs are matched correctly against each supplier's services for the task and language pair. The same matching correction applies to the "Select supplier" mode for Codyt jobs. See managing Standard jobs and our vendor management overview.
Chasing unanswered proposals can now run itself. In Standard projects, Wordbee can remind a supplier who has not accepted or declined a job proposal. Turn it on in the workflow template, on the tab now called "Job proposals", and choose a delay from 1 to 96 hours. The reminder is off by default and the supplier receives it once, with a link to the job. For a project manager running dozens of parallel jobs, that is one fewer thing to track by hand. The workflow template automation options show the setting, and our workflow overview shows where it sits.
Three order-side fixes keep projects moving. Changing the option on the order form no longer removes the files you already uploaded; on submit, the form flags any file or pasted text the selected option does not accept and holds the order until you correct it. In Standard projects, confirming an order with no files marked for online translation, such as an interpreting order, creates its jobs again. And when a workflow condition cancels every job because the translation memory already covers the content, the final file is created and delivered to the order, as the workflow is set up to do; a manager who cancels all jobs by hand still produces no file.
Access, Identity, and Visibility
Confidential projects now behave consistently. You can mark a Standard project as Secret so only its assigned managers and administrators can find or open it, as on Codyt projects, and the setting stays on until somebody unticks it. Previously, everyday actions such as assigning a manager or confirming an order could switch it off without notice, which is exactly the kind of silent change a confidentiality setting must never make. Our security overview covers the wider set of controls.
Single sign-on gained finer control. SSO settings can now include a list of companies whose users get their profile and company details updated from SSO at login, while users from other companies sign in as usual with their existing details unchanged. It complements the existing excluded-companies list and matters most on platforms serving clients and suppliers with different identity setups. See the single sign-on documentation.
Two smaller changes improve what administrators can see and say. The description of the "Can view user names" access right now states accurately what is hidden: names and company details are always hidden, but a short identifier such as initials can still appear in editors, comments, workflow messages, and reports. And in Settings > Activity > Webhook calls, a new Event column shows which event triggered each call and lets you filter the log by event, with calls reporting a finished request appearing as "API callback". For anyone building on the Wordbee API, that turns webhook debugging from guesswork into a filtered list. The system activity documentation has more.
Also in This Release
Cherokee and Bassa (Liberia) can now be enabled in Settings > Translation Settings > Languages and used as source or target languages, both off by default, as listed on the supported languages page. File and folder names with Japanese, Chinese, Arabic, or accented characters, or symbols such as the registered and trademark signs, keep their exact names in zip downloads, where before they could arrive changed or the archive could look empty on Windows; file contents were never affected. Valid XLIFF and MXLIFF files that contain two closing square brackets in a row no longer fail when you mark them for online translation, and a damaged file now explains the problem more clearly. Job messages in the Editor send correctly when they contain punctuation such as question marks or percent signs, use any language, or reach the full 2,000 characters. When creating or uploading a final file fails, both editors now show a short message explaining what went wrong and what to do next. And the file browser on the Documents tab no longer shows a trial notice or an error page when several people open it at the same time right after a platform restart; files and file operations were never affected.
The full technical notes for 2026.4.4.0 live on help.wordbee.com, with configuration steps for every item above. If the new terminology shortcut, the edit effort analysis, or the not-to-translate rules could change how your team works or what it bills, talk to our team and we will walk you through the setup.