https://community.rws.com/product-groups/trados-portfolio/rws-appstore/Including: Desktop & Clouden-USTelligent Community 12 Non-Productionhttps://community.rws.com/product-groups/trados-portfolio/rws-appstore/f/rws-appstore/61067/deepl-api-key-missing-from-product/193594Wed, 13 May 2026 13:41:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:372ff279-bcae-4e91-8e88-42a6ced022e7Patrick Andrew HartnettHi Anna Moorby , please make reference to the documentation here: https://appstore.rws.com/plugin/24?tab=documentation DeepL API Free is not supported.https://community.rws.com/product-groups/trados-portfolio/rws-appstore/f/rws-appstore/61067/deepl-api-key-missing-from-product/193589Wed, 13 May 2026 12:03:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:378f7064-cf3b-400c-a99c-40429a408e3eAnna MoorbyHi there Patrick. So I have the DeepL Pro Teams subscription plus and API Developer (free version), but they don't seem to be talking to each other! Plus I needed a different e-mail account to take out each product. I can't seem to find a single subscription package that includes API access.https://community.rws.com/product-groups/trados-portfolio/rws-appstore/f/rws-appstore/60985/deepl-plugin-not-working-in-trados-team/193588Wed, 13 May 2026 11:58:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:cd6b7b8c-8141-4b38-b095-9593162c34f3Anca StoianBianca Coggiola Hi Bianca, I have opened a case and added the support contract as note for the team to know, please mention this issue of login to them so they can look into it as well. As for the DeepL one, the team can investigate if it's related to us or not the issue you indicated. We will be pleased to help you with this problem so have logged a support case on your behalf. We do prioritise customers who have a support contract so please keep in mind it could take up to 48 hours, especially over a weekend, but rest assured we will contact you as soon as we can. You will be contacted at the email address used for this Community. Support Case Id : CS0048844.https://community.rws.com/product-groups/trados-portfolio/rws-appstore/f/rws-appstore/61067/deepl-api-key-missing-from-product/193587Wed, 13 May 2026 11:57:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:dc4ccbfa-4218-4fed-b680-06e7241e894bPatrick Andrew HartnettHi Anna Moorby , To use this provider, you need a valid DeepL subscription that includes API access and provides a valid DeepL API key . Useful DeepL resources: DeepL API plans and pricing DeepL help: using DeepL with translation tools DeepL help: authentication keyhttps://community.rws.com/product-groups/trados-portfolio/rws-appstore/f/rws-appstore/60985/deepl-plugin-not-working-in-trados-team/193586Wed, 13 May 2026 11:52:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:6332f75e-40d4-4ed6-9092-bc50cb08ccebBianca CoggiolaInitially I tried with my company's email (that's what my Trados Team account is associated with). I have now tried with the gmail account and I still get stuck the same way. The login screen is displayed, I enter the credentials, and then I'm redirected back to the portal's homepage.https://community.rws.com/product-groups/trados-portfolio/rws-appstore/f/rws-appstore/60985/deepl-plugin-not-working-in-trados-team/193584Wed, 13 May 2026 11:17:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:42f12b52-2d06-469a-876c-23c1c311af08Anca StoianHi Bianca I verified and you are registered as a support user with a gmail email address, is that the email which you used to log a case?https://community.rws.com/product-groups/trados-portfolio/rws-appstore/f/rws-appstore/60985/deepl-plugin-not-working-in-trados-team/193583Wed, 13 May 2026 11:04:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:0ed05cc9-11fb-4dd2-a07b-3c20d7c01973Bianca CoggiolaHello Anca, It is still not working. This has been happening since the plugin update. We have a valid API key. Moreover, I am unable to log a case in the support website. I keep getting redirected to the pre-login screen when I try to log in. After sending an email about the issue to rwssupport@rws.com I get an automated reply directing me to the support website.https://community.rws.com/product-groups/trados-portfolio/rws-appstore/f/rws-appstore/61067/deepl-api-key-missing-from-productTue, 12 May 2026 15:03:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:7d021c52-67ed-4e49-ab3a-60521259b145Anna MoorbyI recently subscribed to the DeepL Team package (after 30 March 2026) with the hopes that I could integrate it as a plug-in to my Trados Studio 2022 SR2 - 17.2.12.19268 However, when I try to add the plug-in, which I downloaded from the RWS Appstore, it's asking me for an API key, and there isn't one listed anywhere under my account. The only information I have under my account is: Account details Login details and name Email XXXXXX Change Password ●●●●●●●● Change Display name Not specified Change Set up two-factor authentication for your personal account Disabled Enable Billing information XXXX United Kingdom Change Language English Change Customer reference Not specified Change Billing email address Not specified Change DeepL support has said I should be able to see an “Authentication Key (CAT tools)”. But that's not there either. Any ideas? Thanks in advance.https://community.rws.com/product-groups/trados-portfolio/rws-appstore/f/rws-appstore/61013/microsoft-copilot-aws-ai-for-trados-studio/193560Tue, 12 May 2026 13:27:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:ad6d15b5-8d0e-4c47-80bd-fb863d9406b1Anca StoianHi Paloma You can check this App - AI Localization with Custom.MT - perhaps it is something you can work with: https://appstore.rws.com/plugin/146?tab=documentation Best regards, Ancahttps://community.rws.com/product-groups/trados-portfolio/rws-appstore/f/rws-appstore/60985/deepl-plugin-not-working-in-trados-team/193558Tue, 12 May 2026 11:07:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:0d59260f-fd15-40c6-b808-418de3826e45Anca StoianHi Bianca Coggiola , Can you please let me know if this is working now? thank you. Best regards, Ancahttps://community.rws.com/product-groups/trados-portfolio/rws-appstore/f/rws-appstore/61048/questions-for-optimal-use-of-the-openai-plugin-in-trados-studio-2022-aipe-mtpe/193505Fri, 08 May 2026 11:25:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:3723e1ed-d388-4bd0-bb4f-fb783b2cad4cRWS Community AIProbability score: 0.8 Question improvement suggestion: To enhance clarity, consider breaking down your questions into more specific sub-questions or providing examples for each point to facilitate more targeted responses. In the meantime, based on the information you have provided, here is a suggested answer to your question: Hello Miha, Thank you for your detailed inquiry regarding the optimal use of the OpenAI plugin in Trados Studio 2022. Below, I will address your questions step-by-step: **1. Workflow:** - The segments labeled with "DEEPL" indicate that the text was translated using DeepL, while those labeled "AI" suggest that the AI has modified or enhanced the DeepL output. - The AI typically post-edits the DeepL output where it detects issues, focusing on stylistic and semantic optimization. It may also partially retranslate segments if necessary. - To compare DeepL-only output versus AI-modified output, you can use the PostEdit Compare tool, which reports translation modifications during the post-editing phase. **2. Context:** - The AI processes segments in isolation, but it can access broader context if configured to do so. - To ensure terminological and stylistic consistency across the document, you can utilize your termbase and translation memory effectively. Document-level or batch-context functionality may be limited, but you can manage consistency through careful project settings. **3. Prompt Management and Learning:** - The AI learns from confirmed segments and translator edits, allowing it to remember client-specific preferences and terminology. Using consistent prompts can help maintain this learning. - Regular updates to prompts are recommended, and managing prompts can be done globally, per client, or per project, depending on your workflow needs. - The prompt is typically applied at every AI call, and it's advisable to keep prompts concise to ensure effective processing. **4. Terminology, TM, and QA:** - The AI respects Trados Termbases and Translation Memory, but in case of conflicts, the priority may depend on your project settings. - The AI can assist with terminological consistency, style harmonization, and fixing typical QA issues, but you should verify its output against your TM and TB. **5. Quality Control and Risk Management:** - For regulated or sensitive content, it is advisable to use the plugin with caution. You can adjust settings for more conservative output and minimize risks of over-paraphrasing or hallucinations by closely monitoring the AI's suggestions. - It is generally recommended to avoid using the plugin for highly sensitive or critical content types unless you have established robust quality control measures. I hope this answer addressed your question. If not, please reject the answer, add the question improvement suggestion information, and click the RWS Community AI checkbox on the right to try again. RWS Community AIhttps://community.rws.com/product-groups/trados-portfolio/rws-appstore/f/rws-appstore/61048/questions-for-optimal-use-of-the-openai-plugin-in-trados-studio-2022-aipe-mtpeFri, 08 May 2026 11:24:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:f2a7f900-eec1-4c3a-8f85-0a678556d91eVANJA RENDULIC MEDVESCEKHello, My name is Miha and I am a Project manager at a Slovenia-based LSP, Translat d.o.o. We have recently started using your OpenAI plugin (with gpt-4o-mini model) in Trados Studio 2022 in combination with MT (primarily DeepL). While we understand the basic functionality, we would like to make more effective and structured use of the plugin and integrate it properly into our AIPE / MTPE workflows. To that end, we would appreciate your clarification on the questions below. 1.) Workflow: After MT and AI processing, we see some segments labelled with DEEPL and others with AI; What does this mean in practice? Does the AI only post-edit the DeepL output where it detects issues? Does it partially retranslate segments? Is the focus mainly stylistic and semantic optimization? Is there any way to review or compare DeepL-only output vs. AI‑modified output? 2.) Context: Does the AI process each segment in isolation, or with access to broader context (paragraph or document level)? If processing is segment-based: How is terminological and stylistic consistency ensured across the document? Is there any document-level or batch-context functionality available? 3.) Prompt Management and Learning: Does the AI learn from: confirmed segments, translator edits, or only from prompts? Can the AI remember client-specific preferences, terminology, or style (e.g. on project or profile level) after several usages? Is this predetermined by using an identical (or upgraded) prompt? Are regular updates to prompts recommended, and do you have any best-practice guidance? Based on your experience, what is the most effective way to manage prompts: globally, per client, per project, per language pair...? Is the prompt applied at every AI call or only initially? Are there recommended limits regarding prompt length or complexity? 5.) Terminology, TM, and QA: To what extent does the AI respect Trados Termbases and Translation Memory? In case of conflicts, which has priority: TM/TB or AI output? Can AI also assist with: terminological consistency, style harmonization, fixing typical QA issues (numbers, units, formatting) 6.) Quality Control and Risk Management: How do you recommend using the plugin for regulated or sensitive content (EU texts, legal, life sciences, technical documentation)? Are there settings for a more conservative output? How can the risk of over-paraphrasing or hallucinations be minimized? For which content types would you not recommend using the plugin? Thank you very much in advance for your insights. We would also be happy to review any documentation, best-practice examples, or to discuss these topics during a short call or workshop if available.AIPEOpenAI plugintrados studio 2022AI Professionalhttps://community.rws.com/product-groups/trados-portfolio/rws-appstore/f/rws-appstore/61027/quantum-beta7-cliking-on-a-project-file-triggers-start-of-studio-2024-instead-of-2026-if-2024-is-open/193469Wed, 06 May 2026 13:48:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:ee7a2f2f-fb51-47ac-8730-c7c502f873baAlison FieldAngelo Caltagirone Ciao Angelo, I can confirm this behaviour when double-clicking a project package in Windows Explorer. If Studio 2024 is already open, the package will open to Studio 2024. Interesting... Alihttps://community.rws.com/product-groups/trados-portfolio/rws-appstore/f/rws-appstore/61027/quantum-beta7-cliking-on-a-project-file-triggers-start-of-studio-2024-instead-of-2026-if-2024-is-openWed, 06 May 2026 09:13:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:1331e4f5-06b0-454f-ab55-f406802404b0Angelo CaltagironeHi I realized a couple of weeks ago that when I click on a project file the splash image of Studio Quantum appears, but instead of this version it's the Studio 2024 which opens the project. To open a project on Quantum Studio I need to open it inside of the program with the command Open Project. I thought that when installing the new beta this behaviour would solve itself, but it has not. I still see the splash image of Quantum, but the project opens in Studio 2024. If Studio 2024 is not already open, then Quantum starts. This was never the case before. Kind regards, Angelohttps://community.rws.com/product-groups/trados-portfolio/rws-appstore/f/rws-appstore/61018/terminjectorplus-configuration-formatting-differences-to-improve-100-tm-matchesTue, 05 May 2026 11:24:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:fbecdbc8-fd31-4bca-8732-f1e72c291ba5Joe NashefHello Tommi Nieminen , Is it possible to configure TermInjectorPlus (TIP) to reliably ignore specific character-level differences (e.g. spaces and quotation marks) so that false 99% matches in Trados Studio are set to 100% matches without over-modifying segments or losing leverage? We want to use TIP to normalize minor formatting differences between source segments and TM entries so that they are treated as 100% matches. We are aiming to ignore differences in source texts in Studio where: Non-breaking space are changed to normal space and vice versa Curly quotation marks (single and double/opening and closing, including apostrophes) are changed to straight and vice versa Spaces (normal or non-breaking) before punctuation characters are added/removed Spaces after opening quotation marks are added/removed French-style quotes are changed to English-style quotes (curly or straight) and vice versa Questions; Is the plugin expected to support this type of use case (normalizing formatting-only differences for matching)? Is there a recommended approach or best practice? Can a working rule / configuration be provided to test? for some of the aspects if possible. Thank you,terminjectorhttps://community.rws.com/product-groups/trados-portfolio/rws-appstore/f/rws-appstore/61013/microsoft-copilot-aws-ai-for-trados-studioMon, 04 May 2026 13:26:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:9e431fa8-dc8a-4883-8f44-4bafef4605bcPaloma Fernández DuránWe are using OpenAI provider for Trados Studio at the moment, but the company is considering moving towards Microsoft Copilot / AWS as AI providers for the future. Are there any plugins available to call Copilot / AWS AIs via API, similar to the "OpenAI Provider for Trados" one? If not, are there any alternatives? Thanksplug-inPluginStudioAI Professionalhttps://community.rws.com/product-groups/trados-portfolio/rws-appstore/f/rws-appstore/60882/trados-data-protection-suite-not-working---studio-2024-sr1/193411Mon, 04 May 2026 11:06:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:f845134c-beed-4e55-9929-f97933ad492aEuripides GerardisHello, I am also having a similar problem with Trados 2024 and the Data Protection plug-in. When it starts via a Protect Data Batch Task operation, an error pops up that says: Value cannot be null. Parameter name: value (a rough translation from Greek as the error dialog box appears in Greek even though the UI on the entire machine is English). Initially, it did not start at all because the Settings.JSON file was missing, so I created an empty JSON file, but it appears the solution is not that simple. The TM Anonymizer plug-in does not help. In fact, I do not think it is even relevant. Can you please suggest a solution to this? Thank you all.https://community.rws.com/product-groups/trados-portfolio/rws-appstore/f/rws-appstore/60687/openai-provider-for-trados-studio-documentation-seems-incorrect-to-me/193406Mon, 04 May 2026 09:21:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:e3b7695d-948b-4123-a8f5-7fdcc9f7e552Angelo CaltagironeHi Patrick Andrew Hartnett I have created a custom batch task With this Providers activated: With these pretranslate settings And these settings for OpenAI Provider This should work now. Can you please quickly confirm? Thank you very much, Angelohttps://community.rws.com/product-groups/trados-portfolio/rws-appstore/f/rws-appstore/60687/openai-provider-for-trados-studio-documentation-seems-incorrect-to-me/193400Mon, 04 May 2026 07:37:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:6812dbd4-9948-4493-a2fa-572d2bd396a9Patrick Andrew HartnettHey Angelo Caltagirone , Yes, you can do this in one custom batch task . Think of it as two phases inside the same custom batch task: A. First phase: normal pre-translation Run Pre-translate Files using your TM and Lara. Important: in this phase, OpenAI should not be used as a normal translation provider, otherwise it will also translate at the same time as Lara. B. Second phase: OpenAI refinement Then add Pre-translate Files with OpenAI provider as the next step in the same custom batch task. Here OpenAI is used specifically to review/refine/update the translations that already exist from the first phase. C. Result Your custom batch task would look like this: Pre-translate Files TM enabled Lara enabled OpenAI not used for this normal pre-translation step Pre-translate Files with OpenAI provider OpenAI prompt used to refine the existing translations for example: apply terminology, follow style rules, improve Lara output, etc. So your PMs should not need to run two separate batch tasks manually or change settings between them, as long as the custom batch task is set up this way. The key point is: Use Lara/OpenAI together only if you want them both to generate translations independently. Use Lara first and OpenAI second if you want OpenAI to refine Lara’s output. In your case, because you want Lara to create the translation and OpenAI to improve it afterward, the combined custom batch task is the right approach.https://community.rws.com/product-groups/trados-portfolio/rws-appstore/f/rws-appstore/60687/openai-provider-for-trados-studio-documentation-seems-incorrect-to-me/193397Mon, 04 May 2026 06:37:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:366bdb74-2df2-4d6f-8513-0a5b50b2f781Angelo CaltagironeHi Patrik Thank you for clarifying. This would be the best scenario if the plugin would work as it should. The results in the results window (as I wrote already in another post for Beta Quantum) does rarely insert terms taken from the TB, whereas the AI Assistant makes a much better work. And in both cases (results windows and AI Assist) it adds code parts. Therefore, if I pretranslate with both batch tasks, sometimes you have maybe a good pretranslation with MT wich is overwritten by the plugin with codes (and no terms taken from the TB) and I have to manually delete the codes and insert the terms. At the moment, I pretranslate with my MT provider and then work one segment after another with AI Assist, which is more time consuming. It would be great if you could fix the problem of the plugin. Thank you, Angelo