Releases 2026-06

This page shows items released so far this month.

Tuesday, June 9, 2026 - Version 2026.2.10.0 SWITZERLAND

NEW Automatic Company Moves for SSO Users

If you use SSO, Wordbee can now keep its user accounts aligned with your Identity Provider automatically. When a person is moved to a different company in your directory, the change flows into Wordbee on their next sign-in: the old account is deactivated, a new one is created under the new company, and the move is recorded in the event log for auditing. The user keeps signing in as usual, with no manual admin step required. Available on request; contact Wordbee to turn it on.

NEW Linguists Can Now Track Their Own Progress per Job

Translators and reviewers can now follow their own validation progress directly in each job, without interfering with other people working on the same segments. Today, segment status is shared across the entire workflow; with this feature on, every linguist keeps a private view per job while managers continue to rely on the shared overall status. The feature is off by default. Contact Wordbee to switch it on. For more information, see: https://help.wordbee.com/wbt/how-linguists-track-their-own-progress-per-job

NEW Oversight Reports for Jobs and File QA, Plus Order and Supplier Rate Extensions

Two new Excel reports are now available in Business Reports for users with the Manager profile. The Oversight Report (Jobs category) lists one row per job with its full status history, the suppliers who declined it, the assigned supplier's last login, and project custom fields. The File QA Oversight Per Language report (Quality category) lists one row per file and target language showing whether a QA check was ever run, when, and by which suppliers. Two existing reports gain optional new data columns: S410 can now expose supplier rates, quote unit counts, currency, service, and pricelist; S300 can now expose the date an order first reached Results Approved status along with the elapsed time from order received and from proposal accepted. The S300 and S410 extensions are off by default at the template level. Tenants who want the new columns must customize their own report templates via Reports > Customize. Existing report outputs are unchanged for any user who does not customize their template, and historical orders already approved at the time of release will show blank values in the new S300 columns. For more information, see: https://help.wordbee.com/wbt/report-s300-client-orders and https://help.wordbee.com/wbt/report-s410-jobs-counts-costs

IMPROVED Typed Controls and Defaults for AI Flow Parameters

The Machine Translation connector, QA AI Analysis rule, and Pricelist Service AI Agent screens now render each AI flow parameter with the appropriate input (numeric spinner, dropdown, multi-select, checkbox, password, textarea, or text) instead of a plain text box. These parameters let administrators fine-tune AI behavior, for example by editing the custom prompt, choosing which content the AI should not process, and controlling which translation memory and termbase matches are sent to the AI as reference (such as 100% matches only or 90% and above, with or without unapproved entries). Each parameter is preceded by an override checkbox. When left unticked, the field displays the recommended default declared by the flow (read-only) and is applied at execution time, so default updates in future releases flow through automatically to non-customized configurations. When ticked, admins enter their own value with inline per-type validation. Mandatory fields keep the override locked on, password fields are masked and never carry defaults, and parameters without a declared field type continue to behave as today's plain text box, so existing configurations keep loading and saving unchanged.

IMPROVED Report S410 Now Hides Order ID for Cancelled Orders on Codyt Jobs

In Report S410 (Jobs, Counts & Costs), the Order ID column on Codyt project rows is now left blank when the job's linked order has been cancelled. Previously the cancelled order's ID was still shown. This brings Codyt rows in line with Standard rows, which already hide the Order ID after cancellation. No action is required from users. The change is visible the next time S410 is generated. For more information, see: https://help.wordbee.com/wbt/report-s410-jobs-counts-costs

IMPROVED Supplier Services Grid Column Relabeled to "Rating & Comments"

The column in the supplier pricelist services grid (Suppliers > Prices) and in the Services block of a person's account page previously labeled "Comments" has been renamed to "Rating & Comments". The column already displayed both the supplier rating (stars) and the free-text comment, but the old header was misleading. Sort behavior and column content are unchanged.

IMPROVED Add Service Rating to Static Supplier Group Members

The member list of static supplier groups now shows the service Rating, matching the dynamic supplier group layout. This makes it easier to compare supplier quality at a glance across both group types. For more information, see: https://help.wordbee.com/wbt/suppliers-groups

IMPROVED Per-Project Overrides for Supplier Invoice Status Sync and Visibility

This release adds two per-project workflow settings on the Cost calculation tab of Standard projects: Synchronize job and invoice/quote status, and Initial visibility for created supplier invoices. Project managers can now override the global status-sync rule and per-supplier-company default cost visibility on a single project. The Job Proposal wizard gains a pre-selected Project default option in its publication picker that defers per row to the project setting or the supplier company default. Defaults preserve existing behavior for every project and no database migration is required. For more information, see: https://help.wordbee.com/wbt/supplier-invoices-for-standard-projects

IMPROVED Standardize Editor-Opening Labels to "Open Editor" Across Jobs and Projects

Editor links across Standard project Jobs (list and expanded view), Job Details, and Work & Delivery (in both Standard and Codyt projects) now consistently say "Open editor", or "Open editor, all documents" for links that open every document of a job, instead of the previous "Conduct work" and "View work" wording. The supplier-facing instructional hint on in-progress jobs has been updated to match. No behavior, permissions, or URLs changed.

IMPROVED Multilingual Access Rights Page With Inline Dependency Links

The Access Rights configuration page now renders in your UI language instead of English only, and every permission has a clearer description with clickable inline links to the rights it depends on, so you can spot dependencies at a glance. A small set of permission names was also renamed to better match what they actually do. Permission behavior and existing profile setups are unchanged.

FIX Enforce UI Edit Rules on the API v2 PUT Invoice Endpoint

The API v2 endpoint PUT /api/invoices/items/{id} now enforces the same per-invoice editing rules as the UI, closing a gap where API callers could make changes the UI would refuse. After this fix the API rejects edits to aggregation child invoices (which silently corrupted aggregated totals), edits to approved invoices by users without access right R443 (Can see invoices prior to approval) enabled, edits made under limited or external user contexts, and edits where the user lacks project or job-level rights. This is a backward-incompatible change for API consumers that relied on any of the bypassed checks. Callers now receive a "not authorized" error, and to modify a child of an aggregated invoice they must first delete the aggregation, edit the children, and re-aggregate. API v1 and UI behavior are unchanged.

FIX Mark for Online Translation Now Works When Standard Project Workflows Start With a Source-Only Step

Standard projects whose workflow starts with a source-only step (for example, a source review before translation) can now have documents marked for online translation without errors. Previously, this action failed when word counting was enabled and displayed a misleading message about missing documents. Users no longer need to disable word counting as a workaround.

FIX Fixed Recurring Failure When Re-Marking a Document for Online Translation

Documents that previously failed silently when marking for online translation now retry cleanly without needing to be renamed. Underlying rollback errors are now surfaced in diagnostics for monitoring.

FIX Word Count and Editor Now Respect Per-File Language Assignments

If you mark a file for only a subset of target languages, pretranslation and machine translation from the word count tab now skip the rest of the languages. The same applies to batch machine translation in the Editor. Out-of-scope language cells also become read-only in the Editor, so no one can accidentally create translations that would flow into your translation memories during consolidation.

FIX Retire Lingua Custodia Machine Translation Connector

The retired Lingua Custodia machine translation provider has been removed from Wordbee Translator. It is no longer available when adding MT systems, and related configuration pages, connector code, and stored provider configurations are cleaned up to prevent stale options and configuration-page crashes.

FIX Translation Memory Consolidation Respects File Language Scope and Preserves Approval Status

Translation Memory consolidation now skips files that are not assigned to a target language, so out-of-scope segments no longer end up in the master Translation Memory. When the same source text exists in multiple files, the approval status and translation text always stay matched together, preventing entries that look approved but contain an unverified translation. The result is cleaner, more trustworthy Translation Memories and reduced machine translation and pretranslation costs from segments that were never meant to be exported.

FIX Workflow Steps Now Auto-Start When Auto-Consolidate Is Enabled

With the option to automatically consolidate translations to the master memory upon workflow completion turned on, dependent workflow jobs stopped starting automatically after the second step, forcing project managers to advance them by hand. This fix restores the expected behavior, so workflow steps progress automatically end to end whether or not auto-consolidate is turned on. The fix applies to both Standard and Codyt projects.

FIX Quality Assurance Popup Now Reflects Only the Latest Run When Skipping Green Segments

In the editor, when you re-run QA with "Skip segments with green status" enabled, the QA popup now shows only the issues found by that run. Previously, the popup could still list issues from a previous run even when no new issues were found, making the skip-green option appear to have no effect. QA issues already shown on individual segments remain visible until you click "Clear issues".

FIX Inline Placeholders Preserved at Segment Boundaries in the XML+HTML Parser

Collapsed inline placeholders, such as protected term wrappers, are now preserved at the start and end of segments when the XML+HTML filter keeps inline tags. Existing TM matches against re-imported files may need to be refreshed because boundary placeholders now appear in extracted text.

FIX Independent Language Workflows No Longer Blocked by Pivot Translation in Standard Projects

In Standard projects that combine a pivot language workflow with a different, direct workflow for one or more target languages, the revision job of the direct-workflow language was incorrectly waiting for the pivot translation to finish before it could start. Independent language tracks now run exactly as configured, without unnecessary cross-language dependencies. Project managers no longer need to manually adjust job dependencies after job creation.

FIX Fix Autopropagation Skipping Repeated Segments With Leading or Trailing Whitespace

Autopropagation now correctly copies a translation to all identical repeated segments even when the source text has leading or trailing whitespace, such as Word document footers with field codes like "Page X of Y". Previously, those repetitions were silently left untranslated because the search trimmed the whitespace while the indexed value kept it, so no exact match was found. The fix takes effect immediately in the Editor for new autopropagation actions on existing data, and has no impact on segments that already worked or on Find & Replace, TM lookups, and repetition detection.