https://community.rws.com/ideas/en-USTelligent Community 12 Non-Productionhttps://community.rws.com/ideas/tridion-ideas/i/tridion-docs-ideas/draft-space---figures-and-inline-images---add-ability-to-use-external-references-from-cdn-damWed, 22 Apr 2026 04:11:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:e57659b0-67f0-463c-a2c6-5f9d691708aeKipp WrightWe manage a large repository of images in a DAM and can reference these images via an external link/CDN reference. Would like ability to use external reference / URL link to the image in a Figure or Inline Image as opposed to having to duplicate the image and upload into TridionDocs.ImagesDraft Spacehttps://community.rws.com/ideas/trados-portfolio-ideas/i/trados-cloud/qa-checker-improvementThu, 16 Apr 2026 09:34:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:d188fa54-a148-451e-b4f1-0e76e46fddcbAndreas MerzHello all, we would like the QA Checker to also pick up the following two use cases: 1. Minus signs on negative figures: For negative amounts preceded by an en dash and a euro symbol, e.g., “–€143m,” it would be helpful if the QA checker reported something like “Maybe replace the en dash before the euro symbol with a minus sign (character code 2212 in Word) in the target file.” 2. Single straight quote: Here is a “single straight quote”: ' // And here is a “double straight quote”: " // This is how they are entered in the Online Editor. You can correct double straight quotes relatively easily in the Online Editor using the button I have attached as a screenshot. But you have to fix single straight quotes using a shortcut, or by pasting them into Word, correcting them, and then pasting them back into Outlook. Thanks, AndreasTrados EnterpriseQA Checkerhttps://community.rws.com/ideas/trados-portfolio-ideas/i/trados-studio/feature-request-option-for-single-click-term-insertion-from-the-term-recognition-windowThu, 16 Apr 2026 06:14:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:6ef1ca4f-84b8-468e-9263-25c056a918f6Shosaku TakataniHello Development Team, I would like to request an option to simplify term insertion from the Term Recognition window . Currently, inserting a term requires two steps: right-clicking a term and selecting “Insert term translation” from the right-click menu. This process feels unnecessarily cumbersome, especially since it is performed frequently during translation. It would be very helpful to have an option to insert a term with a single click . Frequently repeated actions should be simplified as much as possible. Thank you for your consideration.Trados Studiohttps://community.rws.com/ideas/trados-portfolio-ideas/i/trados-cloud/automatically-process-the-corresponding-bilingual-excel-file-for-bilingual-excel-file-typeMon, 13 Apr 2026 07:44:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:b8ee23a8-fddd-4243-a897-1acf3eeb16e4Louis LuCurrently, when creating a new TE project, the user has to select the target language for each bilingual Excel file individually. Would it be possible to remove this step so that TE can automatically process the bilingual Excel file according to the language code of the file name (e.g., ja-JP)? Thank youFile Type Settingshttps://community.rws.com/ideas/trados-portfolio-ideas/i/trados-studio/batch-create-return-packages-for-multiple-projectsSun, 12 Apr 2026 07:55:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:e4181f36-12ec-4f8a-b78a-8404f01000b9Sameh ElsharkawyProblem Currently, when you receive and open multiple Project Packages from a client or project manager (e.g., one per language, one per document, or multiple batches), you must complete them and then create a Return Package for each one individually. There is no way to select several projects at once and generate all their Return Packages in a single operation. The Create Return Package wizard only works on the currently selected project. Given the right-click menu shown in image.png , the Create Return Package command is only available for a single selected project. It is not available when multiple projects are selected. Why This Is Important Time efficiency – Freelancers and LSPs regularly handle 10–20+ project packages per week. Creating return packages one by one is repetitive, tedious, and time-consuming. Workflow consistency – When all projects are finished, you should be able to select them all and generate return packages in one click, rather than manually processing each one. Batch tasks precedent – Trados Studio already supports batch operations in other contexts (e.g., Batch Tasks for multiple files). Extending this to Return Packages is a logical and consistent improvement. Common real‑world scenario – Many linguists receive multiple packages from the same client or project manager. Being able to return them all at once would significantly reduce administrative overhead. Proposed Solution Enable multi‑selection in the Projects view. When two or more projects that originated from Project Packages are selected, enable the Create Return Package command. Launch a Batch Create Return Package wizard that: Lists all selected projects. Allows the user to specify an output folder. Generates one .sdlrpx return package per project automatically. Optionally, include a progress indicator to show the status of each package creation. Additional Context This feature is specifically for projects created by opening Project Packages ( .sdlppx ). It does not apply to locally created projects that did not originate from a package, as those cannot produce return packages anyway.Projects viewworkflowproductivityProject Managerbatch processingreturn packageUI/UXpackageshttps://community.rws.com/ideas/trados-portfolio-ideas/i/trados-studio/persistent-custom-filters-folder-dropdown-loader-in-advanced-display-filterSun, 12 Apr 2026 04:22:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:0aa23c94-3ca3-43ee-b2d6-774985c3bd52Sameh ElsharkawyProblem Currently, in Trados Studio’s Advanced Display Filter, you can save custom filters and later import them. However, every time you need to load a saved filter, you must manually browse to the folder where you stored it, locate the file, and import it again. You have to remember where you saved each filter. The process is repetitive and breaks workflow, especially when switching between multiple custom filters (e.g., “Segments with Tags + Unlocked”, “Only Locked”, “Long Target”, etc.). There is no way to define a default filters folder or see a simple dropdown list of your saved filters inside the UI. Why this is important Speed – A translator might apply a custom filter dozens of times per project. Browsing every single time is a significant time sink. User experience – A dropdown is a standard UI pattern for quick access. It would align with other Studio panels (e.g., saved searches in Find/Replace). High-demand filters – Some advanced combinations, such as “Segments containing tags + Unlocked” , are very difficult to recreate manually each time. Being able to save such a filter and load it in one click is a highly requested feature. Organization – If the dropdown could also support categories/folders (e.g., “QA filters”, “Length filters”, “Tag filters”), that would be ideal for power users. Proposed solution Add a setting in Advanced Display Filter preferences: Default custom filters folder – user browses once to select a folder. Ideally Trados would remember the path of this folder every time and not have to make the user browser for it everytime Studio is opened. Add a dropdown list next to the “Load”/“Import” button (or replace the current file‑browse action with a dropdown). The dropdown automatically lists all *.sdladfsettings filter files found in that folder. Selecting an item from the dropdown loads the filter instantly. (Optional but ideal) Allow subfolders inside the main folder to appear as categories in the dropdown (e.g., via indentation or a nested menu). Example use case A user saves a filter called Tags + Unlocked - Medium Length.tdf in their default folder. Later, they open the Advanced Display Filter, click the dropdown, see that filter name, select it – and the filter is applied immediately. No browsing, no hunting.Dropdown menuworkflowadvanced display filterCustom filtersUI/UXhttps://community.rws.com/ideas/trados-portfolio-ideas/i/trados-studio/add-shortest-first-longest-first-sorting-options-for-target-segment-length-in-advanced-display-filter-and-the-regular-filtersSun, 12 Apr 2026 04:01:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:d12a0f79-80f1-46c6-885e-dc81de1eda4fSameh ElsharkawyProblem In the current Advanced Display Filter of Trados Studio, there is no way to sort segments based on the length of the target text. Users cannot quickly bring the shortest or longest target segments to the top of the editor view. This makes it unnecessarily difficult to review, edit, or validate segments that are either very concise (e.g., UI strings, short answers) or excessively long compared to the source. Why this is important Efficiency when editing short segments – Translators often want to process very short target segments first (e.g., single words or short phrases) to get them out of the way or to ensure they are correct before handling longer, more complex sentences. Quality assurance – Long target segments may indicate potential issues (e.g., missing line breaks, overly verbose translations, or incorrect tag placement). Sorting by length would help reviewers spot anomalies faster. Consistency checks – When working with termbases or style guides, seeing the shortest targets first can help identify inconsistent handling of short terms across the file. Cognitive flow – Some linguists prefer to start with “easy” short segments to build momentum; others prefer to tackle long segments first. Providing both options supports different working styles. Proposed solution Add two new sorting criteria to the Advanced Display Filter drop‑down menu (or as separate buttons in the filter bar): Shortest first (ascending target character/word count) Longest first (descending target character/word count) note This feature already exists in other translation environments such as Phrase (formerly Memsource). I mention this not to compare tools in a competitive way, but simply to highlight that the functionality is technically feasible and widely appreciated by many linguists. Adding it to Trados Studio would align with common user expectations and further improve the editor’s flexibility.sort shortestsort longestfilteringadvanced display filterhttps://community.rws.com/ideas/trados-portfolio-ideas/i/trados-studio/feature-request-clickable-urls-in-termbase-viewerFri, 10 Apr 2026 19:03:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:e66be75d-c2aa-46d0-947c-90498fa703c8Shosaku TakataniHello Development Team, I would like to request that URLs entered in the Termbase Viewer be recognized as clickable links . Currently, URLs are displayed as plain text and cannot be opened directly, requiring manual copy and paste into a browser. Enabling clickable links would make it easier to access reference materials. Thank you for your consideration.Trados Studiohttps://community.rws.com/ideas/trados-portfolio-ideas/i/trados-studio/feature-request-option-to-automatically-convert-initial-letters-to-lowercase-when-adding-termsFri, 10 Apr 2026 18:35:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:765927c7-0bd8-47d3-a938-1bfc831c8b3bShosaku TakataniHello Development Team, I would like to request an option to automatically convert the initial letter of each word to lowercase when adding terms to a termbase from the Editor view . This would eliminate the need to manually lowercase the initial letter of each word, thereby saving time. Thank you for your consideration.Trados Studiohttps://community.rws.com/ideas/trados-portfolio-ideas/i/trados-studio/multi-package-workspace-manager-allow-opening-switching-between-multiple-sdlppx-packages-without-closing-reopeningThu, 09 Apr 2026 14:35:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:2b78c9f0-cd1f-44cf-aa98-9463bb23a562Sameh ElsharkawyProblem Statement Currently, when a user opens an .sdlppx package in Trados Studio, they can only have one package dialog/wizard open at a time (can not select multiple .sdlppx packages) . Open package A → complete the import → close. Open package B → complete the import → close. Repeat for each package. This is time-consuming and disrupts workflow, especially when comparing package contents or batch-processing packages. Proposed Solution A new app / utility that enables batch package handling within Trados Studio: Core Features Multi-package selection Allow selecting multiple .sdlppx files from a folder via Ctrl+Click or Shift+Click . Drag-and-drop multiple packages onto the app’s interface. Queue manager List all selected packages with metadata: Package name Status (Pending, In Progress, Completed, Error) Buttons: Start All , Pause , Resume , Remove from queue . Sequential but unattended processing Open each package one after another automatically. For each package, apply a default action If a package requires a decision (e.g., overwrite conflict), the queue pauses and highlights that package. Session logging After all packages are processed, generate a log: Which packages succeeded/failed. Errors or skipped items. Time taken per package. Optional dry-run mode Preview what each package contains without actually importing – useful for checking before bulk processing. Why This Is Valuable for Reviewers / Users Time-saving – process 20 packages in one go instead of 20 manual sessions. Less error-prone – avoids accidentally reopening the wrong package. Better for QA – compare multiple package contents side-by-side in the queue view. Ideal for power users – LSPs, project managers, or in-house teams receiving multiple packages daily. Example User Workflow PM receives 15 .sdlppx files from a client. Opens the Multi-Package Workspace Manager app from the RWS AppStore. Drags all 15 files into the app window. Chooses default action Clicks Start All → goes for coffee. Returns to see a log: 14 succeeded, 1 failed due to missing language resource – easy to fix. Technical Notes (for RWS review) The app would interface with the existing Sdl.Core.Package APIs. Should respect Studio’s existing package security (password-protected packages prompt once at start of queue). Must not violate the “one package wizard at a time” constraint – instead, it automates closing one and opening the next. Built as a Studio view (not a separate .exe) to stay inside Studio’s environment.Project ManagementproductivityLSPTime Saverbatch processingPackage Managerhttps://community.rws.com/ideas/trados-portfolio-ideas/i/trados-cloud/export-option-email-adresses-of-customersThu, 09 Apr 2026 13:17:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:7648133f-ca15-49ba-8b09-6d6b9ef48ebcEric DouchetThere is no way of exporting email-adresses of all (active, inactive, or both) customers in the Enterprise Users dashboard. Customer Emails are not available in reports either. I think it is rather common to need to communicate with all customers, and to be able to contact directly those who are active/inactive. I would appreciate not to have to type about 400 emailadresses on my own. :-)reportingTrados EnterpriseUser ManagementcustomersCustomer Portalhttps://community.rws.com/ideas/trados-portfolio-ideas/i/trados-cloud/te-online-editor-file-volume-limitationTue, 07 Apr 2026 18:28:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:365b10b5-3b07-4c03-9a4a-9a8958b3b3f1Abbie HillThe TE Online Editor's limit of 100 simultaneously open files impacts linguists' ability to maintain consistency (uniform terminology, phrasing, and style across all project files) and perform cross-referencing (searching, propagating, and verifying content spanning multiple files). In a 178-file project, the remaining 78 files stay closed, excluding them from real-time multi-file tools. Specific examples may include: Cross-file repetitions: Identical segments in closed files (e.g., product names) won't update automatically. Linguists must manually retranslate or propagate later (risking variants). Concordance/Display Filter: Linguists can't query terms/phrases across the full set. Results exclude closed files (may lead to inconsistencies). Review changes don't propagate: Stylistic tweaks in open files fail to update closed files. QA: Verification scans only open files. Cross-file errors between Files 1-100 and 101-178 go undetected without separate passes. Because of this, we need to run QA twice, for each LP in the project.Online EditorTrados Enterprisehttps://community.rws.com/ideas/trados-portfolio-ideas/i/trados-studio/improvement-in-auto-number-replacementThu, 02 Apr 2026 08:17:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:1b1c9ad4-b23d-4787-9204-141979cb6ea3Tomonori ShimadaHi team, In a document containing multiple source segments where only numerical values differ, automatic number replacement works incorrectly in some cases. Here is how to reproduce the issue: 1. First, translate the following English source to Chinses as below: EN: AAAA ( 4 ch monaural 32 kHz/12 bit) * 4 CN: AAAA（ 4 声道单声道 32 kHz/12 位）* 4 2. Then, the following source is automatically translated as below as a 100% match: EN: AAAA ( 4 ch monaural 32 kHz/12 bit) * 3 CN: AAAA（ 3 声道单声道 32 kHz/12 位）* 4 As you see, the number in the part corresponding to " 4 ch" is incorrectly replaced as " 3 声道" while the number in the part corresponding "* 3 " is incorrectly replaced as "* 4 ". However, if you first translate "AAAA ( 4 ch monaural 32 kHz/12 bit) * 3 " to "AAAA（ 4 声道单声道 32 kHz/12 位）* 3 ", "AAAA ( 4 ch monaural 32 kHz/12 bit) * 4 " is correctly translated as "AAAA（ 4 声道单声道 32 kHz/12 位）* 4 " with the numbers properly replaced automatically. This inconsistency in the number replacement behaviors (misreplacement) could lead to serious mistranslation, so it would be great that the issue is resolved in future releases.https://community.rws.com/ideas/trados-portfolio-ideas/i/trados-studio/customize-ribbon-panel-display-and-scroll-behaviorTue, 31 Mar 2026 18:01:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:5e7acea2-fd98-41f6-88a7-d42e704344d6Sameh ElsharkawySubject: Usability Issue: Customize Ribbon Panel Display and Scroll Behavior To: RWS Development Team (Trados Studio) Dear RWS Team, I would like to report a usability and UI issue in the Customize Ribbon dialog in Trados Studio (observed in version 2024). Issue Description The Customize Ribbon panel is currently too narrow and cramped, making it difficult to read item names without excessive scrolling. Even when the dialog is manually resized, the vertical scroll bar remains present inside the panel, and the resizing does not improve visibility or reduce the need for scrolling. This behavior significantly hinders usability, especially for users managing long lists of commands or multiple custom tabs. Expected Behavior The panel should have a larger default size to allow users to view more items without scrolling. When the dialog is resized, the internal scroll bar should adapt or disappear if the expanded window provides enough space to display the full list. The overall layout should prioritize readability and efficient navigation. Impact This is not a bug in terms of functionality, but a serious usability issue that affects user experience, particularly for power users who frequently customize the ribbon. Improving this interface element would align with professional usability standards and enhance productivity. I kindly request that this be reviewed and addressed in a future update or service release. Thank you for your continued efforts to improve Trados Studio. Best regards, Sameh RagabCustomize RibbonUsabilitystudio 2024ResizingStudio 2026Quality of LifeScroll BarUI/UXhttps://community.rws.com/ideas/trados-portfolio-ideas/i/trados-cloud/vendor-tab-missing-in-workflowTue, 31 Mar 2026 09:08:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:997298e7-ba19-4a87-be7e-7000cd530721Manuel BaerWhen creating a project, it is possible to assign vendors in the Workflow page. This needs to be possible during all project phases, but as soon as a project has passed the Project Planning step, the Workflow page does not allow the selection of vendors anymore. As the Vendors tab is then missing completely in the Workflow page, you can only re-assign to a vendor in the Stages view. When in an existing project all manual steps need to be re-assigned from an internal user to a vendor, the project managers need to do this from the Stages view. Example: re-assign the translation to a vendor in the Stages view. Then the project manager needs to wait for the translation to complete, only then can the review task be re-assigned in the Stages view. After that, the PM needs to wait for the vendor to complete the Review before they can re-assign the DTP task from the stages view. The vendor doing the DTP task needs to wait for the DTP task to pop up in the Stages view of the project manager. If the PM is currently not available to do the re-assign from the Stages view, the DTP work cannot start. This is very tedious for the PM as well as for the vendor. It would be much better to always be able to pre-assign all manual tasks from the Workflow view rather than doing it step by step from the Stages view.Project ManagementVendor re-assignmentTrados Enterprisehttps://community.rws.com/ideas/trados-portfolio-ideas/i/trados-cloud/add-the-ability-to-sort-tm-maintenance-search-results-by-recency-most-recent-firstMon, 30 Mar 2026 14:00:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:ce623d84-0ac6-42d2-9808-1275517a6f84Simon Pierre CardinalWhen performing a search in TM Maintenance, results are currently displayed in a fixed order (chronological, based on translation unit number). It would be very helpful to have the ability to sort results by creation date or last modified date (e.g., newest to oldest), or alternatively by translation unit number (highest to lowest). This would make it much easier to locate and review recent entries.https://community.rws.com/ideas/trados-portfolio-ideas/i/trados-studio/missing-option-to-skip-tm-creationMon, 30 Mar 2026 12:27:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:9f41ef0b-f420-4370-904d-3eaaa98d46b6Sameh ElsharkawyTitle: Batch Processing: Missing "None" option for Project Translation Memories Area: Task Sequence / Batch Processing Build: Trados Studio 4.1 Quantum 64-bit Beta Description: In the Project Translation Memories settings under Batch Processing, the user is currently forced to choose between "Create file-based translation memories" or "Create server-based translation memories." The Issue: There are many workflows where a user may want to run a batch task (like Analysis or PerfectMatch) without creating any new Project TMs at all. Currently, there is no way to bypass this selection. Proposed Solution: Add a third radio button option: "Do not create project translation memories." User Impact: Saves disk space and processing time by preventing the generation of redundant .sdltm files for projects where they are not required.https://community.rws.com/ideas/trados-portfolio-ideas/i/trados-studio/feature-request-batch-project-initialization-multi-select-open---as-i-am-doing-beta-testing-of-quantum-4-1Mon, 30 Mar 2026 11:14:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:487461fe-3727-44a8-93ba-181a50166073Sameh ElsharkawyThe Problem The current "Open Project" interface (as shown in my screenshot) utilizes a standard Windows file picker that restricts the user to selecting a single .sdlproj file. For users managing dozens of small projects or daily drops, this requires repeating the "Open -> Browse -> Select -> OK" cycle 10 or 20 times, which is inefficient and repetitive. The Proposed Solution: "Mass Load" Capability Update the Open Project internal logic to allow Standard Windows Multi-Select (using Shift + Click or Ctrl + Click ) within the file browser. Functional Requirements Batch Selection: Enable the selection of multiple .sdlproj files from the same directory. Background Loading: Once "Open" is clicked, Studio should queue the projects and load them into the Projects View in the background, rather than opening them one-by-one with a modal progress bar for each. Quantum 64-bit Advantage: Since this is the first 64-bit release, the system can handle the concurrent memory overhead of parsing multiple project XMLs and their associated TM/TB connections without the "Out of Memory" risks present in the 32-bit architecture. User Experience Impact "Translators and PMs often receive 'kits' containing multiple project files. Forcing a one-by-one import is a legacy 32-bit limitation. The Quantum 64-bit release should empower users to 'Drag and Drop' or 'Multi-Select' an entire folder’s worth of projects into the dashboard instantly."64bit #MultiSelect #WorkflowOptimization #BatchProcessing #UserExperience #UXDesign #Efficiencyhttps://community.rws.com/ideas/trados-portfolio-ideas/i/trados-studio/drag-and-drop-plugin-ribbon-groups-into-custom-tabs-for-improved-usabilitySun, 29 Mar 2026 21:19:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:fe3ad7c5-6005-42f8-b709-99e69e5ac1e5Sameh ElsharkawyDescription Currently, when a plugin is installed in Trados Studio, its buttons are typically added to predefined ribbon tabs such as Home or Review . While users can customize the ribbon by creating new tabs and groups, moving plugin functionality into these custom areas requires manually locating and re-adding each individual button. This process becomes tedious and unintuitive, especially for plugins that expose multiple commands across different categories. Proposed Enhancement Introduce the ability to: Move entire plugin groups (or tabs) via drag-and-drop Allow users to reassign existing plugin ribbon groups directly into: Custom tabs Custom groups Preserve the original grouping and structure of the plugin UI Example Use Case A user installs a plugin whose commands appear under the Review tab. Instead of: Manually searching for each command Adding them one by one to a new custom tab/group The user could simply: Drag the plugin group (e.g., TWAS_ZZ_Arabic_Checker ) Drop it into a newly created custom tab One action instead of multiple steps No need to hunt for commands individually Benefits Improved usability and discoverability Reduced friction for non-technical users Faster workspace customization Encourages better plugin adoption Maintains logical grouping defined by plugin developers Suggested Technical Approach This could be implemented by extending the existing ribbon customization system: Expose plugin groups as movable entities Currently, commands are treated individually Introduce a higher-level abstraction for group-level manipulation Enable drag-and-drop within the ribbon editor Allow RibbonGroup elements to be reassigned between tabs Maintain internal command bindings without duplication Persist layout changes in user configuration Store reassigned group locations in the existing UI layout config Avoid modifying plugin manifests Fallback handling If a plugin is removed, gracefully clean up orphaned groups If a plugin updates, preserve user-customized placement where possible Optional Enhancement Allow plugin developers to flag groups as movable or locked Provide a “Move Group” context menu option as an alternative to drag-and-drop Closing Note This enhancement would significantly improve the customization experience in Trados Studio, making it more intuitive and efficient—especially for users working with multiple plugins and complex workflows.Usabilityuser-experienceribbon-customizationdrag-and-dropPluginsworkflowproductivityenhancementhttps://community.rws.com/ideas/trados-portfolio-ideas/i/passolo-ideas/being-able-to-link-a-cloud-tb-to-passoloFri, 27 Mar 2026 14:13:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:bb65d2a4-ba25-4b65-a02f-c971ee513fa1Marketing TraductionIt would be very useful to link Cloud termbasesto Passolo. That way, we could avoid sending the heavy termabse files each time we have to request translations externally.Passolosuggestiontermbases