0% found this document useful (0 votes)
11 views580 pages

Trados Documentation

The document outlines the integration of Trados GroupShare with Trados Studio, focusing on file assignments that enhance translation workflows and security. It details various functionalities including managing assignments, clearing target segments, defining abbreviations, and enabling token recognition. Additionally, it covers licensing, error troubleshooting, organizational management, and recent updates in Trados GroupShare, including improvements in PDF processing and service password encryption.

Uploaded by

phil.maieski
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
11 views580 pages

Trados Documentation

The document outlines the integration of Trados GroupShare with Trados Studio, focusing on file assignments that enhance translation workflows and security. It details various functionalities including managing assignments, clearing target segments, defining abbreviations, and enabling token recognition. Additionally, it covers licensing, error troubleshooting, organizational management, and recent updates in Trados GroupShare, including improvements in PDF processing and service password encryption.

Uploaded by

phil.maieski
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 580

File assignment

Trados GroupShare and Trados Studio work together to enable file assignments for projects published to a Trados GroupShare server. The file
assignment process enables users to make files in an Trados GroupShare project available only to members of a specific role and only for specific
stages of the translation process.
File assignment improves the translation workflow and enhances the security of Trados GroupShare projects files.

Trados Studio - Trados GroupShare Integration


Each assigned file can be set to one of the default project phases: Preparation, Translation, Review and Finalization. The naming of the phases can
be changed in Trados GroupShare Console. Project phases indicate to the assigned users what their translation task is and show project managers
the current translation stage of each file in the Trados GroupShare project.
For more information about managing assignments, see the Trados Studio 2022 SR1 Help.
You can organize the work on projects that you publish to Trados GroupShare servers from the GroupShare layout available in Trados Studio.
When you create and edit assignments from this layout, Trados Studio sends the assignment information to Trados GroupShare.
Trados GroupShare then provides Trados Studio with the resources necessary for completing the assignments and shows this information in the
Projects view > Files tab.
Trados Studio creates and manages assignments in the Files view with the GroupShare layout active, while Trados GroupShare holds and sends
assignment information in the Projects view.
Trados GroupShare provides the entire infrastructure required to enable file assignments that you create in Trados Studio. Trados GroupShare
servers support file assignment information and communicate it to the Trados Studio users assigned to work on Trados GroupShare project files.
File assignment security
When you work with file assignments from Trados Studio, Trados GroupShare makes each file in a Trados GroupShare project available
only to specific Trados Studio users.
File assignment notifications
Trados GroupShare sends out email notifications to the users assigned to work on the Trados GroupShare project files.
Parent topic: Working with projects
Clearing the content of target segments
You can remove the entire content of a target segment, regardless of whether it contains revisions or not, and then start translating again from
scratch.

Procedure
1. Open the appropriate file in Online Editor.
2. Select the target segment whose content you want to clear.
3. On the Home tab, in the Segments group, do one of the following:
To clear the content of that particular segment, select Clear Target > Clear Target or Alt+Delete.
To clear the content of all the segments having the Draft status, select Clear Target > Clear Draft Segments or Alt+Shift+Delete.
The TU status changes to Not Translated.
Parent topic: Translating content
Defining abbreviations
You can define an abbreviation list for each source language of your TMs.

About this task


When you define an abbreviation list, you edit the language resource template used to create a TM.

Procedure
1. Go to the Resources view.
2. In the Language Resource Templates tab, select the checkbox corresponding to the template of choice.
3. Select Edit.
4. In the [language resource template name] dialog, select Language Resources.
5. Identify the language for which you want to define an abbreviation list and select .
6. In the [language resource template name > language] dialog, select Abbreviations.
7. Type in abbreviations or edit existing ones.
8. Select Finish.
Parent topic: Abbreviations
Enabling time and measurement tokens
You can configure Trados GroupShare to recognize tokens and to localize them automatically. Tokens include: dates, times, numbers and
measurements.

Before you begin


In the case of dates and times, make sure you specify the automatic localization settings for dates and times in Trados Studio. Find these settings
under the project settings or project template settings. Do this for each language pair, under Translation Memory and Automated Translation.
You do not need to do anything for numbers and measurements.

Procedure
1. Go to the Resources view.
2. In the Translation Memories tab, select the checkbox corresponding to the TM where you want to enable token recognition.
3. Select Edit.
4. In the [translation memory name] dialog, select Advanced Settings.
5. Under Recognize, select the checkboxes corresponding to the tokens you want to enable.
6. Select Finish.

What to do next
When you enable recognition, the TM does not automatically scan its TUs, so it does not automatically recognize the tokens in existing TUs. To
force the TM to re-scan its TUs, re-index the TM by tuning its performance.
Parent topic: Time and measurement tokens
Single-user licenses
A single-user license activates Trados GroupShare on that computer.
You can perform online activation with this type of license using an activation code. When you enter the activation code in Trados GroupShare, the
application contacts the Trados License Server and activates your product.
If you are not able to access the Internet from the computer on which you installedTrados GroupShare, you can activate the product offline to
license the product.
Activating single-user licenses online (activation code)
Activating single-user licenses offline
Parent topic: Licensing
Unable to discover an endpoint supporting windows
authentication for service identity.svc
Alternative error messages
Unable to discover an endpoint supporting windows authentication for service identity.svc
Please check that you have entered the correct server connection settings and that the server is available
Symptom
A user in Trados Studio is trying to connect to the Trados GroupShare projects server but gets an error message similar to the above.
Probable cause
The following are all true:
The Trados GroupShare projects Application Server has a firewall (or is behind a firewall).
At installation time, the option 'Integrated security' (or, equivalently, 'Windows authentication') was chosen.
The firewall was not given a rule to allow incoming TCP traffic on the port specified for the Application Service.
Solution
Modify the firewall on the Trados GroupShare Application Server to allow the TCP port to accept connections on the appropriate port.
Parent topic: Problems and solutions
Possibility to delete non-empty organizations
You can now delete also organizations and sub-organizations that contain users, translation memories, termbases, sub-organizations or libraries.
This means that you no longer have to first manually delete all the resources inside an organization before being able to delete the organization itself.
If the resources have been created under the organization that you delete, these resources will be removed from Trados GroupShare altogether. If
the organization that you delete is only referencing resources created elsewhere, these resources will still be available in the source organization.
Deleting non-empty organizations is not available for installations that only include MT Server. This is because the new behavior is handled by the
Execution Service, which is not deployed on MT Server-only installations.
Parent topic: Changes introduced in Trados GroupShare 2020 SR1
WebHooks Service
What is Trados GroupShare WebHooks Service
WebHooks provide a publish/subscribe model for wiring together Web APIs and services. You can subscribe to Trados GroupShare
events and get notified when the event happens through a callback.
Using the Trados GroupShare WebHooks Service
Learn how to configure and use the Trados GroupShare WebHooks Service.
Creating field templates
You can speed up the creation process of TMs that share the same fields. Field templates enable you to work consistently across your TMs.

Procedure
1. Go to the Resources view.
2. In the Field Templates tab, select New Field Template.
3. In the Create Field Template dialog, select General Properties.
4. On the General Properties page:
a. Type in a name and, optionally, a description for your field template.
b. Choose a location for the field template in your organization.
5. Select Next.
6. On the Field Definitions page, specify a name, a type and the values for your field.
The VALUES field is enabled if you choose List or List (Multiple) under TYPE.
7. Click anywhere in the white space and add more fields.
8. Select Finish.
Parent topic: Fields
Exporting language resources as template
When you export language resources from existing TMs, these are saved as a new language resource template that you can reuse.

Procedure
1. Go to the Resources view.
2. In the Translation Memories tab, select the checkbox corresponding to the TM whose language resources you want to export.
3. Select Export > Language Resources.
4. In the [translation memory name] dialog, make any changes (if necessary).
5. Select Finish.

Results
The new language resource template is saved in the Language Resource Templates tab.
Parent topic: Language resource templates
Working with users, roles and permissions
To access an Trados GroupShare resource, a user needs to be part of an organization. Organizations give their users roles and permissions.

Guiding principles of GroupShare access control


Users can have one or more roles in an organization.
Users have the permissions granted by the role.
User can and usually do have different roles, and, therefore, different permissions, in different organizations.
Users' effective permissions in an organization consists of the sum of permissions granted by all the roles users have in that organization.

Example: Users want to update resources


When users try to access resources, for example to update a TM, Trados GroupShare compares the users' permissions to the permissions needed
to perform the action. Users who do not have sufficient permissions cannot access resources and cannot perform actions on them.
Organizations and their components
Organizations are networks of users that share their work and resources.
Resource Links
Each resource belongs to just one organization, but you can link the resources in one organization to any number of other organizations.
Access to the resource via the link is determined by the permissions users have.
Users
Users are the individuals or bodies which collaborate on various tasks within an organization. Users can belong to one or several
organizations where they fulfill roles. Roles enforce the permissions users have over resources.
Standard roles and permissions
A role is a collection of permissions. Trados GroupShare has seven standard roles, while Trados GroupShare Cloud has six standard roles,
which correspond to the most common jobs that users do. The permissions associated to roles can be changed in Trados GroupShare, but
they cannot be changed in Trados GroupShare Cloud.
Changes introduced in Trados GroupShare SR1 CU8.1
This page contains an overview of the changes brought by our latest Cumulative Update for Trados GroupShare 2020 SR1.

Project creation optimizations


We've improved the way Trados GroupShare determines word count flags during project pre-translation. This reduces the time taken for creating
projects that include Language Weaver Cloud machine translation. (CRQ-31902)

Updated PDF conversion technology


Starting with this release, Trados GroupShare uses a new mechanism and underlying technology for processing PDF files in translation projects.
This new technology provides PDF support similar to the previous vendor and, overall, you should get similar results when working with PDF files
in Trados GroupShare.
However, the new PDF file type converts PDF project files into translatable format slightly differently, which can lead to the following differences
when compared to previous Trados GroupShare versions:
Differences in analysis statistics.
Differences in TU lookup results due to changes in how PDF text formatting and segmentation is now handled.
Differences in how images are recovered when generating the translated PDF files.
Differences in how Perfect Match is applied.
Differences in how special characters and symbols are processed. If you use Asian languages or other non-Latin based languages as source
languages, we recommend that you enable the new Use alternative processing (better for non-Latin based languages) option in the
PDF file type settings. This option is available when creating projects or project templates in Trados Studio.
Conversion settings for new and existing projects
PDF file-type configurations in your new and existing Trados GroupShare projects will change according to the new PDF Conversion settings in
Trados Studio 2022 CU6:
Layout - remains and existing setting will be remembered.
Headers and footers - no longer available, will always be extracted now.
Detect tables - no longer available, will always be extracted now.
Image recovery - no longer available, images are kept, but no text is extracted.
Recognize PDF text - no longer available, images are kept, but no text is extracted.
Use alternative processing (better for non-Latin based languages) - new setting for processing special characters and symbols.
Support for scanned PDF documents
Support for scanned PDF documents using OCR (optical character recognition) is limited out of the box.
If a PDF file contains merely a scanned picture of the underlying document, then the new technology will not be able to convert the document. If,
on the other hand, the document is scanned but the text in it is selectable, then the technology will attempt to convert the characters within the
document.
You can test this in Adobe Reader, for example. If it's possible to select any text in the document, then the technology should be able to attempt to
convert it
Alternative approaches
If you need more advanced support for scanned PDF documents, we recommend the following options:
Microsoft Word built-in PDF convertor. This accepts PDF files, including OCRed, for opening files and can save them out in Word
.DOCX format, which you can then process as normal.
Adobe Reader built-in function to save PDF documents in Microsoft Word format. This can be purchased as a separate subscription.
Consider purchasing a third-party solution, such as Abbyy Fine Reader or Readiris. These can convert OCR'ed PDF documents to
Microsoft Word format. These options are available as perpetual licenses or on subscription.
What's next?
We are committed to continue improving PDF support with future updates and are in constant touch with our new vendor around this. While we
are transitioning to the new technology, we are keen to get your feedback around this change via our community.

Fixed issue
Segments pre-translated using Language Weaver Cloud machine translation now correctly show "Neural Machine Translation" (NMT) as segment
status when opening the Trados GroupShare project files in the online Editor or in Trados Studio. (CRQ-29276)
Parent topic: Changes introduced in Trados Groupshare 2020 SR1 CU8
Support articles
You can find a large collection of support articles in the Knowledge Base.
Browse the Knowledge Base for articles about:
known issues and workarounds
troubleshooting
technical announcements
Parent topic: Welcome to the Trados GroupShare 2020 SR1 documentation
Exporting fields as template
When you export fields from existing TMs, these are saved as a new field template that you can reuse.

Procedure
1. Go to the Resources view.
2. In the Translation Memories tab, select the checkbox corresponding to the TM whose fields you want to export.
3. Select Export > Fields.
4. In the [translation memory name] dialog, make any changes (if necessary).
5. Select Finish.

Results
The new field template is saved in the Field Templates tab.
Parent topic: Fields
Service password encryption changes
This release changes the encryption method for some services.
The RabbitMQ password is now encrypted with the same mechanism used in the rest of the GroupShare services for the following:
BCM Service
Editor Service Router
Fine Grained Alignment Service
TM Service
Translation Model Service
Verification Service
The password is configured under the encryptedPassword setting in each service configuration file. Optionally, Configurator.exe tool can be used
to encrypt/decrypt the passwords.
Note: Statistics Service and Editor Service still have the password encrypted in Base64 encoding.
Parent topic: Changes introduced in Trados GroupShare 2020 SR1 CU7
Activating single-user licenses online (activation code)
Activation codes for single-user licenses
Once Trados GroupShare is installed on your computer, you must activate the product using the activation code. This will automatically
connect you to the Activation Server using your Internet connection and allocate the activation code to your computer. This is referred to as
'online activation'.
Getting an activation code
An activation code is used to activate your copy of Trados GroupShare.
Activating your product online with a single-user license
By default, Trados GroupShare will automatically try to perform an online activation through the Internet. If, for some reason, it cannot
access the Activation Server, it will prompt you to perform an offline activation.
Deactivating your product online for a single-user license
Deactivating your product returns the license to the Activation Server.
Moving single-user license to another computer
To use your license on another computer, which has Trados GroupShare, you must first deactivate the license on the first computer. Then,
you can activate it on the new computer.
Parent topic: Single-user licenses
Changes to TM Service
New endpoint to validate and change system metadata fields
Users with Administrative permissions can now use endpoint /api/tmservice/tms/{translationMemoryId}/tus/{sourceLanguage}
/{targetLanguage} to remove or make anonymous any PII (personally identifiable information) like username (or name) from system fields in
GroupShare TMs. This is useful for security policies and GDPR-compliance scenarios.

Empty request bodies endpoint


POST requests to TM Service without a request body now require a Content-Type header (generally with value "application/json"). Here are
some examples:
POST /api/tmservice/tms/{tmid}/export
POST /api/tmservice/tms/{tmid}/fuzzyindex/reindex
POST /api/tmservice/tms/{tmid}/fuzzyindex/recomputestatistics

New response code when resource no longer exists


This release also changes HTTP response status codes when interacting with non-existing TM resources. The HTTP 404 (Not found) status code
is now displayed instead of HTTP 401 (Unauthorized) or HTTP 403 (Forbidden):
HTTP GET api/tmservice/tms/{tmId} with an invalid "tmId"
HTTP GET api/tmservice/tms/{tmId}/language-directions/{languageDirectionId} with an invalid "tmId" or "languageDirectionId"
HTTP DELETE api/tmservice/tms/{tmId}/ with an invalid "tmId"
HTTP GET api/language-resource-service/templates/{templateId:guid} with an invalid "templateId"
HTTP GET api/fieldservice/templates/{templateId} with an invalid "templateId"

Changes in Swagger documentation


You can now access the TM-Service documentation from the GroupShare Swagger UI page at /documentation/api/index. Follow the
instructions there to load the endpoints from /resources/TmServiceRestApiDocumentation.json.
Parent topic: API changes for third-party developers
Fixed issues
Fixed an issue where the File Processing Server folder was not removed when upgrading from Trados GroupShare 2017. The folder is no
longer appearing after upgrading to CU8. (LTGS-11099)
TM language pairs and units were not displayed properly in Project Settings if a TM was referenced with a different server name. The issue
is now fixed. (LTGS-11100)
When changing the phase of a project, Trados GroupShare displayed an error if the user that created the project was deleted. The issue is
now fixed. (LTGS-5537)
Using MultiTerm Online in recent Apache Tomcat versions was generating "java.lang.StackOverflowError" and negatively impacting the
disk space on the web server. This issue is now fixed. (CRQ-31794)
In specific scenarios, downloading the latest file version of a Trados GroupShare project from Trados Studio was generating an error. This
issue is now fixed. (CRQ-31650)
Groupshare Dashboard and Reporting tab are now correctly displayed for German User Interface. (CRQ-31294)
When using Google Chrome, clicking on the "?" icon displayed next to a termbase in the Termbases window, the about.pdf download
indicated Failed Network Error. The issue is now fixed. (CRQ-30332)
Sorting by "User Type" is now displayed properly in Trados GroupShare. (CRQ-29338)
Addressed an issue with incorrect overdue notifications sent for already completed files. (CRQ-28364)
Fixed an issue where Trados GroupShare files in the TranslateAndAnalyze FileStore folder never got removed. The files used by T&A
Service are now deleted from the T&A FileStore. (CRQ-24619)
When generating the Analyze report from a browser, the word count for Asian languages was not displayed correctly. This issue is now
fixed. (CRQ-22007)
Optimized project synchronization to avoid timeouts during file check-in and other operations started from Trados Studio. (CRQ-17825)
TMs with "+" characters in the filename are no longer disabled automatically. (CRQ-17759)
Trados GroupShare would not work properly with only one TM Server installed. The issue is now fixed. (CRQ-17381)
Download link for Exporting terms is now displayed in MultiTerm Online. (CRQ-8769)
The Termbase view now correctly displays results when searching for termbases. (CRQ-6158)
Addressed an issue with the Webhook service potentially remaining unresponsive. (CRQ-31013)
SQL stored procedure improvements that provide new overall performance potential to Trados GroupShare and prevents some timeouts
when downloading target files or opening large projects in Trados Studio. (CRQ-30383)
Addressed an issue in which the GroupShare Application Service ignored the SqlCommandTimeout setting when executing certain SQL
stored procedures. (CRQ-30356)
MultiTerm Online now correctly identifies termbase results based on searches for entry IDs that are not listed on the first page of the open
termbase. (CRQ-26475)
Adding new terms in the Legacy/Classic or Custom layout without filling in all mandatory fields caused MultiTerm Online to terminate the
active user session. This issue is now fixed. (CRQ-18265)
Addressed a recently identified vulnerability in MultiTerm Online. (CRQ-31582)
After publishing a project, Publish Project background task remained In Progress on Trados GroupShare if the project had many files. The
issue is now fixed. (LTGS-11053)
Endpoint GET /API/management/v2/users/{username} >now correctly returns a single user instead of a list of users. (LTGS-10848)
MultiTerm Online now correctly displays all language flags from termbases created in MultiTerm Desktop. (LTGS-10802)
The Languages fields under Resources > Translation Memories are now filterable again. (LTGS-10781)
Incorrect warning was displayed when adding fields with duplicate names in the same field template. The issue is now fixed. (LTGS-10775)
Trados GroupShare would not display TM fields for TMs without field templates and would remove their field definitions after saving the
TM. This issue is now fixed. (LTGS-10751)
Fixed an issue where the Update Files button was disabled for projects that contained reference and translatable files with the same name.
(LTGS-10717)
Update translatable/reference files now work for projects with the same file with different roles in different folders. (LTGS-10315)
Printing functionality now works properly for Analysis Report and the total rows in a table are displayed correctly. (LTGS-10313)
When downloading a version of a file, the notification now displays the correct number of the version. (LTGS-10224)
Update Project button is now disabled when all files are checked out. (LTGS-10218)
Fixed an issue where the selected reference files with folder structure were not updated when uploading a file with a matching name.
(LTGS-10206)
MultiTerm Online could not search for terms when applying a Hard filter where the condition equaled a field with more than 50 characters.
This issue is now fixed. (LTGS-10015)
Trados GroupShare failed to unlink template fields from TMs if more than one template field with that name was available under Resources
> Field Templates. This issue is now fixed. (LTGS-9873)
The width of segments in the Online Editor is now adapted accordingly after increasing the size of the browser window for the Trados
GroupShare tab. (LTGS-8912)
When applying the project template setting to a new project, Trados GroupShare would only pick up the settings coming from the All
Language Pairs level, ignoring any batch task settings available for specific language pairs in the project template. This issue is now fixed.
(LTGS-7692)
When adding TMs to an existing or new project template, the list of TMs would expand on the first click on the expand icon. This issue is
now fixed. (LTGS-6172)
Fixed an issue where CALs for sub-organizations were not released after logout. (LTGS-9814)
When creating a new project from a browser, Trados GroupShare would ignore any custom settings coming from specific language pairs in
the project template. This issue is now fixed. (CRQ-21310)
Parent topic: Changes introduced in Trados Groupshare 2020 SR1 CU8
Project details progress bar
You can consult the progress bar on the Project Details pane of each project.
After you open a project, you will see this information setup in the upper right-hand corner of the screen:

The Preparation, Translation, Review and Finalisation areas show whether the project phases are not begun, in progress or completed. Usually,
when all the files in one phase are checked/translated and passed onto the next phase, the percentage turns to 100%. Any percentage between 0%
and 100% shows that the phase is in progress.
The Estimated project progress is x% bar shows how close to completion the project is overall. The percentage changes based on the number of
translated, confirmed and signed off segments the files contain. When you start translating and the segments are in Draft, the percentage will remain
at 0%. It is only after the segments are confirmed and approved/signed off that the progress bar percentage increases.
Parent topic: Project management
New .NET runtimes
We've made the following .NET runtime changes for this release.
GroupShare no longer requires the Microsoft .NET 5 runtime. You can uninstall the runtime deployed by previous GroupShare versions
(CU08: Microsoft .NET 5.0.17 - Windows Server Hosting, Microsoft .NET Runtime 5.0.17 (x64/x86) and Microsoft ASP.NET Core
5.0.17 - Shared Framework (x64/86)), unless used by other applications on the server.
GroupShare now ships with Microsoft .NET 6.0.16 - Windows Server Hosting. This replaces Microsoft .NET SDK 6.0.403 (x64)
deployed by previous GroupShare versions, which can be uninstalled, unless used by other application on the server.
Parent topic: Changes introduced in Trados Groupshare 2020 SR1 CU9
Accepting revisions
After you receive a reviewed file, you can directly accept the revisions you agree with.

Procedure
1. Open the appropriate file in Online Editor.
2. Find the revision that you want to accept and select it.
3. On the Review tab, in the Tracking group, select Accept.
4. Optional: To accept all the revisions at once, on the right side of the screen, select the Revisions panel, and then select Accept All.
Parent topic: Reviewing translated content
Changes introduced in Trados GroupShare 2020 SR1 CU6
This page contains an overview of the new features and fixed brought by Cumulative Update 6 to our latest major release, Trados GroupShare
2020 SR1.
We are constantly reviewing and improving our products. We release enhancements and fixes to resolve customer issues as and when required. All
changes and fixes are bundled into the cumulative update which you can install from RWS Account > Downloads.
Third-party authorization
Starting with GroupShare 2020 CU6 we support the automatic assignment of user roles in SSO login flows. As a prerequisite, this requires
setting up a group or role membership in the identity provider. Both SAML tokens and JWT clains are supported with automatic role
assignments.
Enhanced security policies
To enhance security, the default Trados GroupShare configuration no longer allows you to access the Online Editor via a different URL than
the one set up as External Server Address in the GroupShare Console.
Improved defense against cross-site scripting
This CU improves the way GroupShare encodes output data on the Web UI. This ensures potential hackers or malware cannot inject
HTML and script characters that could make Trados GroupShare vulnerable to cross-site scripting. We have also updated Jquery to
version 3.6. This version prevents cross-site scripting better than previous ones. (CRQ-24131 and CRQ-26899).
Find your project templates easier
The project template list in the Trados GroupShare Web UI is now displayed alphabetically. (CRQ-24625).
Automatic configuration CP-S: Authentication Server Address
The Trados GroupShare installer now automatically configures the CP-S Authentication Server Address to http://localhost:41234. As a
result, you no longer need to manually configure it for multiple installations. (LTGS-4006)
Interactive Logon permission is no longer required
Installing Trados GroupShare no longer requires Interactive Logon. Previously, specifying a service account that did not have the Interactive
Logon permission would lead to an installation error. Additionally, the Log on as a service permission will be granted to the service user
specified in the Trados GroupShare installer. (CRQ-25634)
Custom Properties Service API
The GET /api/properties-service/info API call now returns the ServiceVersion property instead of serviceVersion. This helps prevent some
issues related to word capitalization when using the search function, for example.
GroupShare REST API improvements
If a translation file exists in GroupShare with a RelativePath property set, the following API calls return the RelativePath property of the file:
GET /api/projectserver/v2/projects/{projectId}/files/detailed-information and GET /api/projectserver/v2/projects/{projectId}/files. This
helps developers support users with files in sub-folders via the GroupShare API. (CRQ-24022)
Updated requirements
This page contains a list of requirement updates related to Trados GroupShare 2020 SR1 CU6.
Fixed issues
This page contains a list of issues fixed by Trados GroupShare 2020 SR1 CU6.
Known issues
This page contains a list of known issues related to Trados GroupShare 2020 SR1 CU6.
MultiTerm Online security hotfix
Download this MultiTerm Online hotfix since it upgrades from Apache Log4j 1.2.13 to Apache Log4j 2.17.1. This newer version prevents
some security issues.
Parent topic: What's new in Trados GroupShare
Viewing comments
You can view the comments added by all users to a specific file, segment, or selection. When you open a file, segments or selections that have
comments are highlighted in yellow.

Procedure
1. Open the appropriate file in Online Editor.
2. On the right side of the screen, select Comments .

Results
All the comments are displayed for that file. You can view the specific segment or selection to which each comment applies by selecting the text of
the comment. To further filter comments, expand the Show All menu, and select the comments of interest according to the available criteria:
Current Segment, Segment, Selection, File.
Tip: When the file you are working on contains comments, a small dot is displayed on the Comments button.
Also, segment-level comments are marked with an icon next to the segment number. For example, in the following image, there is a segment-level
comment on segment 22:

Parent topic: Working with comments


Activation codes for single-user licenses
Once Trados GroupShare is installed on your computer, you must activate the product using the activation code. This will automatically connect
you to the Activation Server using your Internet connection and allocate the activation code to your computer. This is referred to as 'online
activation'.
Once you have activated the product, the license is valid for the machine from which you performed the activation and no further action is required.
If you have to move the software to a different computer, you must return the license by deactivating the product, and then activating the product
again from the new computer, using the same activation code.
Note: If you do not have access to the Internet on the computer where you have the software installed, you can still activate your product using
offline activation.
Parent topic: Activating single-user licenses online (activation code)
Viewing differences between translation memory matches
In Online Editor, you can use the Alternative view to see the differences between source segments and their fuzzy matches from the translation
memory. These differences have to do with words or characters that are either included in source segments, but missing from their matches or vice
versa.

Procedure
1. Open the appropriate file in Online Editor.
2. Select the target row of the segment for which you want to view differences between matches.
3. On the View tab, in the Lookups group, select Alternative view.

Results
The differences between the source segment and its matches in the translation memory are highlighted in the Lookups
pane.
Parent topic: Working with translation memories and terminology
Connecting to Trados License Server to consume a network
license seat
When connecting to the Trados License Server , you (as the client user) make a request to obtain a valid Trados GroupShare license. A license
consists of a number of product features, all of which are checked out as part of checking out the license.

About this task


The licensing computer must be turned on when users request network license seats. After closing Trados GroupShare, the license seat is returned
to the license server so other users can use it.
Timeout and lost connections - If the running client loses connection to the license server, Trados GroupShare shows the Product Activation
dialog and requires the client to restore the connection or exit the application. Moreover, if there is no user activity on Trados GroupShare for
more than 5 minutes, the license seat is automatically returned to the license pool. This is to avoid licenses being stranded on a client computer after
a crash or a power failure.
Virtual machines - If you use Trados GroupShare on a virtual machine and you want to activate it with a network license, the licensing server
grants you a license seat just as if you were connecting from a physical computer. In a Citrix/Terminal Service environment, the license server
details can be globally specified for all users in the HKEY_LOCAL_MACHINE branch of the Registry. If the users do not have write access to
HKEY_LOCAL_MACHINE, then they will not be able to change the licensing details from Trados GroupShare. If there are no predefined
settings, individual users will be able to connect to the desired license server manually. The settings will be stored in the
HKEY_CURRENT_USER branch of the Registry for each individual user.
VPN connections - Trados License Server supports accessing network licenses over private network (VPN) connections.
Multiple network segments - The network license server and the client machine do not need to be on the same network. As long as there is
direct communication between the two hosts and the client can access the network server via the port, network licensing works over multiple
network segments.

Procedure
1. Run Trados GroupShare.
2. Click HelpProduct Activation to display the Product Activation dialog.
3. Select Activate, and then select Alternative activation.
4. Select Use a License Server.
5. Enter the short computer name, the fully qualified address (less than 40 characters) or the IP address of the license server.
6. Select Connect.
7. If the license server contains multiple editions of Trados GroupShare, a page is displayed giving you the possibility to choose which one to
use. Select the license edition from the drop-down list. If the license server contains only one license edition of Trados GroupShare, go to
the next step.
8. You are redirected to the Product Activation info page which displays details of the active license. Select Continue to open Trados
GroupShare.
Parent topic: Connecting to the Trados License Manager (users)
Working with comments
Comments enable you to offer more context for the changes or revisions you apply to target segments.
Viewing comments
You can view the comments added by all users to a specific file, segment, or selection. When you open a file, segments or selections that
have comments are highlighted in yellow.
Adding comments
By adding comments, you can make suggestions to translators and reviewers and help improve the overall quality of the translation. You can
add comments only to target segments.
Modifying comments
You can modify previously added comments if you feel that they are not clear enough or if you forgot to make an important point about
something. You can also modify the severity levels of comments.
Deleting comments
You can delete comments after their corresponding issues have been solved or if the information in them is no longer relevant.
Parent topic: Reviewing translated content
Removing a network license from Trados License Manager
offline
You can remove the license that you added to a network server in several exceptional situations: to return unused licenses or to move a license
from one system to another.

Procedure
1. Open a support request in the Customer Gateway.
2. Request a permission ticket using the web form that is displayed. Include your user details and any other required license information, and
then select Submit Case. Our Licensing team will send you back a *.txt file representing the Permission Ticket.
3. Launch SafeNet License Manager.
4. Expand the Subnet Servers tree and select the hostname of the license server from where you want to remove the network license.
5. Right-click the hostname and select Revoke Licenses by Permission Ticket.
6. Browse for and select the *.txt Permission Ticket file that you received from the Licensing team.
7. Save the Revocation Ticket file and send the file back to the Licensing team.
Parent topic: Activating Trados License Manager offline
Translation statuses
Trados GroupShare shows the translation status for each project uploaded to Trados GroupShare and for each document included in the project.
These statuses are set in Trados Studio and indicate the translation progress of the project documents. The document translation status depends on
the segment statuses set in Trados Studio, in the Editor view. The project translation status depends on the translation status set in Trados Studio,
in the Projects view.

How translation statuses are set


Typically the workflow routing of a translatable item is based in part on the item's translation statuses:
1. The translator works on a document and changes the translation status for each translation segment from the Trados Studio Editor view.
2. The segment translation statuses automatically update the document translation status in the Trados Studio Files view.
3. The translator checks in the document from Trados Studio, to update the translation and the translation statuses for the Trados GroupShare
project.
4. Trados GroupShare shows the current translation status for the project and the current translation statuses for the documents in the Projects
view and the Files tab.

Project Translation Status Description


In Progress
The project needs further work and translators can download the project from the Trados
GroupShare server to complete the translation in Trados Studio.

Completed
Translators have completed the work on the project and the Project Manager has marked the
project as complete in the Trados Studio Project view.

Archived
With the work done on a project and delivered to the client, the Project Manager might want to
declutter the Trados GroupShare projects list and archive the project. The project will be hidden
from the Trados Studio workflow.

Detached
To completely remove a project from the Trados GroupShare, but still keep an offline copy, the
Project Manager can detach the project from the server.

Document Translation Status Description


Unspecified
The document has not been edited yet and all the segments in the document are Not Translated.

In Translation
At least one target segment in the document is set to Draft.

Translated
All the segments in the document are Translated in Trados Studio.

In Review
No segments are Not Translated or Draft, and at least one segment is Translated.

Translation Rejected
No segments are Not Translated, Draft or Translated, and at least one segment is Translation
Rejected.

Translation Approved
The status of all segments in the file is set to Translation Approved.

In Sign-Off
The document contains at least one Signed Off and one Translation Approved segment, and no
segment is Not Translated, Draft or Translated.
Document Translation Status Description
Sign-off Rejected
All the segments in a document are Sign-off Rejected, or at least one segment is Sign-off
Rejected when the other segments are Signed Off.

Signed Off
All the segments in the document are Signed Off. The Project Manager can set the project
translation status to Completed.

Segment Translation Status (available in Description


Studio)
Not Translated
The segment target has not been translated or edited yet.

Draft
The segment target may have been edited, but it is not yet considered fully translated; or a
translation memory match was applied to the segment, but the segment text has been edited
since then.

Translated
The translation is confirmed as complete.

Translation Rejected
The reviewer rejected the translation of the target segment.

Translation Approved
The reviewer accepted the translation of the target segment.

Sign-off Rejected
The reviewer rejected the translation of the segment during the sign-off process.

Signed Off
The reviewer approved and signed-off the translation of the segment.

Parent topic: Working with projects


Parent topic: Translation memories (TMs)
Related tasks
Step 4: Completing assignments
Step 5: Advancing assignments to the next phase
Step 2: Planning work on assignments
Step 3a: Completing assignments in Trados Studio
Step 3b: Completing assignments in the Online Editor
Step 4: Completing projects
Adding permissions to user roles
Configuring server-based TMs
Server-based translation memories (TMs) are databases used concurrently by one or several users during the translation process. To configure
server-based TMs, you must configure several components: database servers, database containers and the translation memory-itself.

About this task


To complete the configuration process of server-based TMs, go through the workflow steps:
1. Step 1 - Add database server
2. Step 2 - Add database container
3. Step 3 - Create server-based TM
Step 1: Adding database server
After you installTrados GroupShare, a default server is set. However, you can add as many servers as you need in order to create as many
server-based TMs as you need.
Step 2: Adding database container
After you install Trados GroupShare, a default container is set. Depending on your needs and the complexity of your organization, you can
add as many containers as you need. One container can support several TMs.
Step 3: Creating server-based TM
You create server-based translation memories (TMs) to ensure translations are performed consistently, sharing the same language resource.
Server-based TMs are repositories which store the translation units (TUs) that your organization's users work on over the course of time.
Translation memory advanced settings
To access the translation memory advanced settings in Trados GroupShare, go to the Resources view, select the Translation Memories tab
and select the name of the TM you want to edit. Then go to the Advanced Settings tab.
Parent topic: Translation memories (TMs)
Viewing your deactivation certificate offline for a single-user
license
Deactivation certificates are generated when you deactivate offline. You then return the deactivation certificate to the Activation Server. Until you
return the certificate, you will not be able to activate Trados GroupShare on the same machine or another machine with the same activation code.

About this task


You many need to view your deactivation certificate at a later date if you did not return the certificate to My Account or if you need to prove that
you have deactivated the product on your machine.

Procedure
1. Go to Start > GroupShare [year] > GroupShare [year] Product Activation to display the Product Activation dialog.
2. In the Product Activation dialog, select the View certificate from last deactivation link.
3. If you need to return the deactivation certificate (License) complete the following steps.
a. Switch to a computer that can access the Internet and log onto My Account.
b. Select the Licenses link.
c. Follow the prompts for returning your deactivation certificate for your Trados GroupShare using the copy of the deactivation
certificate that you have.
d. You can now activate your product using the activation code.
Parent topic: Activating single-user licenses offline
Share project via direct link
You'll probably notice the new icon next to each project title. This copies the direct project link to your clipboard and takes your colleagues to
the specific project in the Projects view.
The new option adds to the existing possibility of sharing the URL to the All Projects view, and the URL to open specific project files in the Online
Editor.

Project links for SSO configurations


For the direct link to work, make sure to use the same server name configured in the SSO authentication provider settings. If you are not sure
which Server name is set, you can find it in any email notifications.
Parent topic: Changes introduced in Trados Groupshare 2020 SR1 CU9
Inserting symbols and special characters
If your translation needs to contain symbols and special characters, you can insert them directly from the Online Editor user interface. These
include em dashes (—), en dashes (–), copyright (©) and trademark (™) symbols, as well as various types of quotation marks.

Procedure
1. Open the appropriate file in Online Editor.
2. In the target segment, click the place where you want to add a symbol or a special character.
3. On the Home tab, in the Insert characters group, select the symbol or the special character that you want to add. Select Insert Symbols to
access even more symbols.
Parent topic: Translating content
Step 6: Completing projects
When users complete all the assignments, you can mark the project as Complete. At this stage, all the project files are usually in Finalisation phase
and assigned to the user who can mark it as Complete.

Procedure
1. In Trados Studio, go to the Projects view and select the project you want to complete.
2. On the Home tab, select Mark as Complete or use the project menu.

Results
Trados GroupShare shows the status of the project as Completed.
Parent topic: Workflow for shared projects started in Trados Studio
Related concepts
Standard roles and permissions
Dependencies between permissions
Completing projects
When users complete all the assignments, you can mark the projects as Complete. At this stage, all the project files are usually in the Finalisation
phase.

Procedure
1. Go to the Projects view and select the checkboxes corresponding to the projects you want to complete.
2. Select Mark as Completed.

Results
Trados GroupShare shows the status of the project as Completed.
Parent topic: Project management
REST API endpoint of WebHooks Service
Interaction with the Trados GroupShare WebHooks Service happens through REST API calls, secured with bearer tokens (that you get using
Trados GroupShare Management Rest API login endpoint).
Parent topic: Using the Trados GroupShare WebHooks Service

GET api/webhooks/filters
Returns all WebHooks filters that a user can register with. Basically, these are the events that you'll get notification of when it happens.

Request information
URI parameters: none.
Body parameters: none.
GET /api/webhooks/filters HTTP/1.1
Host: localhost:41239
Authorization: Bearer token

Response information
A JSON array of the existing filters.
HTTP response: 200 OK
[
{
"Name": "Sdl.GroupShare.Events.V2.ProjectCreatedEvent",
"Description": "A project has been created"
},
{
"Name": "Sdl.GroupShare.Events.V2.PhaseChangeEvent",
"Description": "A files phase has been changed"
},
{
"Name": "Sdl.GroupShare.Events.V2.AssignmentEvent",
"Description": "An assignment has been changed"
},
{
"Name": "Sdl.GroupShare.Events.V2.CheckOutEvent",
"Description": "A file has been checked out"
},
{
"Name": "Sdl.GroupShare.Events.V2.CheckInEvent",
"Description": "A file has been checked in"
},
{
"Name": "*",
"Description": "Listen in on all events."
}
]

GET /api/webhooks/registrations
Returns all existing registrations to Trados GroupShare WebHooks.
URI parameters: none.
Body parameters: none.
GET /api/webhooks/registrations HTTP/1.1
Host: localhost:41239
Authorization: Bearer token

Response information
HTTP response: 200 OK
[
{
"Id": "1e41d718057743c5ab91492a7d23ea19",
"WebHookUri": "http://localhost:41240/api/phasechange?noecho",
"Secret": "GroupShareRocks",
"Description": "PhaseChange callback endpoint",
"IsPaused": false,
"Filters": [
"Sdl.GroupShare.Events.V2.PhaseChangeEvent"
],
"Headers": {},
"Properties": {}
},
{
"Id": "6614a59a71434511b399a9a3eb8bda7c",
"WebHookUri": "http://localhost:41240/api/callbacks?noecho",
"Secret": "GroupShareRocks",
"Description": "Subscription to all filters",
"IsPaused": false,
"Filters": [
"*"
],
"Headers": {},
"Properties": {}
}
]

POST /api/webhooks/registrations
Register a web hook with Trados GroupShare.

Request information
Parameter Explanation
WebHookUri The URI used by Trados GroupShare to do a POST request when the event occurs, that you subscribed to using the filter.
WebHookUri query string parameters Use the 'noecho' parameter to register a web hook without endpoint verification. If
you don't supply this parameter Trados GroupShare will do endpoint verification to check that the supplied endpoint exists
i.e. upon receiving the web hook registration request Trados GroupShare will do a GET request to the WebHookUri. If
this is desired then you need to send also an echo query string parameter and when receiving the verification request you
need to return the exact content of that parameter in plain text. Otherwise Trados GroupShare will reject webhook
registration with a message: "WebHook verification failed. Please ensure that the WebHook URI is valid and that the
endpoint is accessible."
Secret A shared secret, created as part of subscribing to events. The receiver uses this shared secret to validate that the request
comes from Trados GroupShare. The WebHook secret key parameter must be between 32 and 64 characters long.
Filters Array of filters that you are interested in subscribing. You can subscribe to multiple events at once, in this case your
callback needs to know how to handle the different callback data. Or subscribe to events one by one with different
callback endpoints.
POST /api/webhooks/registrations HTTP/1.1
Host: localhost:41239
Authorization: Bearer token
Content-Type: application/json
{
WebHookUri: "http://localhost:41240/api/phasechange?noecho",
Secret: "GroupShareRocks",
Description: "PhaseChange callback endpoint",
Filters: ["Sdl.GroupShare.Events.V2.PhaseChangeEvent"]
}

Response information
HTTP response: 201 Created
{
"Id": "1e41d718057743c5ab91492a7d23ea19",
"WebHookUri": "http://localhost:41240/api/phasechange?noecho",
"Secret": "GroupShareRocks",
"Description": "PhaseChange callback endpoint",
"IsPaused": false,
"Filters": [
"Sdl.GroupShare.Events.V2.PhaseChangeEvent"
],
"Headers": {},
"Properties": {}
}
DELETE /api/webhooks/registrations
Delete a web hook registration.

Request information
URI parameters: WebHook registration id. If no registration id is supplied in the URI all registrations will be deleted.
Body parameters: none.
DELETE /api/webhooks/registrations/{registration id} HTTP/1.1
Host: localhost:41239
Authorization: Bearer

Response information
HTTP response: 200 OK or 404 Not Found
Consulting details for translation memory lookups
You can consult the details of a translation memory (TM) lookup in the Lookups panel: the content, the match percentage, the TM it is part of, the
fields, the person who added the translation unit (TU) and the time it was added.

Procedure
1. Open the appropriate file in Online Editor.
2. Select a segment.
3. In the Lookups panel, consult the available matches. Each match (TU) consists of:
the actual text
the match percentage
the TM it is part of
the fields
the person who added the TU
the time the TU was added
Parent topic: Working with translation memories and terminology
Activating your product offline with a single-user license
If you are not able to access the Internet from the computer on which you installed Trados GroupShare or if your firewall prevents you from
performing online activation, you can modify your proxy settings or use offline activation to license Trados GroupShare.

Before you begin


To activate your product offline, you need:
To use another computer with Internet access to the RWS website
To get an activation code

Procedure
1. Go to Start > GroupShare [year] > GroupShare [year] Product Activation to display the Product Activation dialog.
2. Copy the installation ID:
a. In the Product Activation dialog, select Activate.
Trados GroupShare cannot connect to the licensing server to confirm your activation code without an Internet connection, so you will
use the alternative activation options.
b. Select the Alternative activation options link.
c. Select Offline Activation.
d. Paste the activation code in the corresponding text box. A unique installation ID is generated.
e. Copy the installation ID.
3. Get an activation certificate:
a. Log in to My Account.
b. Select the Licenses link.
c. Select the Can't activate online? - Get an Offline Activation Certificate link next to the product key you want to activate.
d. Follow the instructions to create an activation certificate for Trados GroupShare using the installation ID that you have obtained in
Step 2 above. You will also receive the activation certificate by mail.
e. Copy the activation certificate.
4. Activate Trados GroupShare:
a. In the Product Activation dialog of Trados GroupShare, enter the activation code in its corresponding box if you have not done it
already.
b. Enter your activation certificate in the Activation certificate box.
c. Select Activate.
A message is displayed indicating that the activation was successful. You can also click on the My Account link to check that your
license now appears as In Use.
Parent topic: Activating single-user licenses offline
Modifying container details
You can update a container's name and description.

Procedure
1. Go to the System Configuration view.
2. In the Containers tab, select the checkbox corresponding to the container you want to edit.
3. Select Edit.
4. Make all necessary changes.
5. Select Finish.
Parent topic: Containers
API changes for third-party developers
Continuing the initiative started in the Trados Groupshare 2020 SR1 CU8 release, we are adding more endpoints for Trados Studio and third-
party integrations.
Changes to TM Service
New REST endpoints
Parent topic: Changes introduced in Trados Groupshare 2020 SR1 CU9
Acronyms and URLs
A translation memory (TM) can handle acronyms and URLs as recognized tokens.

The effect of enabling recognition of acronyms and URLs


If you configure a TM to recognize acronyms and URLs, the TM treats each acronym or URL as a single word.
Unlike the way Trados Studio handles other recognized tokens, such as variables, Trados Studio does not substitute acronyms or URLs.
For example:
If a TU contains a URL, Trados Studio finds a match if the presented text has the same URL.
If there is no match, the TM does not translate the segment, but recognize the presence of the acronym in the source, and then adds an
annotation to the text file. When the translator opens the file in the Translation Editor, the editor displays the acronym text as a recognized
token.

Prerequisites for acronym recognition


If a TM has acronym recognition enabled, Trados Studio recognizes a term as acronym if all the following are true:
The length is between one and five characters, inclusive.
The first and last characters are uppercase letters.
The characters between the first and last letter are letters or the ampersand (&).
Enabling acronyms and URLs
You can configure Trados GroupShare to recognize acronyms and URLs for each translation memory (TM).
Parent topic: Recognized Tokens
Deleting users
When users are no longer part of your organization you can delete them.

Procedure
1. Go to the Users view and select the Users tab.
2. Select an organization and then identify the user you want to delete.
3. Select the checkbox corresponding to the user you want to delete.
4. Select Delete.
5. In the Delete User dialog, select Yes.
Parent topic: Users
Servers
Server-based TMs need to be hosted by servers, so that they are accessed by multiple users concurrently.
Servers need to be added before creating TMs.
Adding servers
You can add as many servers as you need in order to create as many server-based TMs as you need.
Modifying server details
You can modify the details of server that need adjustment.
Deleting servers
You can safely delete the servers you no longer want to host your server-based TMs.
Parent topic: Translation memories (TMs)
Specifying the MultiTerm server message language
You can specify the MultiTerm server message language for more accessibility.

Procedure
1. In the Trados GroupShare Console navigation tree, select SDL Trados GroupShare > Settings.
2. In the Settings pane, under MultiTerm Server Messages, select the language you want messages from MultiTerm Server to be written in
from the Language list.
3. In the Actions pane, select Apply Changes to save the change.
Parent topic: Trados GroupShare Console settings
Modifying your proxy settings
If you have problems connecting to the Activation Server during online activation or deactivation, you may want to modify your proxy server
settings. Alternatively, you can choose to activate or deactivate offline.

About this task


Note: This operation is not possible for activating network licenses.
Note: You can specify only the proxy server. Proxy authentication is not supported.

Procedure
1. Display the Connection Settings dialog:
If you have attempted to activate or deactivate online and the Activation Failed because you could not connect to the Activation
Server, then you are prompted to modify your connection settings. Select Yes.
In the Product Activation dialog, select the Alternative activation options link on the Activate online page. Select Connection Settings.
2. Modify the settings as needed and then test the connection. If you are still unable to connect to the Activation Server, you can choose to
activate or deactivate offline instead.
Tip: Select Refresh to reset your proxy settings.
Parent topic: Licensing
Setting up project detaching
The detachment process physically removes Completed or Archived projects from the Trados GroupShare database. Trados GroupShare makes
a package of the detached project and stores it in a set location.

Before you begin


The Detach Project option is available for users with Delete Project permission. By default, this permission is assigned to the Administrator,
Power User and Project Manager accounts.

Procedure
1. In the Trados GroupShare Console navigation tree, select SDL Trados GroupShare > Settings.
2. In the Settings pane, under Project Detaching Settings, choose the hour interval between which project detachment occurs.
Attention: Running the project detaching task can impact performance. We recommend that you set a reasonable time range which does not
affect your users. Be aware that the detaching tasks start running only during the time range you have specified. Due to server load or short
time intervals, it may happen that not all detaching tasks in the queue are triggered during the first detaching time slot which follows their
addition to the queue. Eventually, the remaining tasks will be triggered in a subsequent detaching run.
3. Specify a location for the detached projects.
Attention: Make sure that the Windows user account that Trados GroupShare services run under has the appropriate permissions to write
to your designated folder. Otherwise, the detaching will fail.
4. In the Actions pane, select Apply Changes to save the change.
Parent topic: Trados GroupShare Console settings
Log files
MultiTerm log files
MultiTerm records many of its actions in log files. It may be useful to consult these files when a process does not yield the results you expected.
For example, if an import does not process correctly, you can examine the import log file. The following table describes some of these log files.

Log File Details


Import log ( *.log) When you import a file, MultiTerm creates an import log file that
records the details of the import.
Import output file ( *.out) When you process an import with a filter applied, MultiTermcreates an
output file with the entries that do not meet the filter criteria.
Import exclusion file ( *.xcl) When you process an import which contains invalid entries, MultiTerm
creates an exclusion file with information about the invalid entries.
Export log ( *.log) When you export a termbase, MultiTerm creates an export log file that
records the details of the export.

SQL transaction log


SQL Server records all changes made to all databases in a file called a transaction log. The transaction log is used by SQL Server during
automatic recovery.
The transaction log can become very large. If it runs out of space, SQL Server cannot record further transactions and will not allow changes to the
database. You can expand the transaction log using SQL Server Management Studio.
You can use the transaction log for backups, but RWS recommends that you back up the entire database regularly to minimize the risk of data
loss.
Parent topic: Managing termbase data on the host
Updated requirements
This page contains a list of requirement updates related to Trados GroupShare 2020 SR1 CU6.

.NET Core 2.2 is no longer required


This release upgrades CP-S to use .NET Core 3.1 instead of .Net Core 2.2. This means that you can now uninstall .NET Core 2.2 from your
machine if no other applications are using it.

Apache Tomcat
Security testing results proved that using Apache Tomcat version 9.054 prevents certain security issues. We recommend upgrading to version
9.054 of Apache Tomcat if you use an earlier version.
Parent topic: Changes introduced in Trados GroupShare 2020 SR1 CU6
Viewing information about the structure of a file
This information indicates where each segment is located in the structure of the source file; for example, in a paragraph or in a header or footer.

Procedure
1. Open the appropriate file in Online Editor.
2. Do one of the following:
To view the document structure in a column on the right side of the workspace, on the View tab, in the Navigation group, select
Show Document Structure. Then, in the newly displayed column, select the cell corresponding to the segment about which you want
to view information.
The available information about the location of the segment and about the meaning of the code is displayed in the Document Structure
Information box.

To view the document structure in a separate panel, on the right side of the screen, select Show Document Structure Information
Panel .
Tip: If you choose to view information about the document structure in this way, you can also select Detach Panel
to open the panel in a separate window and move it to another part of your
screen or to another screen.
Parent topic: Navigating the Online Editor user interface
Verifying translated content
You can verify translations in Online Editor to check for errors and inconsistencies. Verification checks the target segment against the source
segment and reports if there are missing tags or inconsistent QA (Quality Assessment) items.
The verification can run automatically when confirming a translation or manually, during translation.
This feature is available for Online Editor Advanced.
Running verification during translation
When you verify your translated segments, the system compares the source and the target to find missing or incorrect tags.
Checking verification results
In the Verification panel there are two options. You can filter the verification results by Severity or by Message type.
Parent topic: Working with Online Editor
Adding servers
You can add as many servers as you need in order to create as many server-based TMs as you need.

About this task


You must add servers to Trados GroupShare before creating TMs.

Procedure
1. Go to the System Configuration view.
2. In the Servers tab, select New Server.
3. In the Create Server dialog:
a. Choose a location for your server within the organization.
b. Enter a server name in the Name field.
c. Optionally, provide a description for your server.
d. Choose an authentication method.
4. Select Finish.
Parent topic: Servers
Removing roles from users
When you do not want users to fulfill a role, you can remove the user from that role.

Procedure
1. Go to the Users view and select the Permissions tab.
2. Select the user's home organization (the organization in which the user was created).
3. Identify the user whose role you want to remove.
4. Select the checkbox corresponding to the user's name.
5. Select Remove Users.
Parent topic: User roles
Related concepts
Standard roles
Securing your Trados GroupShare webserver
You can use HTTP Strict Transport Security (HSTS) policy to protect against man-in-the-middle attacks, such as protocol downgrade attacks
and cookie hijacking.

About this task


To enable HSTS and secure cookies:

Procedure
1. Navigate to C:\ProgramData\Package Cache\SDL\SDLTradosGroupShare2020\
2. Locate the EnableHSTS.ps1 and SecureCookie.ps1 powershell scripts and run them as administrator.
Server security configuration recommendations
Follow the steps covered in some or all of the following sections to make sure your Trados GroupShare server is as secure as possible.
Each section covers a specific area.
Parent topic: Installing Trados GroupShare
Getting an activation code
An activation code is used to activate your copy of Trados GroupShare.

About this task


When you activate your product, you use the Product Activation dialog, which prompts you to enter the activation code.

Procedure
1. Log onto My Account.
2. Select Products & Plans > Licenses.
3. Find the activation code for the product you have purchased in the list and copy it.
Parent topic: Activating single-user licenses online (activation code)
Reviewing translated content
You can review translations in Online Editor by managing comments, tracking changes, and using other advanced options.
Reviewing content increases the quality of your translated content.
Revision modes
Whether you are reviewing a translation or integrating reviews in your translation, there are multiple ways in which you can view the revisions
made with tracked changes.
Reviewing content with Track Changes
You can track all the changes you make to a text, which is useful especially when reviewing translations.
Moving from one revision to another
When you receive a reviewed translation, you can move from one revision to another to make sure that you cover all the revisions before
submitting the final translation.
Accepting revisions
After you receive a reviewed file, you can directly accept the revisions you agree with.
Modifying revisions
You can modify your revisions if they are no longer relevant. To modify other users' revisions, you must enable Track Changes first.
Rejecting revisions
After you receive a reviewed file, you can directly reject the revisions you do not agree with.
Revision color markup
When multiple users review files collaboratively, the system automatically assigns a color to individual users, so that they can differentiate
their comments from the ones introduced by other users.
Working with comments
Comments enable you to offer more context for the changes or revisions you apply to target segments.
Parent topic: Working with Online Editor
Configuring organizations and users for enterprise
GroupShare enables you to set up an appropriate schematic at enterprise level.

Procedure
1. Create administrator users at Root Organization level.
2. Add servers at Root Organization level.
3. Create business area organizations.
4. Add business area users.
5. Create TM containers at business area organization.
6. Create an organization for each business team.
7. Assign roles to users.
Note: If you are using Trados GroupShare Cloud, you cannot edit roles and permissions.
Parent topic: Organizations and their components
Consulting cloud project details
If you have a file open in the browser, you can easily check what project it belongs to and what its location is. This is particularly useful when you
work on multiple files at the same time.

Procedure
1. Open the appropriate file in Online Editor.
2. On the header, in the top right-hand corner, hover over the information icon. Check the project name and its location.
Parent topic: Navigating the Online Editor user interface
Trados GroupShare general conrefs
Full name of the product: Trados GroupShare
Short name of the product: Trados GroupShare
Full name and current version of the product: Trados GroupShare 2020 SR1
Short name and current version of the product: Trados GroupShare 2020 SR1
Standalone current version: 2020 SR2
Full name and previous version of the product: SDL Studio GroupShare 2019 and SDL Studio GroupShare 2017
Short name and previous version of the product: Studio GroupShare 2019 and Studio GroupShare 2017
Standalone previous version: 2019 and 2017
Full name of the GroupShare Console: Trados GroupShare Console
Full name and current version of the SDL GroupShare Console: Trados GroupShare Console 2020 SR1
Short name and current version of the SDL GroupShare Console: Trados GroupShare Console 2020 SR1
Short name of the Console: Trados GroupShare Console
Full Name of the MultiTerm Administrator: MultiTerm Administrator
Short name of the MultiTerm Administrator: MultiTerm Administrator
MultiTerm Online: MultiTerm Online
MultiTerm Online short: - MultiTerm Online
MultiTerm Server component: MultiTerm Server
TM Server componentTM Server
Project Server component- Project Server
.net Framework version 4.8
Trados Studio: Trados Studio
Client account for licenses My account
Client account for licenses with linkMy account

Help links
GroupShare Online Help link: Trados GroupShare 2020 SR1 Help
GroupShare Installation Guide: Trados GroupShare 2020 SR1 Installation Guide
GroupShare Release Notes: Trados GroupShare 2020 SR1 Release Notes
Cumulative Updates article: Trados GroupShare 2020 SR1 Cumulative Updates

File paths
SDLTradosGroupShare2020
%Programdata%\Package Cache\SDL\SDLTradosGroupShare2020\SQLScripts\SQLServer\
C:\ProgramData\Package Cache\SDL\SDLTradosGroupShare2020
Step 1: Publishing projects to Trados GroupShare
Publish a Trados Studio project to a Trados GroupShare server so that multiple users can work at the same time to complete translation tasks.
Parent topic: Workflow for shared projects started in Trados Studio

Publishing new projects


If you haven't created your project in Trados Studio yet, but you want to share it to Trados GroupShare, you can specify to have your project
published automatically to Trados GroupShare immediately after it is created.

Before you begin


If you want to share termbases and translation memories, they must be server-based.
If you want to share AutoSuggest dictionaries, they must be located on a shared public location and have an UNC path.

Procedure
1. In Trados Studio, go to the Projects view.
2. On the Home tab, select New Project and go through the pages of the project creation wizard.
3. On the One Step page, add project files and specify the available settings and:
If no other customization or review is needed, go to step 12.
If further customization or review is needed, walk through the steps below.
4. On the General page, specify the available settings: source editing, tokenization for Asian languages, customers.
5. Select Next.
6. On the Languages page, select the source and target languages for your project.
7. Select Next.
8. On the Translation Memory and Automated Translation page, configure any translation resources you want to include in your project.
Remember: If you want your Trados GroupShare users to access the same translation memory resources, you must create or use server-
based translation memories.
9. Select Next.
10. On the Termbases page, configure any termbases you want to include in your project.
Remember: If you want your Trados GroupShare users to access the same translation memory resources, you must create or use server-
based translation memories.
11. Select Next.
12. On the Trados GroupShare page, select Publish on a server and specify: server information and a location for your project in the
organizations tree.
a. Select the Preparation tab.
b. Under Due date, choose an end date and time for the assignments in this stage.
c. Optionally, under Available Assignees, type a user name, especially if you have a large user list and you want to retrieve users fast.
d. Under All Users, select the user you want to add to the project phase, and select Add. Repeat this for as many users as you need for
the project phase.
Tip: RWS recommends that you assign users to phases at this point. If, however, you decide to skip this step or, if changes occur
after you publish the project to , you can assign or unassign users from phases at a later date.
e. Repeat for the rest of the phases: Translation, Review and Finalisation.
13. On the Perfect Match page, add or remove files if necessary, and choose whether you want to apply Perfect Match to your translation.
14. Select Next.
15. On the Batch Tasks page, review the settings for the selected task sequence.
If the project has a server-based TM created in Trados GroupShare 2017 SR1 CU9 or later, the (Beta) Prepare with GroupShare
sequence is available.
This sequence contains the GroupShare Analyze and Translate batch task that performs a server-side analysis and pre-translation of your
project files. This batch task is faster than preparing the project in Trados Studio.
You can apply the batch task and task sequence to projects that use server-based TMs and are published to Trados GroupShare.
16. Select Next.
17. On the Summary page, select Finish.

Results
When the project is published, Trados GroupShare displays the new project in the Projects view.
Trados GroupShare then analyzes the permissions of the users who are members of Trados GroupShare roles on the server, and makes the
project files visible to the appropriate users in Trados Studio. Permissions to access projects are managed from the Project Server.

Publishing existing projects


If you already created a project in Trados Studio, you can publish it manually to Trados GroupShare anytime.

Before you begin


If you want to share termbases and translation memories, they must be server-based.
If you want to share AutoSuggest dictionaries, they must be located on a shared public location and have an UNC path.

Procedure
1. In Trados Studio, go to the Projects view and double-click a project to open it.
2. On the Home tab, in the GroupShare layout, select Publish Project.
3. In the Publish Project dialog, choose a server:
If the server is in the list, select a server from the list.
If the server is not in the list, select Servers and, in the Servers dialog, select Add. In the Add GroupShare Server dialog, type the
server address, enter your authentication details, and select OK.
4. In the Publish Project dialog, browse a project location on the Trados GroupShare server, select OK and, then, select Finish.

Results
When the project is published, Trados GroupShare displays the new project in the Projects view.
Trados GroupSharethen analyzes the permissions of the users who are members of Trados GroupShare roles on the server, and makes the project
files visible to the appropriate users in Trados Studio. Permissions to access projects are managed from the Project Server.

Running the GroupShare Analyze and Translate batch task


After the project is published you can run a batch task to analyze and pre-translate the project files on the Trados GroupShare server.

Procedure
1. In Trados Studio, select the published project.
2. On the Trados Studio ribbon, go to Home > Batch Tasks > GroupShare Analyze and Translate
3. Follow the wizard and select the language pairs that you want the batch task to apply to.
Third-party authorization
Starting with GroupShare 2020 CU6 we support the automatic assignment of user roles in SSO login flows. As a prerequisite, this requires setting
up a group or role membership in the identity provider. Both SAML tokens and JWT clains are supported with automatic role assignments.
Parent topic: Changes introduced in Trados GroupShare 2020 SR1 CU6
Applying translations
You can apply the results retrieved from the TMs (translation memories) included in your project to the target segment. Context matches and
100% matches are applied automatically to target segments when you select them.

About this task


If your TM contains multiple translations for the same segment, you can choose which one to apply.

Procedure
1. Open the appropriate file in Online Editor.
2. Select the target segment to which you want to apply an existing translation. The available translations are automatically displayed in the
Lookups panel.
3. Do one of the following:
Select the segment you want to edit. From the Lookups panel, double-click the translation you want to apply or press Ctrl+Shift+A.
Note that fragment matches are highlighted in yellow.
Tip: Suggestions can include full matches, fragment matches or terms. Fragment matches are marked with a vertical yellow line, while
terms are marked with a vertical red line.
Tip: Alternatively, you can press Ctrl+<digit>, where <digit> represents the order of that particular translation in the Lookups
panel. For example, press Ctrl+1 to apply the first translation from the Lookups panel or Ctrl+9 to apply the ninth one.
Edit the target segment. When AutoSuggest detects already translated content, a box is displayed below the segment you are editing.
Use the key arrows to navigate the suggestions. Choose a suggestion and either press Enter or double-click it.

Results
The translation is applied to the target segment. Until you confirm it, the target segment has the Draft status.
Parent topic: Working with translation memories and terminology
You can access a resource although you do not have the
permission
Symptom
You can see or write termbase data although your role was not granted access rights for this.

Probable Cause Solution

You are in more than one Trados GroupShare roles. For each termbase, you get the sum of access rights for all the roles that
you belong to. Make sure that you are not also member of another role
that allows unrequired access.

Entries are classified by entry classes and you have access to more Make sure that your role provides Entry level access only to the
entry classes than required. required entry classes.

You have access to an input model which allows you to edit fields you Make sure that your role has the must use an input model restriction.
should not have access to.

Parent topic: Problems and solutions


Moving from one revision to another
When you receive a reviewed translation, you can move from one revision to another to make sure that you cover all the revisions before
submitting the final translation.

Procedure
1. Open the appropriate file in Online Editor.
2. On the Review tab, do one of the following:
To move to the next segment containing revisions, select Next.
To move to the previous segment containing revisions, select Previous.
Tip: If you select Next and Previous without any segments being displayed, it means that the file you are working on no longer contains
revisions. If your asset still contains revisions, a small dot is displayed next to the Revisions Panel button on the right side of the screen:

Parent topic: Reviewing translated content


Activating your product online with a single-user license
By default, Trados GroupShare will automatically try to perform an online activation through the Internet. If, for some reason, it cannot access the
Activation Server, it will prompt you to perform an offline activation.

Before you begin


To activate your product online, you need:
Internet access
The product activation code

Procedure
1. Go to Start GroupShare [year] GroupShare [year] Product Activation to display the Product Activation dialog.
2. Select Activate.
3. On the Online Activation page, enter your activation code in the Activation code box. Your can get your activation code by accessing your
My Account > My Licenses.
4. Select Activate.
A message is displayed indicating that the activation was successful.
Parent topic: Activating single-user licenses online (activation code)
Specifying project server notification settings
The project server notification settings are used to send email notifications to Trados GroupShare users.

Procedure
1. In the Trados GroupShare Console navigation tree, select SDL Trados GroupShare > Settings.
2. In the Settings pane, under Project Server Notification Settings, provide the necessary credentials:
a. In the Email Sender Display Name field, enter the name that Trados GroupShare will show before the email address in the From
field, for example, GroupShare Notification.
b. In the Email Sender Address field, enter the email address that Trados GroupShare will use for sending out notification emails, for
example, [email protected].
Tip: RWS recommends that you use a valid email address for sending out project notification emails. Add a non-functional email
address only if you are not expecting replies from the users who will receive the notification emails.
c. In the SMTP Host field, enter the address of your SMTP host which will be used for sending notification emails.
d. In the Port (default 25) field, enter the SMTP port of the email server (integers only).
e. In the Credentials (user) and the Credentials (password) fields , enter the user and password of your SMTP host. Credentials are
only required if your host requires authentication.
f. Select the Use SSL checkbox if the SMTP server requires the SSL/TLS channel.
g. In the Email Templates Location field, specify the location where your custom email templates are stored. Make sure that the
Application Service has at least Read rights to this folder.
h. Select the Include "Open in Studio" link checkbox, so that the email notification you send translators and reviewers contains a direct
link to their assigned task. The link opens the assignment in Trados Studio.
i. Select the Include "Edit Online" link checkbox, so that the email notification you send translators and reviewers contains a direct link
to their assigned task. The link opens the assignment in Online Editor.
j. Test the email notification system by filling in an email address and selecting Send Test Email.
3. In the Actions pane, select Apply Changes to save the change.
4. After changing the server notification settings, restart the Trados GroupShare services. In the Trados GroupShare Console navigation tree,
select SDL Trados GroupShare > Services, and then, in the Actions pane, select Restart Services .
Parent topic: Trados GroupShare Console settings
User profile pictures
Starting with this release, Trados GroupShare accounts support custom profile pictures. These offer an alternative to the default avatars that show
your initials on a colored background.
The profile pictures appear in various places in the Trados GroupShare views, to illustrate the users assigned to work on projects or tasks.
To update your profile picture, go to Manage Account > Profile Information. If you are a project manager, you can also update profile pictures for
other users in your account from the Users view.
Parent topic: Changes introduced in Trados GroupShare 2020 SR1
Step 2: Planning work on assignments
To make it easy to manage a project during its lifetime, you should assign engineers, translators and reviewers to translation phases for each
project file. Each of the users will be notified when the file reaches the phase they are assigned to by email.

About this task


Starting with SDL Trados Studio 2017 SR1, the project template, which you create in Trados GroupShare, can include file assignments. This
means that you can decide which users work on your files, for each file phase, when you actually create the template.

Procedure
1. Go to the Projects view and select a project to open it.
2. In the project planning board, set to the Kanban-style view, select one or more files.
3. Select Planning for <n> files.
4. For each phase, in the Planning for <file> window:
a. Assign the users that work on the files from the Assigned users list.
b. Specify a due date in the Delivery at field.
Note: If users were assigned to work on file phases when the project template was created, you can consult them at this stage. You can
adjust the list of assigned users by deleting currently assigned ones, or by adding new ones.
5. Select Save.
6. When work is done on a file in a phase, drag the file to the next phase or to any of the other three phases with no restriction.
The assigned user receives a notification email regarding the task assigned to them and the due date for it.

What to do next
Once all assigned work is planned for, the assigned users can start the actual work either in Trados Studio or in Online Editor.
Assigned users receive an email with two direct links to the assigned file, one which opens the file in Trados Studio, and another (a file-name link)
which opens the file in Online Editor. Depending on your available configuration, you can perform either Step 3a or Step 3b.
Parent topic: Workflow for shared projects started in Trados GroupShare
Related concepts
File assignment security
File assignment notifications
Standard roles and permissions
Dependencies between permissions
Translation statuses
Deleting server-based TMs
You can safely delete server-based TMs that are out-of-date or no longer relevant.

Procedure
1. Go to the Resources view.
2. In the Translation Memories tab, select the checkboxes corresponding to the TMs you want to delete.
3. Select Delete.
4. In the confirmation message, select Yes.
Parent topic: Translation memories (TMs)
SDL Trados GroupShare concept conrefs
Enter a short description of your concept here (optional).
Users have access to the organization's resources depending on the permission associated to their role. Resources include:
Translation memories (TMs)
Termbases
Language resource templates
Field templates
Project templates

About Perfect Match


A Perfect Match is a form of context match that compares updated source files to a corresponding set of existing bilingual files rather than to a
translation memory (TM). Segment matches, known as Perfect Matches, are checked for context, that is, the surrounding entries are checked to
ensure that they are the same.
If your existing bilingual file was segmented differently to the current file or had merged segments, Perfect Match can dynamically merge up to three
consecutive segments in your current file to improve your match results. The translations are then extracted from the existing bilingual files and
transferred to the updated source files.
Because the Perfect Match segment matching process includes a check for context and segmentation, Perfect Match units typically need no further
translation or editing during translation.
Example of a segmentation rule
The following rule is used as an exception to the segmentation rule that defines a segment demarcated by a period (full stop).
Because it is used as an exception, the TM will treat text that matches this pattern as matching a section of text that does not contain a segment
break, even if the text also matches the more general pattern that defines a segment break.
This following rule matches any text that contains a period (perhaps followed by other closing punctuation), followed by a space and then a
lowercase letter.

Before break
\.+[\p{Pe}\p{Pf}\p{Po}"]*
Close, final and other punctuation, are defined Unicode categories for the following codes:
\p{Pe} specifies close punctuation.

\p{Pf} specifies final quote punctuation.

\p{Po} specifies other punctuation.

After break
\s\p{Ll}

This regular expression matches a space followed by a lowercase letter.


For more information about Unicode categories, see, http://msdn.microsoft.com/en-us/library/system.globalization.unicodecategory.aspx.
Parent topic: Segmentation rules
Related tasks
Specifying segmentation rules
Mixed Online Editor licensing options
Online Editor can be accessed under the form of a Basic edition, of an Advanced edition, or a combination of both (a mixed edition).
The mixed Online Editor license (Basic and Advanced) can be used starting from Trados GroupShare 2020 CU2. The previous product version,
Trados GroupShare 2020 CU1, offered Online Editor, as either Basic or Advanced.
The Basic edition has some limitations, but both editions allow you to open a file for translation or review in Trados GroupShare. If you purchase a
mixed license, you can switch between the Basic or the Advanced mode when opening files.
Trados GroupShare offers you the possibility of purchasing licenses with mixed Online Editor entitlements as follows:
Basic only
Advanced only
Basic and Advanced (starting from Trados GroupShare 2020 CU2)
The Online Editor trial version uses the Advanced edition.
Parent topic: Changes introduced in SDL Trados GroupShare 2020
New solution for reporting and dashboard
We've replaced the reporting engine with one built on the Logi Analytics platform.
All the reports on the Trados GroupShare Dashboard are now embedded Logi Reports.
The new reporting service is included in the installer and configured automatically. It uses the same port, user and permissions as the Web service.
Parent topic: Changes introduced in SDL Trados GroupShare 2020
TM system fields
You can use these field names in the filter description when exporting translation units (TUs).

Field name Description Field type


chd Date-time
The date/time the TU was last changed.

chu String
The user who last changed the TU.

crd Date-time
The date/time the TU was created.

cru String
The name of the user who created the TU.

sourcetagcount Integer
The number of tags in the source segment.

sourceplainlength Integer
The length of the plain source text of the TU, in
characters.

src String
The source text of the TU.

targettagcount Integer
The number of tags in the target segment.

targetplainlength Integer
The length of the plain source text of the TU, in
characters.

trg String
The target text of the TU.

usc Integer
The number of times the TU has been used so far.

usd Date-time
The date/time the TU was last used.

usu String
The name of the user that last used the TU.

Parent topic: Exporting TUs from server-based TMs


Defining variables
You can define the list of variables translation memories (TMs) take into consideration. Each language pair can have a list of variables.
Parent topic: Variables

Define variable list when creating language resources


Procedure
1. Go to the Resources view.
2. In the Language Resource Template tab, select New Language Resource Template.
3. In the Create Language Resource Template dialog, select General Properties.
4. Select Language Resources.
5. On the Language Resources page, select a source language.
6. Click anywhere on the white space.
7. Select .
8. On theCreate Language Resource Template > [source language name] page, select Variables.
9. Type in a variable and click anywhere on the white space.
10. Repeat step 9 to add more variables.
11. Select Finish.

Define variable list when editing language resources


Procedure
1. Go to the Resources view.
2. In the Language Resource Templates tab, select the checkbox corresponding to the language resource template of choice.
3. Select Edit.
4. In the [language resource template name], select Language Resources.
5. Identify the language for which you want to add variables and select .
6. On the [language resource template name > source language name] page, select Variables.
7. Type in or edit a variable.
8. Click anywhere on the white space.
9. Select Finish.
Concept conrefs for Language Cloud
A library topic for any concept-specific elements that you might want to conref.

Names of components or other non-variables


Content Description
RWS Language Cloud Generic name for the platform hosting cloud offers.
Trados Customer Portal The name of the component currently known as Client/Customer
Portal.
Trados Customer Portal The name of the component currently known as Client/Cusomter
Portal, along with the name of the company. I took out the company
name.
a Trados Customer Portal + account/subscription/[noun]
Trados Enterprise The name of Language Cloud Translation Management / Trados
Enterprise.
a Trados Enterprise + account/subscription/[noun]
Trados Team The name of Trados Live Team.
a Trados Team + account/subscription/[noun]
Trados Studio cloud capabilities The name of Trados Live Essential.
a Trados Studio cloud capabilities + account/subscription/[noun]
Trados Terminology The name of Trados Live Terminology.
a Trados Terminology + account/subscription/[noun]
RWS ID The name of RWS ID.
RWS Account The name of RWS Account.
RWS ID The name of RWS ID as UI control.
RWS Account The name of RWS Account as UI control.
Cloud-based Terminology The name of Cloud-based Terminology in Studio, as it appears in the
UI.
Studio The short name of the product currently known as Trados Studio.
Trados Studio A longer (but still not long) name of the product currently known as
Trados Studio.
a Trados Studio + account/subscription/[noun]
Trados Studio The name of the product currently known as Trados Studio.
Trados Studio 2021 The name of the most recent supported version of Trados Studio.
MultiTerm The short name of the product currently known as MultiTerm.
MultiTerm The name of the product currently known as MultiTerm.
Trados GroupShare
WorldServer
TMS
Managed Translation
Machine Translation The name of the product formerly known as BeGlobal.
Tridion Sites
Tridion Docs
Tridion Sites to Language Cloud service integration
Tridion Docs to Language Cloud service integration
*.sdlxliff
SDLXLIFF
Content Description
*.sdltm
SDLTM
*.sdlftsettings
SDL TMS Classic
SDL TMS Classic
Linked Machine Translation Account
Open in Studio
Open in Online Editor
Open Task in Language Cloud
Download Cloud Projects
Preparing & uploading project to Language Cloud
Download SDLXLIFF
Upload SDLXLIFF

Conreffed paragraphs
first end-to-end intelligent translation solution powered by Hai, a Linguistic AI TM technology. RWS Language Cloud provides a single,
cloud-based solution for companies to access machine intelligence and human expertise, to optimize their translation process, for greater
control, visibility, and scalability across their global content supply chain. Complete content integration
Intelligent translation management
Smart dashboard and notifications
Sophisticated neural MT
Translator productivity (studio integration)
Enterprise-level scalability and security
Increase productivity by using Hai, our linguistic AI, to automatically analyze content.
Review processes securely in the cloud, with complete peace of mind.
Leverage industry-leading neural machine translation trained to your content for optimum quality.
Connectors + Online editor
Ability to manage your various vendors and understand project status.
persona-based user experience (heatmaps for project managers + connectors for content requesters.
The operations detailed in this section can be performed by administrators and lead project managers:
Administrators are users who are part of the Administrator default group located in the Root folder. Administrators have access everywhere
(any folder).
Lead project managers are users who are part of the Lead Project Manager group in a customer folder. Lead project managers have the
same permissions (can do the same things) as administrators, but only at customer folder level. Administrators create Lead Project Manager
groups and add users to these groups for each customer where this is necessary.
The operations detailed in this section can be performed by administrators, lead project managers, project managers:
Administrators are users who are part of the Administrator default group located in the Root folder. Administrators have access everywhere
(any folder).
Lead project managers are users who are part of the Lead Project Manager group in a customer folder. Lead project managers have the
same permissions (can do the same things) as administrators, but only at customer folder level. Administrators create Lead Project Manager
groups and add users to these groups for each customer where this is necessary.
Project managers are users who are part of a Project Manager group (the default group located in the Root folder or a customer-specific
group located in a customer folder). Administrators can add project manager users at Root folder level and customer-folder level, while lead
project managers can add project manager users at customer-folder level (and customer child folders).

Links to QSGs
Customer Requester QSG in PDF format
Customer Reviewer QSG in PDF format
Legal notice
Copyright and trademark information relating to this product release.
Copyright © 2000–2023 RWS Holdings plc. All rights reserved.
This legal notice applies to RWS Holdings plc and its subsidiaries and affiliates. All intellectual property rights contained herein are the sole and
exclusive rights of RWS. All references to RWS shall mean RWS Holdings plc and its subsidiaries and affiliates details of which can be obtained
upon written request.
All rights reserved. Unless explicitly stated otherwise, all intellectual property rights including those in copyright in the content of this website and
documentation are owned by or controlled for these purposes by RWS. Except as otherwise expressly permitted hereunder or in accordance with
copyright legislation, the content of this site, and/or the documentation may not be copied, reproduced, republished, downloaded, posted,
broadcast or transmitted in any way without the express written permission of RWS.
Trados GroupShare is a registered trademark of RWS. All other trademarks are the property of their respective owners. The names of other
companies and products mentioned herein may be the trademarks of their respective owners. Unless stated to the contrary, no association with
any other company or product is intended or should be inferred.
This product may include open source or similar third-party software, details of which can be found by clicking the following link:
Acknowledgments.
Although RWS takes all reasonable measures to provide accurate and comprehensive information about the product, this information is provided
as-is and all warranties, conditions or other terms concerning the documentation whether express or implied by statute, common law or otherwise
(including those relating to satisfactory quality and fitness for purposes) are excluded to the extent permitted by law.
To the maximum extent permitted by law, RWS shall not be liable in contract, tort (including negligence or breach of statutory duty) or otherwise
for any loss, injury, claim liability or damage of any kind or arising out of, or in connection with, the use or performance of the Software
Documentation even if such losses and/or damages were foreseen, foreseeable or known, for: (a) loss of, damage to or corruption of data, (b)
economic loss, (c) loss of actual or anticipated profits, (d) loss of business revenue, (e) loss of anticipated savings, (f) loss of business, (g) loss of
opportunity, (h) loss of goodwill, or (i) any indirect, special, incidental or consequential loss or damage howsoever caused.
All Third Party Software is licensed "as is." RWS makes no warranties, express, implied, statutory or otherwise with respect to the Third Party
Software, and expressly disclaims all implied warranties of non-infringement, merchantability and fitness for a particular purpose. In no event will
Licensor be liable for any damages, including loss of data, lost profits, cost of cover or other special, incidental, consequential, direct,
actual, general or indirect damages arising from the use of the Third Party Software or accompanying materials, however caused and
on any theory of liability. This limitation will apply even if Licensor has been advised of the possibility of such damage. The parties
acknowledge that this is a reasonable allocation of risk.
Information in this documentation, including any URL and other Internet website references, is subject to change without notice. Without limiting
the rights under copyright, no part of this may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any
means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of RWS.
Parent topic: Welcome to the Trados GroupShare 2020 SR1 documentation
Step 3: Updating file phase
Users can access the files assigned to them for a specific phase. When you assign files to a project phase, you inform the assigned users what their
translation tasks are.

About this task


When the allocated files reach the phase where the users are assigned to work on them, Trados GroupShare automatically sends the assigned
users a phase change notification email.

Procedure
1. In Trados Studio, go to the Projects view, double-click a project published on Trados GroupShare to open it.
2. In the Files view, select one or more files.
3. On the Home tab, expand Change Phase and assign project files to one of the four available project phases.

Results
Trados GroupShare displays the current phase of each file in the Projects view when you open a project. This information is visible to all the users
who have permission to see the project files.
Parent topic: Workflow for shared projects started in Trados Studio
Related concepts
Standard roles and permissions
Dependencies between permissions
File assignment security
Printing project level reports
You can print the reports irrespective of the project's file phases

About this task


Reports are available only for projects created in Trados GroupShare.

Procedure
1. Go to the Projects view and select a project to open it.
2. In the [project name] tab, select .
3. Consult the report details.
4. Optionally, go to the table columns and:
Sort the data in ascending or descending order.
Customize the columns that are displayed.
Tip: The filters you apply at column level are kept when printing the report.
5. Select Print.
Parent topic: Project-level reports and background tasks
Detaching completed projects
Trados GroupShare projects can be fully removed from the system. Unlike archiving, detaching removes all traces of the project from the server.

Before you begin


Users who detach projects need the Delete Project permission in Trados GroupShare. The Delete Project permission is assigned by default to
the Administrator, Power User and Project Management roles.

About this task


The project is packaged and saved to the location set in Trados GroupShare Console.

Procedure
1. In the Projects view select the checkboxes corresponding to the Completed or Archived projects you want to detach.
2. Select Detach.
3. In the prompt, choose if you want to delete the project's translation memories or not. A background task is scheduled to run the process.
Note: The detached project cannot be restored from the web interface.
Parent topic: Project archiving
Restoring completed projects
You can restore projects from a Completed status to an In progress status if there is still some work left to do.

Procedure
1. In the Projects view, select the checkboxes corresponding to the Completed projects you want to restore.
2. Select Move to In Progress.

Results
The project is brought back to the In progress status and its files appear in the Preparation phase of the project tab.
Parent topic: Project management
Problems and solutions
You cannot access a resource although you have the permissions
You can access a resource although you do not have the permission
You cannot add database server (authentication issues)
You cannot specify a windows user in add user
Defined field is not in project TM
Main TMs are not updated
At the end of a project Trados GroupShare updates the main translation memories (TMs) from translation units (TUs) in the project TMs.
Unable to discover an endpoint supporting windows authentication for service identity.svc
Recognized Tokens
A recognized token is a short piece of text, in a defined set of formats, that a translation memory (TM) treats as a single word.
Tokens that can be recognized are:
Dates
Times
Numbers (in numerals)
Measurements
Acronyms and URLs
Variables
Inline tags
For example, if dates are enabled as recognized tokens in a TM, the TM recognizes Monday 1 January, 1900 as one word.

Where to enable or disable the recognition of tokens


You enable or disable the recognition of tokens by editing the general properties of a TM.
These settings affect how the TM analyzes the source text into tokens. The recognized tokens settings specify text patterns that the TM recognizes
as tokens, and also specify the type of token.
For some types of recognized token, you can provide a rule that the TM uses to translate occurrences of the token in the source text. These rules
are auto-localization rules and are described below.

How the TM uses the recognition of tokens setting


When a translation unit (TU) is added to a TM, the TM scans the TU for recognized tokens. For example, if dates are enabled, it analyses the TU
for dates. If recognition of this token is not enabled for the TM, the TM does not recognize the tokens. If, for example, you later enable date
recognition, the TM does not immediately analyze existing TUs for dates - you need to re-index the TM. When you do re-index the TM, the TM
scans existing TUs for currently recognized tokens.
When new text is presented for a translation, the TM segments the text and then checks for recognized tokens, that is, it checks for recognized
tokens only within a segment.

How recognized tokens are handled in translation


For some recognized tokens, the suggested target is the same as the source:
Inline tags
Acronyms
URLs
Variables
For the remaining recognized tokens, the translation is formed by automatically localizing the source. These tokens are:
Dates
Times
Numbers (in numerals)
Measurements

Where to change automatic localization rules for recognized tokens


The automatic localization rules are specified in the project settings.

Where to change settings related to recognized tokens


When a TM analyzes source text, it uses the recognize tokens settings. If the TM recognizes a token within a matched segment, it translates the
whole segment.
If the token is not part of a matching segment, then it provides the suggested translation (for example, provides a date in the target language).
You can specify these settings under the generic language resources settings, and also directly to any TM, under TM settings. As you would
expect, any settings that are directly specified for a TM override the generic settings.
Time and measurement tokens
Dates, times, numbers and measurements are examples of tokens.
Acronyms and URLs
A translation memory (TM) can handle acronyms and URLs as recognized tokens.
Variables
A variable is a word or phrase that the translation memory (TM) recognizes in the source text. The TM copies the variable to the target text.
Because variables are identical between source and target text, they are useful for special terms such as product names.
Parent topic: TM language processing rules and recognized tokens
Verify translations in Online Editor
You can now use the Online Editor in Trados GroupShare to perform QA checks as part of the translation and review process. This feature is
available with Online Editor - Advanced edition.
Parent topic: Changes introduced in SDL Trados GroupShare 2020
File assignment notifications
Trados GroupShare sends out email notifications to the users assigned to work on the Trados GroupShare project files.
Email notifications keep the users involved in a Trados GroupShare project up-to-date on the status of current assignments.Trados GroupShare
sends the notifications to the email address that you specify in the User Account Details window when you create or edit a Trados GroupShare
user.
File assignment notifications sent by email:
Inform users they are added/removed from the list of users assigned to work on the files in the current phase.
Inform users that other users are added/removed from the list of users working on the files in the current phase.
Inform users they can start/stop working on the files in the current phase.
Give users direct access to their project assignments via links.
Eliminate the project manager's task to inform users about assignments manually.
Eliminate the user's task to manually connect to the relevant project.
Note: Users without the View Other Users permission (by default, members of the External Translator role) see the other users added/removed
from the list of users assigned to work on the same files as Anonymous users.

New assignment/Phase change notification email for Trados Studio


When you change the phase for one or more files or when you receive a new assignment, Trados GroupShare sends out a Files Ready For You
email message. This email notifies the users assigned to work on the files in the current phase that they can start working on the files.
Users with Check Out My Files permissions can now check out the files from the Trados GroupShare server and start working on them in Trados
Studio. After completing the assignment and checking in the files, users with Change Current Phase permission can advance the files to the next
project phase. If the users are not assigned to the new phase as well, or do not have Check Out any Files permission, they are no longer able to
access the files.
If there are other users already assigned to work on the files in the next phase, Trados GroupShare sends the new users a Files Ready For You
email message.

New assignment/Phase change notification email for Online Editor


When you change the phase for one or more files or when you receive a new assignment, Trados GroupShare sends out a Files Ready For You
email message. This email notifies the users assigned to work on the files in the current phase that they can start working on the files.
Users can now start translating the assignment in Online Editor by clicking the file name in the notification email. Online Editor allows several
concurrent users to work on the same assignment, at the same time. All users can check in their changes, but only the last user who works on the
file can change the file phase. Moreover, users having a Project Manager role can force the check in of files at any time.
If there are other users already assigned to work on the files in the next phase, Trados GroupShare sends the new users a Files Ready For You
email message.

Assignment changed/Removed notification email for Trados Studio


When you change the users assigned to work on the files in the current phase, Trados GroupShare sends out one of the Assignment Changed
email messages. These emails notify the users already assigned to work on the files in the current phase that other users have been added/removed
from the list of users assigned to work on the same files.
The users who are removed from the list of users working on the files in the current phase receive an Assignment Removed email message. This
email informs the unassigned users that they can stop working on the files.
Note: Users with Check out any files permission can check out files even if they receive an assignment removed notifications.

Assignment changed/Removed notification email for Online Editor


When you change the users assigned to work on the files in the current phase, Trados GroupShare sends out one of the Assignment Changed
email messages. These emails notify the users already assigned to work on the files in the current phase that other users have been added/removed
from the list of users assigned to work on the same files.

Email templates
Trados GroupShare uses a predefined email template which defines the format and appearance of the notification emails and the information they
contain. You can use your own email template to customize the email notifications that Trados GroupShare sends. You can specify customized
email templates when you first install Trados GroupShare or at any time from the Trados GroupShare Console.

Default Phase change email

Default Assignment removed email

Parent topic: File assignment


Related tasks
Step 4: Completing assignments
Step 5: Advancing assignments to the next phase
Step 1a: Creating projects from scratch
Step 2: Planning work on assignments
Creating project templates
Step 1b: Creating projects based on previous projects
Other information related to Trados GroupShare WebHooks
Parent topic: Using the Trados GroupShare WebHooks Service

Receiver and Sending flows


WebHook Receiver Registration Flow

WebHook receiver registration flow


Registration Request Structure
{
"WebHookUri":"http://<hosturl>/api/webhooks/incoming/custom",
"Secret":"12345678901234567890123456789033",
"Description":"Sample WebHook Reciever.",
"Filters":[ "Sdl.GroupShare.Events.V2.ProjectCreatedEvent",
"Sdl.GroupShare.Events.V2.PhaseChangeEvent",
"Sdl.GroupShare.Events.V2.AssignmentEvent",
"Sdl.GroupShare.Events.V2.CheckInEvent",
"Sdl.GroupShare.Events.V2.CheckoutEvent"
]
}

Sending WebHook Messages Flow

Sending WebHook messages flow

Event Message Design


Project Created Event

Headers
Key Value
X-Correlation-ID Correlation ID
Message Body
Property name Value
ProjectId Project ID
ProjectName Project name
RaisedBy Username of the user who triggered the event
Server Trados GroupShare server name, read from WebHookService settings.
Action Sdl.GroupShare.Events.V2.ProjectCreatedEvent
Example Message Body
{
"Action": "Sdl.GroupShare.Events.V2.ProjectCreatedEvent",
"ProjectName": "0430 - 1311",
"ProjectId": "3b7755a7-9ad3-4541-824e-81f8accadbaa",
"RaisedBy": "sa",
"Server": "groupshare.local"
}

Phase Change Event


Headers
Key Value
X-Correlation-ID Correlation ID
Message Body
Property name Value
ProjectId Project ID
LanguageFileId File ID
Phase JSON object that contains "id" and "name" members for phase id and phase
name.
RaisedBy Email address of the user who triggered the event
Server Trados GroupShare server name, read from WebHookService settings.
Message Body
Property name Value
Action Sdl.GroupShare.Events.V2.PhaseChangeEvent
Example Message Body
{
"Action": "Sdl.GroupShare.Events.V2.PhaseChangeEvent",
"Phase": {
"id": 22,
"name": "Translation"
},
"LanguageFileId": "ce88d061-284c-4af6-9902-62c1b9e5decf",
"ProjectId": "2a299c68-20c0-4bd3-87d0-a0d8c1490cf4",
"RaisedBy": "sa",
"Server": "groupshare.local"
}

Assignment Change Event


Headers
Key Value
X-Correlation-ID Correlation ID
Message Body
Property name Value
ProjectId Project ID
LanguageFileId File ID
From Collection of users who were assigned before the assignment change.
To Collection of user who are now assigned.
RaisedBy Email address of the user who triggered the event
Server Trados GroupShare server name, read from WebHookService settings.
Action Sdl.GroupShare.Events.V2.AssignmentEvent
Example Message Body
{
"Action": "Sdl.GroupShare.Events.V2.AssignmentEvent",
"From": [
{
"userEmail": "sa"
}
],
"To": [
{
"userEmail": "pm"
},
{
"userEmail": "sa"
}
],
"LanguageFileId": "ce88d061-284c-4af6-9902-62c1b9e5decf",
"ProjectId": "2a299c68-20c0-4bd3-87d0-a0d8c1490cf4",
"RaisedBy": "sa",
"Server": "groupshare.local"
}

Check Out Change Event


Headers
Key Value
X-Correlation-ID Correlation ID
Message Body
Property name Value
ProjectId Project ID
LanguageFileId File ID
RaisedBy Email address of the user who triggered the event
Server Trados GroupShare server name, read from WebHookService settings.
Action Sdl.GroupShare.Events.V2.CheckOutEvent
Example Message Body
{
"Action": "Sdl.GroupShare.Events.V2.CheckOutEvent",
"LanguageFileId": "ce88d061-284c-4af6-9902-62c1b9e5decf",
"ProjectId": "2a299c68-20c0-4bd3-87d0-a0d8c1490cf4",
"RaisedBy": "sa",
"Server": "groupshare.local"
}

Check In Change Event


Headers
Key Value
X-Correlation-ID Correlation ID
Message Body
Property name Value
ProjectId Project ID
LanguageFileId File ID
RaisedBy Email address of the user who triggered the event
Server Trados GroupShare server name, read from WebHookService settings.
Action Sdl.GroupShare.Events.V2.CheckInEvent
Example Message Body
{
"Action": "Sdl.GroupShare.Events.V2.CheckInEvent",
"LanguageFileId": "ce88d061-284c-4af6-9902-62c1b9e5decf",
"ProjectId": "2a299c68-20c0-4bd3-87d0-a0d8c1490cf4",
"RaisedBy": "sa",
"Server": "groupshare.local"
}
Supported languages
The following list contains all languages officially supported by Trados GroupShare. We aim to support the languages supported by Windows, but
support for some languages may be behind the latest Windows version.

A
Supported languages for Trados GroupShare projects:
Afar (Djibouti)
Afar (Eritrea)
Afar (Ethiopia)
Afrikaans (Namibia)
Afrikaans (South Africa)
Aghem (Cameroon)
Akan (Ghana)
Albanian (Albania)
Albanian (Kosovo)
Albanian (Macedonia FYRO)
Alsatian (France)
Alsatian (Liechtenstein)
Alsatian (Switzerland)
Amharic (Ethiopia)
Arabic (Algeria)
Arabic (Bahrain)
Arabic (Chad)
Arabic (Comoros)
Arabic (Djibouti)
Arabic (Egypt)
Arabic (Eritrea)
Arabic (Iraq)
Arabic (Israel)
Arabic (Jordan)
Arabic (Kuwait)
Arabic (Lebanon)
Arabic (Libya)
Arabic (Mauritania)
Arabic (Morocco)
Arabic (Oman)
Arabic (Palestinian Authority)
Arabic (Qatar)
Arabic (Saudi Arabia)
Arabic (Somalia)
Arabic (South Sudan)
Arabic (Sudan)
Arabic (Syria)
Arabic (Tunisia)
Arabic (U.A.E.)
Arabic (World)
Arabic (Yemen)
Armenian (Armenia)
Assamese (India)
Asturian (Spain)
Asu (Tanzania)

B
Bafia (Cameroon)
Bamanankan (Latin Mali)
Basaa (Cameroon)
Bashkir (Russia)
Basque (Basque)
Belarusian (Belarus)
Bemba (Zambia)
Bena (Tanzania)
Bengali (Bangladesh)
Bengali (India)
Blin (Eritrea)
Bodo (India)
Breton (France)
Bulgarian (Bulgaria)
Burmese (Myanmar)

C
Catalan (Andorra)
Catalan (Catalan)
Catalan (France)
Catalan (Italy)
Central Atlas Tamazight (Latin, Morocco)
Central Atlas Tamazight (Tifinagh, Morocco)
Chechen (Russia)
Chiga (Uganda)
Chinese (Simplified Han, Hong Kong SAR)
Chinese (Simplified Han, Macao SAR)
Chinese (Simplified PRC)
Chinese (Simplified, Singapore)
Chinese (Traditional, Hong Kong S.A.R.)
Chinese (Traditional, Macao S.A.R.)
Chinese (Traditional, Taiwan)
Church Slavic (Russia)
Cornish (United Kingdom)
Corsican (France)
Croatian (Croatia)
Croatian (Latin, Bosnia and Herzegovina)
Czech (Czech Republic)

D
Danish (Denmark)
Danish (Greenland)
Dari (Afghanistan)
Divehi (Maldives)
Duala (Cameroon)
Dutch (Aruba)
Dutch (Belgium)
Dutch (Bonaire, Sint Eustatius and Saba)
Dutch (Curaçao)
Dutch (Netherlands)
Dutch (Sint Maarten)
Dutch (Suriname)
Dzongkha (Bhutan)

E
Edo (Nigeria)
Embu (Kenya)
English (American Samoa)
English (Anguilla)
English (Antigua and Barbuda)
English (Australia)
English (Austria)
English (Bahamas)
English (Barbados)
English (Belgium)
English (Belize)
English (Bermuda)
English (Botswana)
English (British Indian Ocean Territory)
English (British Virgin Islands)
English (Burundi)
English (Cameroon)
English (Canada)
English (Caribbean)
English (Cayman Islands)
English (Christmas Island)
English (Cocos (Keeling Islands))
English (Cook Islands)
English (Cyprus)
English (Denmark)
English (Dominica)
English (Eritrea)
English (Europe)
English (Falkland Islands)
English (Fiji)
English (Finland)
English (Gambia)
English (Germany)
English (Ghana)
English (Gibraltar)
English (Grenada)
English (Guam)
English (Guernsey)
English (Guyana)
English (Hong Kong)
English (India)
English (Indonesia)
English (Ireland)
English (Isle of Man)
English (Israel)
English (Jamaica)
English (Jersey)
English (Kenya)
English (Kiribati)
English (Lesotho)
English (Liberia)
English (Macao, SAR)
English (Madagascar)
English (Malawi)
English (Malaysia)
English (Malta)
English (Marshall Islands)
English (Mauritius)
English (Micronesia)
English (Montserrat)
English (Namibia)
English (Nauru)
English (Netherlands)
English (New Zealand)
English (Nigeria)
English (Niue)
English (Norfolk Island)
English (Northern Mariana Islands)
English (Pakistan)
English (Palau)
English (Papua New Guinea)
English (Pitcairn Islands)
English (Puerto Rico)
English (Republic of the Philippines)
English (Rwanda)
English (Saint Kitts and Nevis)
English (Saint Lucia)
English (Saint Vincent and the Grenadines)
English (Samoa)
English (Seychelles)
English (Sierra Leone)
English (Singapore)
English (Sint Maarten)
English (Slovenia)
English (Solomon Islands)
English (South Africa)
English (South Sudan)
English (St Helena Ascension Tristan da Cunha)
English (Sudan)
English (Swaziland)
English (Sweden)
English (Switzerland)
English (Tanzania)
English (Tokelau)
English (Tonga)
English (Trinidad and Tobago)
English (Turks and Caicos Islands)
English (Tuvalu)
English (U.S. Virgin Islands)
English (US Minor Outlying Islands)
English (Uganda)
English (United Kingdom)
English (United States)
English (Vanuatu)
English (World)
English (Zambia)
English (Zimbabwe)
Esperanto (World)
Estonian (Estonia)
Ewe (Ghana)
Ewe (Togo)
Ewondo (Cameroon)

F
Faroese (Denmark)
Faroese (Faroe Islands)
Filipino (Philippines)
Finnish (Finland)
French (Algeria)
French (Belgium)
French (Benin)
French (Burkina Faso)
French (Burundi)
French (Cameroon)
French (Canada)
French (Caribbean)
French (Central African Republic)
French (Chad)
French (Comoros)
French (Congo [DRC])
French (Congo)
French (Djibouti)
French (Equatorial Guinea)
French (France)
French (Mauritius)
French (Mayotte)
French (Monaco)
French (Morocco)
French (New Caledonia)
French (Niger)
French (Rwanda)
French (Réunion)
French (Saint Barthélemy)
French (Saint Martin)
French (Saint Pierre and Miquelon)
French (Senegal)
French (Seychelles)
French (Switzerland)
French (Syria)
French (Togo)
French (Tunisia)
French (Vanuatu)
French (Wallis and Futuna)
Frisian (Netherlands)
Friulian (Italy)
Fulah (Cameroon)
Fulah (Guinea)
Fulah (Mauritania)
French (French Guiana)
French (French Polynesia)
French (Gabon)
French (Guadeloupe)
French (Guinea)
French (Haiti)
French (Ivory Coast)
French (Luxembourg)
French (Madagascar)
French (Mali)
French (Martinique)
French (Mauritania)

G
Galician (Galician)
Ganda (Uganda)
Georgian (Georgia)
German (Austria)
German (Belgium)
German (Germany)
German (Liechtenstein)
German (Luxembourg)
German (Switzerland)
Greek (Cyprus)
Greek (Greece)
Greenlandic (Greenland)
Guarani (Paraguay)
Gujarati (India)
Gusii (Kenya)

H
Hausa (Latin Ghana)
Hawaiian (United States)
Hebrew (Israel)
Hindi (India)
Hungarian (Hungary)

I
Ibibio (Nigeria)
Icelandic (Iceland)
Igbo (Nigeria)
Indonesian (Indonesia)
Interlingua (France)
Interlingua (World)
Inuktitut (Latin Canada)
Inuktitut (Syllabics Canada)
Irish (Ireland)
Italian (Italy)
Italian (San Marino)
Italian (Switzerland)

J
Japanese (Japan)
Javanese (Indonesia)
Javanese (Javanese Indonesia)
Jola-Fonyi (Senegal)

K
K'iche' (Latin, Guatemala)
Kabuverdianu (Cabo Verde)
Kabyle (Algeria)
Kako (Cameroon)
Kalenjin (Kenya)
Kamba (Kenya)
Kannada (India)
Kashmiri (Devanagari, India)
Kashmiri (Perso-Arabic, India)
Kazakh (Kazakhstan)
Khmer (Cambodia)
Kikuyu (Kenya)
Kinyarwanda (Rwanda)
Kiswahili (Congo DRC)
Kiswahili (Kenya)
Kiswahili (Tanzania)
Kiswahili (Uganda)
Konkani (India)
Korean (Korea)
Korean (North Korea)
Koyra Chiini (Mali)
Koyraboro Senni (Mali)
Kurdish (Perso-Arabic, Iran)
Kwasio (Cameroon)
Kyrgyz (Kyrgyzstan)

L
Lakota (United States)
Langi (Tanzania)
Lao (Lao P.D.R.)
Latin (World)
Latvian (Latvia)
Lingala (Angola)
Lingala (Central African Republic)
Lingala (Congo DRC)
Lingala (Congo)
Lithuanian (Lithuania)
Lower Sorbian (Germany)
Luba-Katanga (Congo DRC)
Luo (Kenya)
Luxembourgish (Luxembourg)
Luyia (Kenya)

M
Macedonian (Former Yugoslav Republic of Macedonia)
Machame (Tanzania)
Makhuwa-Meetto (Mozambique)
Makonde (Tanzania)
Malagasy (Madagascar)
Malay (Brunei Darussalam)
Malay (Latin Singapore)
Malay (Malaysia)
Malayalam (India)
Maltese (Malta)
Manipuri (India)
Manx (Isle of Man)
Maori (New Zealand)
Mapudungun (Chile)
Marathi (India)
Masai (Kenya)
Masai (Tanzania)
Mazanderani (Iran)
Meru (Kenya)
Meta' (Cameroon)
Mohawk (Mohawk)
Mongolian (Cyrillic Mongolia)
Mongolian (Traditional Mongolian, Mongolia)
Mongolian (Traditional Mongolian, PRC)
Morisyen (Mauritius)
Mundang (Cameroon)

N
N'ko (Guinea)
Nama (Namibia)
Nepali (India)
Nepali (Nepal)
Ngiemboon (Cameroon)
Ngomba (Cameroon)
North Ndebele (Zimbabwe)
Northern Luri (Iran)
Northern Luri (Iraq)
Norwegian Bokmal (Norway)
Norwegian Bokmal (Svalbard and Jan Mayen)
Norwegian Nynorsk (Norway)
Nuer (South Sudan)
Nyankole (Uganda)

O
Occitan (France)
Oriya (India)
Oromo (Ethiopia)
Oromo (Kenya)
Ossetian (Georgia)
Ossetian (Russia)

P
Papiamento (Caribbean)
Pashto (Afghanistan)
Persian (Iran)
Polish (Poland)
Portuguese (Angola)
Portuguese (Brazil)
Portuguese (Cabo Verde)
Portuguese (Guinea-Bissau)
Portuguese (Macao, SAR)
Portuguese (Mozambique)
Portuguese (Portugal)
Portuguese (Sao Tomé and Príncipe)
Portuguese (Timor-Leste)
Prussian (World)
Punjabi (India)
Punjabi (Pakistan)

Q
Quechua (Bolivia)
Quechua (Ecuador)
Quechua (Peru)

R
Ripuarian (Germany)
Romanian (Moldova)
Romanian (Romania)
Romansh (Switzerland)
Rombo (Tanzania)
Rundi (Burundi)
Russian (Belarus)
Russian (Kazakhstan)
Russian (Kyrgyzstan)
Russian (Moldova)
Russian (Russia)
Russian (Ukraine)
Rwa (Tanzania)

S
Saho (Eritrea)
Samburu (Kenya)
Sami Inari (Finland)
Sami Lule (Norway)
Sami Lule (Sweden)
Sami Northern (Finland)
Sami Northern (Norway)
Sami Northern (Norway)
Sami Northern (Sweden)
Sami Skolt (Finland)
Sami Southern (Norway)
Sami Southern (Sweden)
Sango (Central African Republic)
Sangu (Tanzania)
Sanskrit (India)
Scottish Gaelic (United Kingdom)
Sena (Mozambique)
Serbian (Cyrillic, Bosnia and Herzegovina)
Serbian (Cyrillic, Kosovo)
Serbian (Cyrillic, Montenegro)
Serbian (Cyrillic, Serbia)
Serbian (Latin, Bosnia and Herzegovina)
Serbian (Latin, Kosovo)
Serbian (Latin, Montenegro)
Serbian (Latin, Serbia)
Sesotho (Lesotho)
Sesotho (South Africa)
Sesotho sa Leboa (South Africa)
Setswana (South Africa)
Shambala (Tanzania)
Shona (Latin, Zimbabwe)
Sindhi (Devanagari, India)
Sindhi (Perso-Arabic, Pakistan)
Sinhala (Sri Lanka)
Slovak (Slovakia)
Slovenian (Slovenia)
Soga (Uganda)
Somali (Djibouti)
Somali (Ethiopia)
Somali (Kenya)
Somali (Somalia)
South Ndebele (South Africa)
Southern Sotho (South Africa)
Spanish (Argentina)
Spanish (Bolivarian Republic of Venezuela)
Spanish (Bolivia)
Spanish (Chile)
Spanish (Colombia)
Spanish (Costa Rica)
Spanish (Cuba)
Spanish (Dominican Republic)
Spanish (Ecuador)
Spanish (El Salvador)
Spanish (Equatorial Guinea)
Spanish (Guatemala)
Spanish (Honduras)
Spanish (Latin America)*
Spanish (Mexico)
Spanish (Nicaragua)
Spanish (Panama)
Spanish (Paraguay)
Spanish (Peru)
Spanish (Philippines)
Spanish (Puerto Rico)
Spanish (Spain International Sort)
Spanish (United States)
Spanish (Uruguay)
Standard Morrocan Tamazight (Tifinagh, Morocco)
Swati (siSwati, South Africa)
Swati (siSwati, Swaziland)
Swedish (Aland Islands)
Swedish (Finland)
Swedish (Sweden)
Syriac (Syria)

T
Tachelhit (Latin, Morocco)
Tachelhit (Tifinagh, Morocco)
Taita (Kenya)
Tajik (Cyrillic, Tajikistan)
Tamazight (Latin, Algeria)
Tamil (India)
Tamil (Malaysia)
Tamil (Singapore)
Tamil (Sri Lanka)
Tasawaq (Niger)
Tatar (Russia)
Telugu (India)
Teso (Kenya)
Teso (Uganda)
Thai (Thailand)
Tibetan (India)
Tibetan (PRC)
Tigre (Eritrea)
Tigrinya (Eritrea)
Tigrinya (Ethiopia)
Tongan (Tonga)
Tsonga (South Africa)
Turkish (Cyprus)
Turkish (Turkey)
Turkmen (Turkmenistan)

U
Ukrainian (Ukraine)
Upper Sorbian (Germany)
Urdu (India)
Urdu (Islamic Republic of Pakistan)
Uyghur (PRC)

V
Vai (Latin, Liberia)
Vai (Vai, Liberia)
Valencian (Spain)
Venda (South Africa)
Vietnamese (Vietnam)
Volapük (World)
Vunjo (Tanzania)

W
Walser (Switzerland)
Welsh (United Kingdom)
Wolaytta (Ethiopia)
Wolof (Senegal)

X
Xhosa (isiXhosa, South Africa)

Y
Yakut (Russia)
Yangben (Cameroon)
Yi (PRC)
Yiddish (World)
Yoruba (Benin)
Yoruba (Nigeria)

Z
Zarma (Niger)
Zulu (isiZulu, South Africa)
SDL Trados GroupShare task conrefs
Enter a short description of your task here (optional).

Before you begin


Enter the prerequisites here (optional).

About this task


Enter the context of your task here (optional).

Procedure
1. Go to the Users view and select the Content tab.
2. Go to the Users view and select the Users tab.
3. Go to the Users view and select the Permissions tab.
4. Go to the Resources view.
5. Go to the System Configuration view.

Steps for creating roles


Procedure
1. Select New Role to display the application-wide Add Roles window.
Tip: Alternatively, go to Edit Roles > Add New.
2. Select Finish.

Steps for editing roles


Procedure
1. Select Edit Roles and, from the drop-down menu, select the role you want to edit.
Tip: Alternatively, identify the role in the right-hand side pane and select .
2. Select Finish.

Steps for deleting roles


Procedure
1. xxxxxx
2. Select .

Steps for assigning roles to users


Procedure
1. Select the user's home organization (the organization in which the user was created).
2. In the right-hand side pane, identify the role you want to assign to your user. If necessary, select .
3. Under the role of your choice, select the Grant [role name] permissions to ... field.
4. In the list, select the user you want to assign the role to.
Note: Roles assigned within an organization propagate to its subsidiaries.

Steps for removing roles from users


Procedure
1. Select the user's home organization (the organization in which the user was created).
2. Identify the user whose role you want to remove.
3. Select the checkbox corresponding to the user's name.
4. Select Remove Users.
Steps for assigning permissions to user roles
Procedure
1. Expand the Edit Roles list and select the role you want to add permissions to.
2. Select Finish.

Steps for removing permissions from use roles


Procedure
1. Expand the Edit Roles list and select the role you want to remove permissions from.
2. Select Finish.

Steps for the Projects chapter


Procedure
1. In Trados Studio, go to the Projects view and double-click a project to open it.
2. In Trados Studio, go to the Projects view, double-click a project published on Trados GroupShare to open it.
3. Select Next.
4. Go to the Projects view and select a project to open it.

Steps for creating projects


Before you begin
Create a project template. You will need it during the project creation wizard.
If you want to upload a group of translatable files in one shot, you need to create a *zip archive that contains the files for translation.

Procedure
1. Go to the Projects view and select New Project.
2. In the General Settings tab of the New Project window:
a. Provide a name and a description for your project.
b. Select a location in the organization.
c. Select a project template from the list.
d. Browse for or drag and drop translatable files: the *zip archive (containing all the project files) or individual files.
Restriction: You can create projects either by using a *zip archive or by using individual files. You cannot use both methods at the
same time.
e. Optionally, set a due date and time for your project.
f. If you select the Restrict file downloads for this project checkbox, only the roles which have the Secure Project File Download
permission will be able to download the source files and the translated files. By default, the Secure Project File Download permission
is available for the following roles: Administrator, Power User, Project Manager.
3. In the New Project window, select the General Settings tab:
a. Provide a name and a description for your project.
b. Select a location in the organization.
c. Select a project template from the list.
d. Browse for or drag and drop translatable files: the .ZIP archive (containing all the project files) or individual files.
Restriction: You can create projects either by using a .ZIP archive or by using individual files. You cannot use both methods at the
same time.
e. Optionally, set a due date and time for your project.
4. If you have custom fields in your account Resources that want to apply to the new project:
a. Click the Custom Fields tab in the New Project window.
b. Select a Custom Field from the drop-down list.
c. Fill in a Value for the custom property.
d. To add more custom fields, select the plus sign and repeat steps b and c.
5. In the New Project window, select the PerfectMatch Settings tab.
6. On the Add Matching Files page, map your source files to previous translations from which you want to extract previous signed-off
segments. You can upload previous translations:
From Previous Projects. Choose this if you have an existing Trados GroupShare project that contains similar files from which you can
Extract PerfectMatch translations. The matches are parsed in the order in which the reference projects are added.
PerfectMatch is correctly applied if the language pair of the current project is the same as or one of the available language pairs of the
reference project.
The first reference project you add receives a LOCK status automatically. If you do now want to prevent translators from editing the
TUs to which PerfectMatch is applied, clear the LOCK checkbox. You can add the same reference project twice, and enable
LOCK on one instance while disabling LOCK on the second instance.
From bilingual Files. Choose this if you have .SDLXLIFF documents available on your computer from which you can extract
PerfectMatch translations. Make sure the names of the .SDLXLIFF files match the name of the corresponding source file. For single-
file projects, Trados GroupShare automatically renames .SDLXLIFF files to use the same name as the source file.
7. Select Finish.
The new project is added to the Projects list and instantly visible to all the users with access to the project. Trados GroupShare also shows
these users an on-screen notification about the new project.

Steps for completing projects


Procedure
1. Go to the Projects view and select the checkboxes corresponding to the projects you want to complete.
2. Select Mark as Completed.

Results
Trados GroupShare shows the status of the project as Completed.

Steps for adding/modifying/deleting servers


Procedure
1. In the Servers tab, select New Server.
2. In the Create Server dialog:
a. Choose a location for your server within the organization.
b. Enter a server name in the Name field.
c. Optionally, provide a description for your server.
d. Choose an authentication method.
3. Select Finish.
4. Select Edit.
5. Select Delete.

Steps for adding/modifying/deleting containers


Procedure
1. In the Containers tab, select New Container.
2. In the Create Container dialog:
a. Choose a location for your container within the organization.
b. Choose a database server.
c. Enter a container name and a database name.
d. Optionally, provide a description for your container.
3. Select Finish.
4. Select Edit.
5. Select Delete.

Steps for creating/deleting/modifying TMs


Procedure
1. In the Translation Memories tab, select New Translation Memory.
2. On the General Settings page:
a. Type the TM details.
b. Choose a location for your TM.
3. On the Language Pairs page, select source and target languages for your language pair(s).
4. On the Fields page, perform one of the following actions:
Select a field template. The field columns are automatically updated with the template content.
Configure the field columns.
Leave the fields blank.
5. On the Language Resources page select a language resource template or configure each language resource.
If you select a field template, the field columns are automatically updated with the template content.
If you select , you can configure the fields accordingly. Select Finish.
6. On the Advanced Settings page, do one of the following:
If you selected a language resource template in the previous step, the Advanced Settings page is automatically populated with data
from the template and all checkbox options are disabled. You can consult these settings, but you cannot edit them.
If you did not select a language resource template in the previous step, select the checkboxes corresponding to your TM's recognized
tokens and multiple-part tokens (considered as one element).
7. On the Performance Tuning page, in the make any necessary changes in terms of Performance, Fuzzy Index and Statistics, and consult
whether the TUs are aligned.
Note: upLIFT alignment is the fragment alignment (also known as FGA) that automatically occurs for TMs which have 5,000 TUs or more.
The automatic alignment happens between 00:00 AM and 06:00 AM. You can check whether the TUs are aligned or not on the
Performance Tuning page of server-based TMs which meet the minimum 5,000 TU requirement.
8. Select Next.
9. Select Finish.

Steps for adding/modifying/deleting language resources and language resource


templates
Procedure
1. On the Language Resources page:
a. Select a source language and click the page white space.
b. Select .
c. In the Create Language Resource Template > [source language name] dialog, select the Abbreviations page.
d. Type an abbreviation. Click anywhere on the white page and type more abbreviations.
e. Select Next.
f. On the Ordinal Followers page, type an ordinal follower. Click anywhere on the white page and type more ordinal followers.
g. Select Next.
h. On the Segmentation Rules page, choose either Paragraph based segmentation or Sentence based segmentation, and add or edit
segmentation rules.
i. Select Next.
j. On the Variables page, type a variable. Click anywhere on the white space and type more variables.
k. Select Finish.
2. Select Finish.
3. Select Edit.
4. Select Delete.

Steps for adding/deleting project templates


Procedure
1. In the Project Templates tab, select New Project Template.
2. In the General Settings page of the New Project Template wizard:
a. Type a name, and, optionally, a description for your project template.
b. Choose a location for the project template in your organization.
c. Browse for your template file.
3. Select Next
4. In the Language Pairs page of the New Project Template wizard, select a source language and one or more target languages.
5. You can select Finish to save the project template or select Next to continue the wizard with adding translation memories (TMs) or
termbases.
6. In the Translation Memories page of the New Project Template wizard:
under All language pairs, select a TM from the ones available in your organization to use for all your language pairs
under Specific Language Pairs, select a specific TM from the ones available in your organization to use for a specific language pair.
7. In the Termbases page of the New Project Template wizard, select a termbase from the ones available in your organization.
8. Select Finish.
9. Select Delete.
10. Select Create.

Steps for reports


Procedure
1. In the [project name] tab, select .
2. Consult the report details.
3. Optionally, go to the table columns and:
Sort the data in ascending or descending order.
Customize the columns that are displayed.
Tip: The filters you apply at column level are kept when printing the report.
4. Select Print.
5. Select Save As and choose an export file format.

Procedure

Required folder hierarchy and naming for .ZIP archives

When you create a project from a .ZIP file that contains multiple files, Trados GroupShare automatically identifies all the translatable files from the
root folder and from any subfolders available in the archive.
If your .ZIP archive also contains reference files or PerfectMatch files, make sure to use the structure and file naming described below. This
hierarchy enables Trados GroupShare to map your source files to the corresponding PerfectMatch files:
\SourceFiles - Optional folder containing the individual files or subfolders of files for translation. If you do not want to group all source files into
a single folder, you can also add the source files directly under the root archive folder. If you do add the source files as a single folder, we
recommended naming this folder "SourceFiles" to enable Trados GroupShare to map any corresponding PerfectMatch files easier.
If you name the SourceFiles folder differently, the structure of the PerfectMatch folder must also include your custom-name folder for every
language code subfolder in your PerfectMatch folder. See image 2b: ZIP structure when using a custom name for the Source Files folder.
...\1st Set Of Source Files
...\...\...\First File.docx
...\...\...\Second File.doc
...\2nd Set of Source Files
...\...\Third File.txt
...\...\Fourth File.doc

\PerfectMatchFiles - Optional folder containing already translated files in .SDLXLIFF format. The name of the folder must be
"PerfectMatchFiles". The PerfectMatch structure should match the folder and file name of the corresponding the source folder and source file.
...\de-de
...\...\1st Set Of Source Files
...\...\...\First File.docx.sdlxliff
...\...\...\Second File.doc.sdlxliff
...\...\2nd Set of Source Files
...\...\...\Third File.txt.sdlxliff
...\...\...\Fourth File.doc.sdlxliff
...\fr-fr
...\...\1st Set Of Source Files
...\...\...\First File.docx.sdlxliff
...\...\...\Second File.doc.sdlxliff
...\...\2nd Set of Source Files
...\...\...\Third File.txt.sdlxliff
...\...\...\Fourth File.doc.sdlxliff

\PerfectMatchFiles_1 - If you have more than one version of a PerfectMatch file that you want to apply to a source file, or if you want to add
more than one .SDLXLIFF file with the same name, create additional "PerfectMatchFiles" folders using the following format:
\PerfectMatchFiles_1, \PerfectMatchFiles_2, \PerfectMatchFiles_3,...
...\de-de

...\...\1st Set Of Source Files


...\...\...\First File.docx.sdlxliff
...\...\2nd Set of Source Files
...\...\...\Fourth File.doc.sdlxliff

\ReferenceFiles - Optional folder containing project files that should be used as a reference when translating or reviewing the source files. The
name of the folder must be "ReferenceFiles".
...\Diagram.vdsx
...\Image.png

Image 1: Required .ZIP structure when using the recommended name for the Source Files folder

Image 2: Required .ZIP structure when using a custom name for the Source Files folder
Viewing your license status
You can view your current license status if you want to check details about license validity or license feature coverage.
By viewing your current license status, you can check:
How many days are left in your trial license before product purchase becomes mandatory
What license type you have, before upgrading to a different license version
What your translation unit (TU) threshold is
How many CALs are currently allocated in your license
You can view your current license information in the Product Activation dialog or, for some products, on the web interface.

To display the Product Activation Do the following:


dialog in:

Trados GroupShare This dialog is automatically displayed each time you open the application in trial mode or when you
access it from the Help tab > Product Activation.

>
Trados GroupShare
This dialog is automatically displayed each time you access Help > Product Activation.

Trados GroupShare If you are on the computer where Trados GroupShare is installed, select:
(TM Server/Project Server/MultiTerm Start > > Trados GroupShare [year] > GroupShare [year] Product Activation.
Server)

Parent topic: Licensing


Post-translation Analysis report
The Reports view now includes an additional report: Post-translation analysis (PTA). Generate this report during any project phase to get a
detailed overview of your TM leverage and translators' effort on individual files.
PTA shows the number of words, segments and characters translated by each translator who has worked on the project file. The counts are
grouped by match rate to help you determine translation costs accurately: New, Perfect Match, Context Match, Exact Match, Fuzzy Band. The
PTA report is also generated automatically, as part of the Finalize task.
Parent topic: Changes introduced in Trados GroupShare 2020 SR1
GroupShare TMs and local TMs
Translation Memories (TMs) that are stored on Trados GroupShare are called Trados GroupShare TMs. TMs that are stored on the user's
computer are called local TMs.
Users can access and manage both TM types depending on their infrastructure, affiliation and needs. To access and manage a Trados GroupShare
TM, users need to be part of an organization which assigns them roles that have sufficient permissions for these tasks. The two TM types share the
following similarities and differences:
Properties Trados GroupShare TMs Trados Studio TMs
Accessed via a client application like Trados YES YES
Studio
Accessed from anywhere YES NO
Accessed and updated concurrently by many YES NO
users
Stored on a database server YES NO
Stored on a local computer NO YES
Managed by Trados GroupShare YES NO
Managed by Trados Studio NO YES
Parent topic: Translation memories (TMs)
Options for displaying tags
In Online Editor, you can choose between multiple ways of having tags displayed.
The following options are available on the View tab, in the Tags group, in the Show Tag Details list:
No Tag Text – If you choose this option, no text is displayed within tags. To see the entire content of a tag, place the cursor over it.
Partial Tag Text – If you choose this option, text is displayed only partially within tags. To see the entire content of a tag, place the cursor
over it.
Full Tag Text – If you choose this option, all the available content is displayed within tags.
Tag Id – If you choose this option, only IDs are displayed within tags. Tag IDs are unique identifiers assigned automatically to each tag pair
and placeholder tag in the asset. To see the entire content of a tag, place the cursor over it.
Parent topic: Formatting segments
Modifying comments
You can modify previously added comments if you feel that they are not clear enough or if you forgot to make an important point about something.
You can also modify the severity levels of comments.

Procedure
1. Open the appropriate file in Online Editor.
2. On the right side of the screen, select Comments .
3. In the Comments panel, find the comment that you want to modify.
4. Select the current text of the comment.
5. Make changes to the text or to the severity level of the comment.
6. Select an area outside the comment to save your changes.
Parent topic: Working with comments
GroupShare REST API improvements
If a translation file exists in GroupShare with a RelativePath property set, the following API calls return the RelativePath property of the file: GET
/api/projectserver/v2/projects/{projectId}/files/detailed-information and GET /api/projectserver/v2/projects/{projectId}/files. This helps
developers support users with files in sub-folders via the GroupShare API. (CRQ-24022)
Parent topic: Changes introduced in Trados GroupShare 2020 SR1 CU6
Downloading project files in .sdlxliff format
You can download the project files in .sdlxliff format to store or consult them irrespective of the project phase they are in, if you are not
restricted in this regard by a user who has the Secure Project File Download permission.

About this task


To restrict the download of project files to some users, users must be assigned a role which has the Secure Project File Download permission. The
Secure Project File Download permission is assigned to the following roles by default: Administrator, Power User and Project Manager. During
project creation, users in these roles must select the Prevent file downloads for this project checkbox, which means that only users with the Secure
Project File Download permission will be able to download the source project files and the translated project files.

Procedure
1. In the Projects view, select the project whose files you want to download in .sdlxliff format .
2. In the project tab, do one of the following:
Select Download all files > Download all files (target excluded).
Select the checkboxes corresponding to the files you want to download and select selected files.
3. Save the document(s) as a zip archive on a location of your choice.
Parent topic: Project management
Restoring archived projects
You can restore archived projects, if necessary. When Trados Studio connects to a Trados GroupShare server, it no longer displays archived
projects into its Projects view, thus improving overall performance and productivity.

Before you begin


Users who restore archived projects need the Edit Project permission in Trados GroupShare.

Procedure
1. In the Projects view, select the checkboxes corresponding to the Archived projects you want to restore.
Note: If the project list does not display Archived projects, select the Filter panel and select the Archived checkbox.
2. Select Restore.

Results
The project status is changed from Archived to completed.
Parent topic: Project archiving
Viewing navigation information about a file
Navigation information consists in the name and path of the file, as well as in details about whether the segment you are working on is part of a
header, a footer, or a paragraph, for example.

Procedure
1. Open the appropriate file in Online Editor.
2. On the View tab, in the Navigation group, select Show Navigation.
Parent topic: Navigating the Online Editor user interface
Custom fields
As a project manager or power user, you can create a list of custom fields to be used by other users.
A custom field is metadata that can be attached to a certain project in Trados GroupShare.
Creating custom fields
Editing custom fields
You can modify the details of custom fields when they no longer suit your needs.
Deleting custom fields
You can safely delete any custom field that no longer meets your requirements.
Parent topic: Working with resources
Retiring legacy Language Weaver URLs
Starting with February 23rd, support for our legacy web domains is discontinued:
sdl.com
sdlbeglobal.com
This change is part of our brand transformation to Language Weaver and unifies access to our platform.
The following URLs are impacted by this change and will be decommissioned:
Web UI URLs:
https://translate.sdlbeglobal.com
https://translate.sdl.com
API base URLs:
https://translate-api.sdl.com
https://translate-api.sdlbeglobal.com
For more information, check out this article which explains how the API integration is affected.
Parent topic: Changes introduced in Trados Groupshare 2020 SR1 CU9
Creating projects
When you create projects from the Trados GroupShare web interface, you create a storage for all the files that need to be translated. At this stage,
you also decide which organization is in charge of your project.

Before you begin


Make sure you:
Create a project template. You will need it during the project creation wizard.
If you want to upload a group of translatable files in one shot, you need to create a *zip archive that contains the files for translation.

Procedure
1. Go to the Projects view and select New Project.
2. In the General Settings tab of the New Project window:
a. Provide a name and a description for your project.
b. Select a location in the organization.
c. Select a project template from the list.
d. Browse for or drag and drop translatable files: the *zip archive (containing all the project files) or individual files.
Restriction: You can create projects either by using a *zip archive or by using individual files. You cannot use both methods at the
same time.
e. Optionally, set a due date and time for your project.
f. If you select the Restrict file downloads for this project checkbox, only the roles which have the Secure Project File Download
permission will be able to download the source files and the translated files. By default, the Secure Project File Download permission
is available for the following roles: Administrator, Power User, Project Manager.
3. In the New Project window, select the PerfectMatch Settings tab.
4. If you have custom fields in your account Resources that want to apply to the new project:
a. Click the Custom Fields tab in the New Project window.
b. Select a Custom Field from the drop-down list.
c. Fill in a Value for the custom property.
d. To add more custom fields, select the plus sign and repeat steps b and c.
5. Select Finish.
The new project is added to the Projects list and instantly visible to all the users with access to the project. Trados GroupShare also shows
these users an on-screen notification about the new project.
Parent topic: Project management
Related concepts
Workflow for shared projects started in Trados Studio
Workflow for shared projects started in Trados GroupShare
About Perfect Match
Known issues
This page contains a list of known issues related to Trados GroupShare 2020 SR1 CU6.

Breaking change in TM-Service REST API


Creating TMs as a user that is assigned to multiple organizations triggers the following error: An internal server error occurred. An error
occurred while processing your request. ". To avoid this, when creating TMs, make sure that the POST request paylod contains both location
and ownerId. The location parameter must contain the organization path for the new TM, whereas the ownerId should be set to the respective
organization's GUID. This change in parameters applies to language resource templates and field templates as well, so you need to send both
location and ownerId. (CRQ-25767)

Emoji issues in the Online Editor


In the Online Editor, you cannot delete emojis in target segments unless you add a few characters after them. Trying to repeatedly add emojis will
lead to unwanted characters and incorrect emoji placement. Additionally, downloading or checking in the native file from the Online Editor after
inserting emojis in target segments will result in errors. To avoid these errors, make sure that you use the same emojis in the same order as they
appear in the source when translating segments.

AutoSuggest in the Online Editor disabled for Asian languages


With the current releases, the AutoSuggest feature in the Online Editor is disabled when translating or reviewing into Asian languages. We're
bringing AutoSuggest back for Asian languages to the Online Editor in Trados GroupShare with the upcoming 2020 SR1 CU7 release soon.
Parent topic: Changes introduced in Trados GroupShare 2020 SR1 CU6
Upgrading from SDL Trados GroupShare 2017 to Trados
GroupShare2020 SR1
Recommendation
RWS recommends users who have the SDL Trados GroupShare 2017 RTM version to first update to SDL Trados GroupShare 2017 CU10,
and only then to upgrade to Trados GroupShare 2020 SR1.
Supported upgrades
From SDL Trados GroupShare 2017 CU10 to Trados GroupShare 2020 (or later CUs) and SR1
From Trados GroupShare.00. 2017 CU11 to Trados GroupShare 2020 CU1 or later
Unsupported upgrades
From SDL Trados GroupShare 2017 CU11 to Trados GroupShare 2020 RTM.
Upgrading the database manually
To upgrade the database from SDL Trados GroupShare 2017 CU10 to Trados GroupShare 2020 SR1 manually:
1. Run Sdl.GroupShare.Database.SdlSystem.dacpac on the SDLSystem database.
2. Run Sdl.GroupShare.Database.MTMaster.dacpac on the MTMaster database.
3. Run all .SQL script files from TMServiceSystem_UpgradeSchema_1.5.3.sql to TMServiceSystem_UpgradeSchema_1.6.8.sql
on the TMService database.
4. Run all .SQL script files from tmserver-mssql-8.59-to-9.0.0.sql to tmserver-mssql-11.0.24-to-11.0.35.sql on the
TMContainer database.
5. Create Logs database.
6. Run Sdl.GroupShare.Database.Logs.dacpac on the Logs database.
7. Run TranslationModelsMain_UpgradeSchema_1.0.1.sql on the TMModel database.
8. Run TranslationModelsMain_UpgradeSchema_1.1.0
.sql on the TMModel database.
9. Run Sdl.GroupShare.Database.WebHooks.dacpac on the WEBHooks database.
10. Run Sdl.GroupShare.Database.CPSService.sql on the CPSSevice database.
11. Run LRServiceSystem_UpgradeSchema_1.2.0.sql on the TMService database.
Note:
For manually deploying dacpac packages you could use SqlPackage command. The tool need to be downloaded from Microsoft. An example
command to run it (replace the variables): SqlPackage.exe /a:Publish /sf:{PathToDacpacFile} /tcs:{SQLConnectionString}
/p:BlockOnPossibleDataLoss=false
Parent topic: Upgrading to Trados GroupShare 2020 SR1
Project settings
Project settings refer to the elements which control a project's behaviour. You can access and manage the project settings if you are assigned the
Edit Project permission.
Project settings are particularly useful if Trados Studio projects are published on an Trados GroupShare server, and you need to consult or modify
the project settings without having to log on to Trados Studio.
Viewing project settings
You can access and manage the project settings if you are assigned the Edit Project permission.
Editing project settings
You can access and manage the project settings if you are assigned the Edit Project permission.
Parent topic: Project management
Translation origin
A source text and a target text unit form a translation unit (TU). TUs are displayed on one row in Online Editor. Each TU has a translation origin,
namely a resource where the translation originated.
TUs can have one of the following translation origins at a time:
Interactive (no icon) - This target segment has been changed by typing inside the target segment.
Copied From Source (no icon) - This target segment has been changed using the Copy the source to target option.
100% matches ( ) - This target segment has been changed by applying a TU with a corresponding 100% match from a
translation memory (TM). A 100% match occurs when a segment has been translated before, whether in the same asset, or in a different
asset with the exact same segment.
Context Match ( ) - This target segment has been changed by applying a TU with a corresponding context match from a TM.
A context match occurs when a segment has been translated before in the same asset and with the same surrounding text.
Perfect Match ( ) - This target segment has been changed by automatically comparing the source file to an existing bilingual
file, not to a TM. Perfect matches are checked for context, which means that the surrounding text is also checked to ensure that it is the
same as in the bilingual file. For more information about perfect matches and their usage, see the Trados Studio documentation.
Auto-propagated ( ) - This target segment has been changed by auto-propagating a translation, after typing and confirming
another segment identical with the current one.
TM with Rejected changes ( ) - This target segment has been changed by applying a TU with rejected changes
from a TM. These matches originate from segments that have been translated and saved to the TM, but whose changes were rejected later
on by a linguistic reviewer.
Automatic Translation ( ) - This target segment has been changed by applying a TU from an automated translation
server.
Neural Machine Translation - This target segment has been changed by applying a TU from Machine Translation.
Fuzzy Match ( ) - The segment was translated by applying a 98% TM match (a fuzzy match), and then by editing and
confirming the translation. The fuzzy match figure is retained so that you can tell this was a fuzzy match which was subsequently edited.
When you edit a segment, the background color of the percentage match figure disappears.
Tip: The notion of origin before adaptation applies to segments which have been changed multiple times and refers to the previous origin of the
segment. For example, if a segment was machine-translated initially, but you made a few corrections later on, its current origin is Interactive (you
performed the last change by typing a translation manually) and its origin before adaptation is Automatic Translation (the origin before the last
change).
Parent topic: Filtering segments
Deleting roles
When roles are no longer necessary, you can delete them from the server.

Procedure
1. Go to the Users view and select the Permissions tab.
2. Select an organization and select the role you want to delete.
3. Select .
Parent topic: User roles
Archiving completed projects
You can reduce the list which displays all the Trados GroupShare projects by archiving the ones which are completed and are not imminently
needed anymore. Archived projects can be restored at a later date, if necessary.

Before you begin


Users who archive projects need the Edit Project permission in Trados GroupShare.

About this task


When the Enable automatic Project Archiving option is enabled in Trados GroupShare Console, Trados GroupShare executes an automated
nightly task to archive projects that are in Completed status for more than the number of days set up in Trados GroupShare Console.

Procedure
1. In the Projects view, select the checkboxes corresponding to the Completed projects you want to archive.
2. Select Archive.

Results
The project status is changed from Completed to Archived.
Parent topic: Project archiving
Translating content
You can translate content in Online Editor using the translation resources (TMs, terminology, MT) originating in the application Online Editor
integrates with.
Online Editor can integrate with: Trados Studio, Trados GroupShare, Managed Translation, WorldServer, cloud products (Trados Enterprise,
Trados Team, Trados Studio cloud capabilities).
Copying source content to target segments
If a source segment contains long numbers or other characters which are easily mistyped, you can copy the entire content of a source
segment into the target segment and translate around those characters. Do the same if the segment translation is the same in both the source
and in the target language.
Modifying source segments
If some of the source segments you are working on contain mistakes, you can modify them and correct the mistakes.
Copying content in target segments
If copying content to and from source segments is disabled, you can still copy external content to target segments.
Splitting segments
If the initial segmentation of a file contains source segments that are too long (perhaps as a result of improper formatting in the source text)
and that should be split, you can correct the segmentation and split the segments.
Merging segments
If the initial segmentation of a file contains source segments that were split unnaturally (perhaps as a result of improper formatting in the
source text) and that should be merged, you can correct the segmentation and merge the segments.
Formatting segments
When working with segments, you can perform multiple actions to make sure that the formatting in your target text is consistent with the one
in the source text.
Inserting symbols and special characters
If your translation needs to contain symbols and special characters, you can insert them directly from the Online Editor user interface. These
include em dashes (—), en dashes (–), copyright (©) and trademark (™) symbols, as well as various types of quotation marks.
Overwriting content in segments
If you copy the content of source segments to target segments, you do not need to delete all the copied content when you start translating;
you can simply overwrite it.
Clearing the content of target segments
You can remove the entire content of a target segment, regardless of whether it contains revisions or not, and then start translating again
from scratch.
Working with translation memories and terminology
Keeping previously translated content in translation memories and enforcing terminology are best practices for reusing content and reducing
translation costs.
Locking and unlocking segments or parts of segments
By locking segments or parts of segments, you can protect them from being modified. You can unlock protected segments or parts of
segments if you need to modify them.
Confirming translated segments
You should confirm segments when you finish translating them or if you want to approve them during the review process. Confirmed
translations are added to the translation memory automatically.
Changing segment statuses
You can change the status of a segment if you want to mark a confirmed segment as Draft or if you want to approve, reject, or sign off
translated segments during the review process.
Parent topic: Working with Online Editor
Interactive Logon permission is no longer required
Installing Trados GroupShare no longer requires Interactive Logon. Previously, specifying a service account that did not have the Interactive Logon
permission would lead to an installation error. Additionally, the Log on as a service permission will be granted to the service user specified in the
Trados GroupShare installer. (CRQ-25634)
Parent topic: Changes introduced in Trados GroupShare 2020 SR1 CU6
TM language processing rules and recognized tokens
Translation memories (TMs) are complex databases that use a series of versatile elements catering for your translation needs.
TMs are based on language processing rules which include:
Segmentation rules for the source text
Recognized tokens (placeableas) to identify non-translatable content:
Dates
Times
Numbers
Measurements
Acronyms and URLs
Email addresses
Alphanumeric strings
Variables
Currencies
The ability to generate and customize language processing rules makes the TM creation process very flexible and efficient.
TM backwards compatibility
Trados GroupShare 2020 CU3 and Trados Studio 2021 include major improvements to the language processing rules functionality. These
improvements enable you to customize auto-localization formats for the following recognized tokens: dates, times, numbers, measurements and
currency amounts.
The possibility to extend the formats used for identifying and auto-localizing recognized tokens is not supported in previous versions of Trados
Studio and Trados GroupShare.
This causes the following compatibility limitations:
Language processing rules created in Trados GroupShare 2020 CU3 are not compatible with TMs created in Trados Studio 2017 and
2019.
TMs created in Trados GroupShare 2020 CU3 and later can be opened in Trados Studio 2017 and 2019 TMs, but you cannot edit the
TM settings in these Trados Studio versions.
To avoid these limitations, we recommend using language processing rules created in Trados GroupShare 2020 CU3 and Trados Studio 2021,
and later, only with the current and future releases.
Item categories: translatable and other items
You define the item category when you add the item to a project and the category is shown in the project status. The table in this topic lists
available item categories.
Language resource templates
Segmentation rules
Segmentation rules define how a translation memory (TM) or a project divides source text into segments.
Abbreviations
Abbreviations are standardized short strings that replace full words or expressions. Abbreviations must be marked appropriately in
translation memories (TMs), so that they can be differentiated from fully fledged words or expressions.
Ordinal followers
Ordinal followers refer to the various symbols used in numbers, figures or dates.
Recognized Tokens
A recognized token is a short piece of text, in a defined set of formats, that a translation memory (TM) treats as a single word.
Parent topic: Translation memories (TMs)
Supported file types
The current topic provides a table of supported file types, their file name extensions, and a help topic concerning the file type settings.

File type name File type extension Help topic


SDL XLIFF *.sdlxliff SDLXLIFF
XLIFF *.xlf, *.xliff,.xlz XLIFF
XLIFF 2.0 *.xlf, *.xliff XLIFF 2.0
XLIFF: Kilgray MemoQ *.mqxlf, *.mqxliff, *.mqxlz XLIFF: Kilgray MemoQ

Microsoft Word 97-2003 *.doc, *.dot*.wps Word 97-2003

Microsoft Word 2007-2019 *.docx, *.dotx, *.docm, *.dotm Word 2007-2013

Microsoft PowerPoint 97-2003 *.ppt, *.pps, *.pot,.dps PowerPoint 97-2003

Microsoft PowerPoint 2007-2019 *.pptx, *.ppsx, *.potx, *.pptm, *.potm, PowerPoint 2007-2019
*.ppsm

Microsoft Excel 97-2003 *.xls, *.xlt,.et Excel 97-2003


Microsoft Excel 2007-2019 *.xlsx, *.xltx, *.xlsm,*.xltm Excel 2007-2016
Bilingual Excel Studio *.xlsx Bilingual Excel Studio
Microsoft Visio *.vsdx, *.vsx, *.vtx, *.vdx, *.vssx, *.vstx, Visio
*.vsdm, *.vssm, *.vstm

Rich Text Format (RTF) *.rtf Rich Text Format

XHTML 1.1 (2) *.html, *.htm , *.xhtm


HTML 5 *.htm, *.html, *.xhtml, *.jsp, *.asp, *.aspx, HTML 5
*.ascx, *.inc, *.php, *.hhk, *.hhc
Adobe FrameMaker 8-2020 MIF *.mif FrameMaker MIF
Adobe FrameMaker 8-2020 MIF V2 *.mif

Adobe InDesign CS2-CS4 INX *.inx InDesign INX


Adobe InDesign CS4-CC IDML *.idml InDesign IDML
Adobe InCopy CS4-CC ICML *.icml InCopy ICML
Adobe Photoshop *.psd;*.pdd;*.psdt; Adobe Photoshop
OpenDocument Text Document (ODT) *.odt, *.ott, *.odm OpenDocument Text Document
OpenDocument Presentation (ODP) *.odp, *.otp OpenDocument Presentation
OpenDocument Spreadsheet (ODS) *.ods, *.ots OpenDocument Spreadsheet
QuarkXPress Export *.xtg, *.tag QuarkXPress
PDF *.pdf PDF
Comma Delimited Text (CSV) *.csv Simple Delimited Text
Tab Delimited Text *.txt Simple Delimited Text
Portable Object *.po Portable Object
Subtitle formats *.srt,*.vtt,*.sbv,*.sub,*.ttml,*.xml,*.dfxp SubRip
File type name File type extension Help topic
Java Resources *.properties Java Resources
Microsoft .NET *.exe; *.dll Microsoft .NET Libraries
Markdown *.md;*.markdown Markdown
XML 2: Microsoft .NET Resources *.resx XML: Microsoft .NET
XML 2: OASIS DITA 1.3 Compliant *.xml, *.dita,*.ditamap XML: OASIS DITA 1.3
XML 2: OASIS DocBook 4.5 Compliant *.xml XML: OASIS DocBook 4.5
XML 2: Author-it Compliant *.xml XML: Author-it
XML 2: MadCap Compliant *.html, *.htm XML: MadCap
XML 2: W3C ITS Compliant *.xml, *.its XML: W3C ITS
XML 2: Any XML *.xml XML: Any XML
JSON *.json JSON
Text *.txt Text
Email *.msg, *.eml, *.emlx, *.oft Email
YAML *.yaml;*.yml YAML
XLIFF MemSource *.mxliff MemSource
Parent topic: Working with projects
Shortcuts in Online Editor
Shortcuts are a simple and efficient alternative to working with the mouse. As project deadlines near, you might want to use them to save time.
The following keyboard shortcuts are available in Online Editor and can be used with Microsoft keyboards. For Mac keyboards, use the Option
key (instead of Alt) and the Command key (instead of Ctrl).
Category Windows Shortcut Mac Shortcut Action
Translating Ctrl+Enter Command+Enter Confirm the current translation and move to the next
and unconfirmed segment.
reviewing
content
Ctrl+Alt+Enter Command+Option+Enter Confirm the current translation and move to the next segment,
regardless of its status.
Ctrl+Alt+Shift+Enter Command+Option+Shift+Enter Confirm the current translation and remain on the current
segment.
Ctrl+R Control+R Reload the current segment if its translation has been modified
in the meantime.
Ctrl+B Command+B Apply bold formatting.
Ctrl+I Command+I Apply italics formatting.
Ctrl+U Command+U Apply underline formatting.
Ctrl+Alt+Oemplus Control+Option+Oemplus Apply subscript formatting.
Ctrl+Shift+Oemplus Control+Shift+Oemplus Apply superscript formatting.
Ctrl+Shift+K Command+Shift+K Apply smallcaps formatting.
Ctrl+Space Command+Fn+Space Clear formatting.
Ctrl+Alt+Space Control+Option+Space Clear all segments.
Ctrl+Insert Control+Shift+I Copy the source content of the current segment to the target
area.

Alt+Shift+Insert Control+Shift+Option+I Copy the source content of all segments to the target area.
Alt+Delete Option+Fn+Backspace Clear the content of the current target segment.
Alt+Shift+Delete Option+Shift+Fn+Backspace Clear the content of all the segments having the "Draft" status.
Shift+F3 Shift+Fn+F3 Change the casing of a selected segment or text.
Ctrl+Comma Command+Comma or Bring up the smart action menu.
Control+Comma
Insert Command+Shift+O or Turn overwrite (insert) mode on or off.
Control+Shift+O
Alt+F2 Fn+F2+Option Enable source editing for the current segment.
F8 Fn+F8 Verify document.
F3 Fn+F3 Open concordance search for the selected source/target.
Working Alt+Page Up Option+Fn+Up Arrow Go to the previous translation in the Lookups panel.
with the
translation
memory
Alt+Page Down Option+Fn+Down Arrow Go to the next translation in the Lookups panel.
Ctrl+Shift+A Command+Shift+A or Apply selected translation from the Lookups panel.
Control+Shift+A
Ctrl+1 Command+1 Apply the 1st translation from the Lookups panel.
Ctrl+2 Command+2 Apply the 2nd translation from the Lookups panel.
Ctrl+3 Command+3 Apply the 3rd translation from the Lookups panel.
Ctrl+4 Command+4 Apply the 4th translation from the Lookups panel.
Ctrl+5 Command+5 Apply the 5th translation from the Lookups panel.
Category Windows Shortcut Mac Shortcut Action
Ctrl+6 Command+6 Apply the 6th translation from the Lookups panel.
Ctrl+7 Command+7 Apply the 7th translation from the Lookups panel.
Ctrl+8 Command+8 Apply the 8th translation from the Lookups panel.
Ctrl+9 Command+9 Apply the 9th translation from the Lookups panel.
Ctrl+Shift+U Command+Shift+U Add as the content as a new translation unit.
Splitting and Ctrl+Alt+I Control+Option+I Split the current segment.
merging
segments
Locking and Ctrl+L Command+L or Control+L Lock or unlock the current segment.
unlocking
segments

Ctrl+Shift+L Command+Shift+L or Lock or unlock the current selection.


Control+Shift+L
Navigation Ctrl+A Command+A or Control+A Select the entire content of the active segment.
and basic
actions
Ctrl+Up Arrow Command+Up Arrow Navigate to the previous segment.
Ctrl+Down Arrow Command+Down Arrow Navigate to the next segment.
Ctrl+ Backspace Control+Backspace Delete the previous word.
Ctrl+Delete Control+Fn+Backspace Delete the next word.
Backspace Backspace Delete the previous character.
Delete Fn+Backspace Delete the next character.
Ctrl+Right Arrow Command+Right Arrow Move cursor to next word.
Ctrl+Left Arrow Command+Left Arrow Move cursor to previous word.
Ctrl+Shift+Right Arrow Command+Shift+Right Arrow Select the word after the cursor.
Ctrl+Shift+Left Arrow Command+Shift+Left Arrow Select the word before the cursor.
Ctrl+Home Command+Fn+Left Move to the first segment in the document.
Ctrl+End Command+Fn+Right Arrow Move to the last loaded segment in the document.
Page Up Command+Fn+Up Arrow Move one page up.
Page Down Command+Fn+Down Arrow Move one page down.
Ctrl+Z Command+Z or Control+Z Undo your last action.
Ctrl+Y Command+Y or Control+Y Redo your last action (if you undid it).
Ctrl+G Control+G or Command+G Go to.
Alt+H (Not available on Mac) Show the Home tab.
Alt+R (Not available on Mac) Show the Review tab.
Alt+U (Not available on Mac) Show the Quality Assessment tab.
Alt+V (Not available on Mac) Show the View tab.
Adding Ctrl+Alt+Minus Sign Control+Option+Minus Sign Add an em dash (—) to the current segment.
symbols and
special
characters
Ctrl+Minus Sign Command+Minus Sign or Add an en dash (–) to the current segment.
Control+Minus Sign
Shift+Enter Shift+Enter Add a soft break to the current segment.
Ctrl+Shift+Space Command+Shift+Space Add a non-breaking space to the current segment.
Ctrl+Shift+C Command+Shift+C Add the copyright symbol (©) to the current segment.
Ctrl+Alt+R Control+Option+R Add the registered symbol (®) to the current segment.
Category Windows Shortcut Mac Shortcut Action
Ctrl+Alt+T Control+Option+T Add the trademark symbol (™) to the current segment.
Ctrl+Shift+E Command+Shift+E Add the euro symbol () to the current segment.
Ctrl+Shift+P Command+P or Control+P Add the pound symbol () to the current segment.
Ctrl+Shift+4 Control+Shift+4 Add German quotation marks to the current segment.
Ctrl+Shift+5 Control+Shift+5 Add English quotation marks to the current segment.
Ctrl+Shift+6 Control+Shift+6 Add angular (French) quotation marks («») to the current
segment.
Parent topic: Working with Online Editor
New project settings XML REST API endpoint
This release makes it possible to extract and amend viable settings of existing projects through the REST API.
For this, Trados GroupShare provides a new API endpoint to export the current settings of a project as a Trados project settings file (.sdlproj).
After changing the settings in the file, the file can be reimported, and the changed settings applied through the same endpoint: (GET/PUT
/api/projectserver/v2/projects/{projectId}/settingsxml. (CRQ-24649)
New endpoints for third-party developers
With this change we are adding the following new REST API endpoints. The old endpoints are still available for use, but only for previous versions
of Trados Studio.
POST: /api/projectserver/v2/projects/{projectId}/files/externalCheckOut. Calling this endpoint will check-out exclusively multiple files at
once.
POST: /api/projectserver/v2/projects/{projectId}/files/externalCheckIn. Calling this endpoint will check-in multiple files at once. This action
is restricted to the user who previously checked out the files.
POST: /api/projectserver/v2/projects/{projectId}/files/undoExternalCheckOut. Calling this endpoint will undo check-out multiple files at
once. This action requires Cancel Check Out of Other Users Project Files permission. If the user who performs this action is the user who
check-out the files, then translation is lost. Otherwise, the translation if saved.
POST: /api/projectserver/v2/projects/{projectId}/cancelPublishPackage. During project creation, this endpoint allows you to cancel the
publishing of project package to Groupshare.
GET: /api/management/v2/permissions/organizationtree?username=[encoded username]&hideImplicitLibs=[hideImplicitLibs. Calling this
endpoint will retrieve all the user permission from all organizations that this user belongs to.
Parent topic: Changes introduced in Trados Groupshare 2020 SR1 CU8
Disconnecting from Trados License Server to free up a license
seat
Disconnecting from the license server returns your license seat to the license pool. The license seat is immediately available for other network users
to activate Trados GroupShare on their computers.

Procedure
1. Run Trados GroupShare.
2. Go to Help > Product Activation to display the Product Activation dialog.
3. Select Disconnect, and then select Continue.
Parent topic: Connecting to the Trados License Manager (users)
Other enhancements
This topic encompass a diverse set of features and optimizations that aim to improve efficiency, flexibility, and user experience across different
areas of the GroupShare platform.
The target languages in the Create Translation Memory and Edit Translation Memory window are now displayed only as flags. Language
names are displayed only when hovering over the language flags, to ensure that you can use multiple target languages for the same source
language. (CRQ-32443)
You can now use language codes to search for source and target languages in the Reporting tab filter. Similarly, the New Project Template
window has been enhanced to enable you to use language codes in the Target languages field as well. Previously, this was possible only for
source languages. (LTGS-11566, LTGS-11561)
We have changed the way the language options are displayed when exporting a translation memory. After selecting the Export option in the
Translation Memories window, the language pairs available for the TM are no longer displayed as separate options, but as radio buttons
inside a single submenu. (LTGS-11599)
To ensure that new organizations stand out even in long lists of organizations, newly created organizations are now automatically selected
after creation. Similarly, when deleting an organization, the parent of the organization is now automatically selected to better show the
context for your recent change. (LTGS-11411)
Introduced a set of improvements to enhance security. (CRQ-32198, CRQ-32113, CRQ-32107, CRQ-32104, CRQ-29250, CRQ-
29244, CRQ-29120, CRQ-22386, CRQ-14752 and CRQ-34575)
Enhanced performance in the following areas:
Download native files
Download files
Finalize files
Change project status
Detach project
Publishing events (Assignment, Check-in, Check-out, Phase change, Project created etc.)
Requesting GroupShare project information from Trados Studio. (CRQ-31867)
Parent topic: Changes introduced in Trados Groupshare 2020 SR1 CU9
Working with resources
Trados GroupShare uses several resources to create and manage both shared projects and translation memories (TMs).
To create shared projects in Trados GroupShare, you must import a project template from Trados Studio.
To translate the files of a shared project you can use termbases (from MultiTerm) or server-based TMs. You can reuse several TM components
to set up other TMs:
Fields
Language resources templates including:
Variables
Segmentation rules
Recognized tokens
Translation memories (TMs)
Translation memories (TMs) store translated text which translators can reuse anytime. The ability to reuse previous translations is particularly
useful if a company has documents that are translated a number of times, in different versions, for example if similar text is used in many
documents.
Termbases
Use MultiTerm Desktop to create server termbases and add them as resources in Trados GroupShare.
Project templates
Project templates are.sdltpl files that are generated in Trados Studio from existing translation projects.
Custom fields
As a project manager or power user, you can create a list of custom fields to be used by other users.
Viewing white spaces and other non-printing characters
Viewing white spaces is particularly useful if you want to remove unnecessary non-printing characters from your text.

Procedure
1. Open the appropriate file in Online Editor.
2. On the Home tab, in the Formatting group, select Show Whitespaces.
Parent topic: Formatting segments
Activation Failed - Cannot connect to activation server
Parent topic: Error message solutions

Symptom
You are activating or deactivating a single-user license.

About this task


The following error is displayed:

Cause
About this task
You are not connected to the Internet or your proxy settings are preventing you from connecting the Activation Server.

Solution
Procedure
1. Click OK.
2. Go to Start > GroupShare [year] > GroupShare [year] Product Activation to display the Product Activation dialog.
3. In the Product Activation window, select the Alternative activation link and do one of the following:
Select Connection Settings to modify your proxy settings.
Activate or deactivate your product offline.
Removing user access to resources
When you no longer want your users to have access to organization resources, you can remove their user access permissions. Several options are
available.

About this task


Removing user access permissions requires that:
You have thorough knowledge of the permissions included under your organization's roles.
You check whether users do not have access permissions to resources in any of the roles they have.
Note: Consider that a user might have access to a resource using a resource link.
Parent topic: User permissions

Remove a role having user access permissions


By removing a role that has user access permissions, the users who are assigned that role will no longer have access to organization resources.
Examine all the roles that cover organization resources and remove those roles.

About this task


This is a drastic measure. Note that all users who are already assigned to this role will be affected by this change.

Procedure
1. Go to the Users view and select the Permissions tab.
2. Select an organization and select the role you want to delete.
3. Select .

Remove user access permissions from an existing role


By removing user access permissions from an existing role, you edit the permissions enabled by that role.

About this task


This is a drastic measure. Note that all users who are already assigned to this role will be affected by this change.

Procedure
1. Go to the Users view and select the Permissions tab.
2. Expand the Edit Roles list and select the role you want to remove permissions from.
3. In the [role name] dialog, clear the checkboxes which refer to resources.
4. Select Finish.

Remove user from role having user access permissions


By removing users from a role that has user access permissions, users no longer have access to your organization resources.

About this task


If users have several roles, each including user access permissions, remove users from all roles you see fit.

Procedure
1. Go to the Users view and select the Permissions tab.
2. Select the user's home organization (the organization in which the user was created).
3. Select the checkbox corresponding to the user's name.
4. Select Remove Users.
Translation memories (TMs)
Translation memories (TMs) store translated text which translators can reuse anytime. The ability to reuse previous translations is particularly useful
if a company has documents that are translated a number of times, in different versions, for example if similar text is used in many documents.
When you, as translator, translate some text, you can add the translation to the TM, so that later you or other translators can reuse that translation.

TMs and language pairs


The purpose of a TM is to hold text translations from one language to another language - a language pair.
In Trados GroupShare, TMs can contain multiple language pairs.
The TM divides text into segments. For each segment, the TM stores the source, the translation and other supplementary data, such as the
translation date. This collection of data that is stored for each segment is called a translation unit (TU).
Translators can use a TM to find translations for their text:
If a text segment that must be translated is the same as the source text in a TU, the TM provides an exact match translation.
If a text segment that must be translated is similar, but not identical, with the source text, the TM provides a translation based on a fuzzy
match.
Because a TM holds supplementary data for each translated segment, for example date, author and status, the translator can evaluate an offered
translation and can choose between translations offered by different TMs.
In instances where the source segment has an exact match in the TM, the translation editor can use the TM's translation text for the target segment.
As you work through your translation, you can accept or override the matches that the editor offers for your translation.
Typically, after the translation has passed some review level, the project manager enables newly translated segments to be added to the TM. In this
way, the TM is continually improved with use.
You can use more than one TM at the same time.
When you use the translation editor to translate text, the editor takes each source segment in turn and searches all the specified TMs for matches
for the source text. You can specify the order in which the editor searches the TMs, and you can also grade each TM for reliability.
GroupShare TMs and local TMs
Translation Memories (TMs) that are stored on Trados GroupShare are called Trados GroupShare TMs. TMs that are stored on the user's
computer are called local TMs.
Main TMs and project TMs
A GroupShare installation can have a number of Main TMs. For example, some installations have a TM for each subject matter area and a
TM for each of their customers.
Language Pairs
A language pair consists of a source language and a target language. A language pair has direction: English to French is not the same as
French to English.
Translation statuses
Trados GroupShare shows the translation status for each project uploaded to Trados GroupShare and for each document included in the
project.
Configuring server-based TMs
Server-based translation memories (TMs) are databases used concurrently by one or several users during the translation process. To
configure server-based TMs, you must configure several components: database servers, database containers and the translation memory-
itself.
Modifying server-based TMs
You can modify the details of server-based TMs when they no longer suit your needs.
Deleting server-based TMs
You can safely delete server-based TMs that are out-of-date or no longer relevant.
Exporting TUs from server-based TMs
You can export TUs to use them later, for instance to import them in another TM.
Importing TUs to server-based TMs
You can import TUs into an existing TM in order to update it with relevant content.
Downloading server-based TMs
Once the TUs of a server-based TM are exported, you can download the export file at a later date.
Tuning server-based TM performance
You can optimize the way your TM works in terms of speed and accuracy. Trados GroupShare performs the re-indexing and
recomputation tasks in the background, leaving you free to do other actions.
Updating TMs after project file download
You can download the translated project files in their native format and update the TMs (translation memories), during any project phase, if
you are not restricted in this regard by a user who has the Secure Project File Download permission.
TM language processing rules and recognized tokens
Translation memories (TMs) are complex databases that use a series of versatile elements catering for your translation needs.
Fields
Fields hold supplementary data for each translation unit (TU) in a TM.
Containers
Containers are server-based entities which hold TMs.
Servers
Server-based TMs need to be hosted by servers, so that they are accessed by multiple users concurrently.
Parent topic: Working with resources
Activating Trados License Manager offline
Find out how to activate a network license server using a locking code and without connecting the server to the Internet.
Activating a network license with Trados License Manager offline
After you installed the Trados License Manager, generate an Installation ID (locking code) and use it to issue an activation certificate. You
can license the server only with this activation certificate.
Removing a network license from Trados License Manager offline
You can remove the license that you added to a network server in several exceptional situations: to return unused licenses or to move a
license from one system to another.
Parent topic: Activating the Trados License Manager (administrators)
Merging segments
If the initial segmentation of a file contains source segments that were split unnaturally (perhaps as a result of improper formatting in the source text)
and that should be merged, you can correct the segmentation and merge the segments.

Before you begin


The project which the file belongs to must have the Allow editing of source text in segments setting enabled.

About this task


This feature is available for Online Editor Advanced.
You can only merge consecutive segments that are part of the same paragraph.

Procedure
1. Open the appropriate file in Online Editor.
2. Select the target area of the segment that you want to merge.
3. On the Home tab, in the Segments group, select Other Actions > Edit Source.
4. Click inside the first source segment you want merged with a consecutive segment.
5. On the Home tab, in the Segments group, select Other Actions > Merge Segments.

Results
The two segments are merged, along with their translations (if available).
Parent topic: Translating content
Details about segments and translations
These details consist in: the current status of the translation, information about whether each segment is locked or not, as well as the percentage of
the translation memory match applied to the translation.
They are displayed in the last three columns of the workspace:

If you point to the status column, the Translation details box is displayed, containing information about the status, origin, and score of the
translation:

Status
The translation status expresses the progress made with each segment:
Status Icon Description
Not Translated The segment has not been translated at all.
Draft Scenario 1: Someone has started
translating the segment. It is still a work in
progress.
Scenario 2: A translation memory match
was applied to the segment at first, but the
translation has been modified since.

Translated The segment has been translated and


confirmed.
Translation Rejected A reviewer has rejected the translation of
this segment.
Translation Approved A reviewer has approved the translation of
this segment.
Sign-off Rejected The translation of this segment has been
rejected during the sign-off process.
Signed Off The translation of this segment has been
approved and signed off.
Locked The segment is locked.

Origin
The translation origin expresses the way in which each segment has been translated:
Origin Icon This segment has been
translated by...
Interactive None. Typing text in the target
area.
Copied from Source None. Copying the source content
to the target area
(Ctrl+Insert).
100% Match Applying a translation unit
(100% match) from the
translation memory.
Context Match Applying a translation unit
(context match) from the
translation memory.
Perfect Match The surrounding text is also
checked to ensure that it is
the same as in the bilingual
file.
Origin Icon This segment has been
translated by...
Auto-propagated Auto-propagation—after
someone modified and
confirmed another segment
that was identical with the
current one.
TM with Rejected changes Matches originating from
segments that have been
translated and saved to the
TM, but whose changes
were rejected later on by a
linguistic reviewer.
Automated Translation Applying a translation unit
from an automated
translation server.
Fuzzy Match Applying a translation unit
(fuzzy match) from the
translation memory.
Neural Machine NMT
Translation This target segment has been
changed by applying a TU
from
Machine Translation.

Score
The translation score expresses the translation memory leverage of each segment:
Score Icon Description
100% , , The segment has been retrieved from a
translation memory (100% match or context
match) or auto-propagated.
Less than 100% The segment has been retrieved from a
translation memory (fuzzy match).
0% The target segment has the Draft status or the
or none at all. Automated Translation origin. No score is
displayed in the score column and 0% is
displayed as a score in the Translation details
box.
If a translation was applied from a translation memory, information about the system (translation provider) is also displayed in the Translation
details box:

Parent topic: Navigating the Online Editor user interface


Setting up execution server threads
You can specify the maximum number of execution threads permitted on the server to control resource usage.

Procedure
1. In the Trados GroupShare Console navigation tree, select SDL Trados GroupShare > Settings.
2. In the Settings pane, under Execution Server Settings, set the number of threads.
3. In the Actions pane, select Apply Changes to save the change.
Parent topic: Trados GroupShare Console settings
Updating existing translation units
While translating, you may find that some translation units (TUs) in your translation memory (TM) contain mistakes. In such cases, you can update
the existing TUs in the TM.

Procedure
1. Open the appropriate file in Online Editor.
2. Select the target segment whose translation you want to update.
3. Search for TUs and apply the appropriate translation.
4. Make the necessary changes directly in the target segment.
5. Confirm the translation.

Results
The TU is updated in the TM. These updates are also reflected in the Lookups panel.
Parent topic: Working with translation memories and terminology
Installation IDs
An installation ID is created for the computer on which you install the Trados GroupShare and is unique to each computer.
This means that after you have activated the license, you will not be able to run a copy of the licensed program on a different computer until it is
deactivated on the first computer.
Parent topic: Activating single-user licenses offline
About Perfect Match
A Perfect Match is a form of context match that compares updated source files to a corresponding set of existing bilingual files rather than to a
translation memory (TM). Segment matches, known as Perfect Matches, are checked for context, that is, the surrounding entries are checked to
ensure that they are the same.
If your existing bilingual file was segmented differently to the current file or had merged segments, Perfect Match can dynamically merge up to three
consecutive segments in your current file to improve your match results. The translations are then extracted from the existing bilingual files and
transferred to the updated source files.
Because the Perfect Match segment matching process includes a check for context and segmentation, Perfect Match units typically need no further
translation or editing during translation.

Why Use Perfect Match?


There are two scenarios where you might want to apply Perfect Match:
You have an existing Trados GroupShare project that has been fully reviewed. At the start of a project, you can base a new project on an
existing project that has been fully reviewed. This will use the translated bilingual files in the project for Perfect Match. For example, this could be
useful if you are starting translation on a technical manual for a second version of a product where the product is almost the same as the first
version.
You have an existing bilingual SDLXLIFF file available on your computer. At the start of a project, you can easily leverage translations
from project files that are no longer available on Trados GroupShare. Creating projects based on bilingual files instead of reference projects gives
you more control over which translation file is mapped to which source file.
Parent topic: Working with projects
Related tasks
Creating projects
Creating custom fields
Procedure
1. Go to the Resources view.
2. In the Custom Fields tab, select New Custom Fields.
3. In the Create Custom Fields dialog, fill in the required details:
Field Name - fill in a name for the custom field
Description - fill in a relevant description for the custom field
Organization - choose the organization that the custom field will be assigned to
Schema - select the type of input that the custom field will have
Default - fill in a default value that the user will see for the custom field value
Resource Type - select if the custom field is created for projects or project templates
Parent topic: Custom fields
Creating users
Users are defined by the roles they have within organizations. In addition to the standard users (defined by their standard roles) Trados
GroupShare allows you to create as many users as you need to organize your translation team.

Procedure
1. Go to the Users view and select the Users tab.
2. Select the organization to which you want to add the new user.
3. Select New User .
4. In the Create User wizard, fill in the account details.
5. Select Next and, in the Roles wizard section, choose which roles you want the new user to have within the organization.
6. Select Finish to create the new user and assign the selected roles.
Note: Only the System Administrator and members of the Administrator role can create, edit or delete users.
Parent topic: Users
Related concepts
User roles
User permissions
Available Trados GroupShare services
The current section enumerates the available Trados GroupShare services as they are featured in the Services pane of Trados GroupShare
Console.
SDL Application Service
SDL BCM Service
SDL Custom Properties Service
SDL Editor Service
SDL Editor Service Router
SDL Execution Service
SDL Feedback Service
SDL Fine Grained Alignment Service
SDL GroupShare WebHooks Service
SDL Language Resource Service
SDL Logging Service
SDL MultiTerm Matrix Cache Service
SDL Notification Service
SDL Reporting Service
SDL Statistics Service
SDL TM Service Host
SDL TM Service Agent
SDL Trados GroupShare Resource Management Service
SDL Translate And Analysis Service
SDL Translation Model Service Builder
SDL Translation Model Service Host
SDL Translation Service
SDL Verification Service
Parent topic: Checking service status
Automatic configuration CP-S: Authentication Server Address
The Trados GroupShare installer now automatically configures the CP-S Authentication Server Address to http://localhost:41234. As a result,
you no longer need to manually configure it for multiple installations. (LTGS-4006)
Parent topic: Changes introduced in Trados GroupShare 2020 SR1 CU6
Translating and checking in files from Trados Studio
After you finish translating the shared files in Trados Studio, you must check them back in to Trados GroupShare from Trados Studio.

About this task


After assignments are completed, users must check in their translation or review tasks performed in Trados Studio, and must move them to the
next file phase from the same Trados Studio. Make sure that the users who check in their assignments have the correct permissions to change the
file phases, namely Change Current Phase and Change Any Phase. Assign users the appropriate roles or adjust the permissions associated to
their roles before users reach this project step.

Procedure
1. Open your Trados GroupShare assigned files in Trados Studio.
2. In Trados Studio, in the Files view, select the file you want to check out.
Important: You cannot check out from Online Editor files which are already checked out in Trados Studio. Wait until the file is checked in
from Trados Studio before you check-it out (open) in Online Editor.
3. On the Home tab, select Check out.
4. On the Home tab, select one of the following: Open for Translation, Open for Review, Open for Sign-Off, depending on your assigned
tasks and project phase.
5. Start working on the file.
All the segments which were pre-translated based on similar, previously translated projects (namely, based on the PerfectMatch
functionality), are displayed as locked and signed-off. You can still edit them, if needed.
6. When finished, in the Files view, select the file you want to check in.
7. On the Home tab, select Check in.
8. Expand Change Phase and select the next phase the document should go to.
Note: If there are users already assigned to work on the file in the new phase, Trados GroupShare sends these users a phase change
notification email and updates the information in the Current Phase column of the Trados GroupShare application.
Parent topic: File translation and check-in
Removing a network license from Trados License Manager
Manager online
You can remove the license that you added to a network server in several exceptional situations: to return unused licenses or to move a license
from one system to another.

Procedure
1. Open License Server Manager, and select the Deactivate option.
2. In the activated product licenses list, search for the product you wish to deactivate.
3. Select the Deactivate All button to deactivate all the product keys corresponding to a product. Due to restrictions of the licensing system, it
is not possible to only deactivate one product key. You will have to deactivate all product keys for a certain product, and then re-activate
the ones you wish to keep.
Your license will be deactivated on the server and the used seats will be returned.
Parent topic: Activating Trados License Manager online
Moving single-user license to another computer via Internet
To deactivate Trados GroupShare online, you must be connected to the Internet.

Procedure
1. Go to Start > GroupShare [year] > GroupShare [year] Product Activation to display the Product Activation dialog.
2. Select Deactivate.
3. A prompt is displayed asking if you want to deactivate Trados GroupShare. Select Yes. A message is displayed indicating that the
deactivation was successful.
4. Activate Trados GroupShare on the new computer.
Parent topic: Moving single-user license to another computer
Server security configuration recommendations
Follow the steps covered in some or all of the following sections to make sure your Trados GroupShare server is as secure as possible. Each
section covers a specific area.

Authentication Method
Our general recommendation is to use one of the following primary authentication methods: Windows Authentication, SAML v2
Authentication or JWT Authentication, even though SDL Authentication is an option as well. This will allow using sophisticated account
lockout options available in the dedicated identity and authentication services.

System Security
We recommend the system administrators to implement an anti-virus solution to perform a scan before uploading or further using the files in
translation projects and resources.
Database authentication
When connecting to the database server, we strongly recommend using Windows authentication over of SQL-based authentication. With SQL
authentication, the username and password credentials to access the database are visible in clear text in the configuration file. With Windows
Authentication the credentials are not specifically embedded in the file, which means that they cannot be accessed in case someone gains access to
your configuration file.

Enable HTTP Strict Transport Security (HSTS)


To check that HSTS is enabled in IIS Manager:
1. Access the IIS Web Server.
2. Open IIS Manager.
3. Expand the Sites section and click SDL Server.
4. Click on HSTS.
5. Verify that Enable is checked, and Max-Age is set to something other than 0.

The HSTS Policy is communicated by the server to the user agent via an HTTP response header field named Strict-Transport-Security. HSTS
Policy specifies a period of time during which the user agent should only access the server in a secure fashion. Check the response headers to see
if the strict-transport-security field is present.

Redirect HTTP to HTTPS


To redirect HTTP to HTTPS:
1. Add a redirect ruleconfigured in the website web.config file located under SDL Server\Web\web.config
<rule name="Redirect HTTP to HTTPS" stopProcessing="true">
<match url="(.*)" />
<conditions>
<add input="{HTTPS}" pattern="off" />
</conditions>
<action type="Redirect" url="https://{HTTP_HOST}/{R:1}" redirectType="Permanent" />
</rule>
2. Open Developer Tools and take the link to any resource, for example a font, an image, etc.
3. Copy the link and paste it in a new tab, changing the protocol from HTTPS to HTTP. You should see a redirect happening.

Disable Tomcat default page


This setting is a one-time configuration and it is generally not required after an upgrade.
To disable Tomcat default page:
1. Navigate to C:\Program Files\Apache Software Foundation\Tomcat 9.0\conf
2. Open the web.xml file and comment out the following section:
<welcome-file-list>
<welcome-file>index.html</welcome-file>
<welcome-file>index.htm</welcome-file>
<welcome-file>index.jsp</welcome-file>
</welcome-file-list>

Note: If you disable index.jsp you will need to specify that in the URL when loading MultiTerm Online. We do not recommend this as it can lead
to unexpected issues. The other two entries can be commented out as they are not used.

Disable deprecated TLS and SSL versions


This setting is a one-time configuration and it is generally not required after an upgrade.
Navigate to your system's Key Registry. We recommend consulting docs.microsoft.com on how to do so depending on your system.
Check that the following keys are present and set to:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Client]
"DisabledByDefault"=dword:00000001
"Enabled"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Server]
"DisabledByDefault"=dword:00000001
"Enabled"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0\Client]

"DisabledByDefault"=dword:00000001
"Enabled"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 3.0\Server]
"DisabledByDefault"=dword:00000001
"Enabled"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Client]
"DisabledByDefault"=dword:00000001
"Enabled"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server]

"DisabledByDefault"=dword:00000001
"Enabled"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Client]
"DisabledByDefault"=dword:00000001
"Enabled"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server]
"DisabledByDefault"=dword:00000001
"Enabled"=dword:00000000

Path traversal fix for MultiTerm Online (MTO)


Path traversal vulnerability in IIS should not reproduce if RequestFilteringModule and UrlRoutingModule modules are enabled. For GroupShare
this is enabled by default.
This is not the case for MTO.
You can see this by accessing https://<domain>/multiterm/..;x=x/ which displays Tomcat's default page.
If MultiTerm Online is routed through IIS this can be fixed with request filtering:
1. Go to Request Filtering in IIS Manager under SDL Server.
2. Add a new "Deny Sequence" URL rule to deny the character sequence ".." in the URL.
After the rule is added accessing https://<domain>/multiterm/..;x=x or any other URL that has ".." in it will return HTTP 404 error.

Enable HSTS for MTO


1. Navigate to C:\Program Files\Apache Software Foundation\Tomcat 9.0\conf and open the web.xml file.
2. Edit the HttpHeaderSecurity filter as follows:
<filter>
<filter-name>httpHeaderSecurity</filter-name>
<filter-class>org.apache.catalina.filters.HttpHeaderSecurityFilter</filter-class>
<async-supported>true</async-supported>
<init-param>
<param-name>hstsEnabled</param-name>
<param-value>true</param-value>
</init-param>
<init-param>
<param-name>hstsMaxAgeSeconds</param-name>
<param-value>31536000</param-value>
</init-param><init-param>
<param-name>antiClickJackingOption</param-name>
<param-value>SAMEORIGIN</param-value>
</init-param>
</filter>

3. Set the antiClickJackingOption parameter using the value SAMEORIGIN, otherwise, pages that contain iFrame can stop working after
enabling HSTS.
4. Ensure the <async-supported> line is always above the <init-param> ones as shown in the example above. Otherwise you may hit XML
validation erros if that is enabled directly on the context or by the system ropertySTRICT_SERVLET_COMPLIANCE.
5. Uncomment the following section:
<filter-name>httpHeaderSecurity</filter-name>
<url-pattern>/*</url-pattern>
<dispatcher>REQUEST</dispatcher>
</filter-mapping>

MTO security constraint configuration


1. Navigate to C:\Program Files\Apache Software Foundation\Tomcat 9.0\webapps\multiterm\WEB-INF
2. Open the web.xml file.
3. Add the following section:
<security-constraint>
<web-resource-collection>
<web-resource-name>twx-portal</web-resource-name>
<url-pattern>/*</url-pattern>
</web-resource-collection>
<user-data-constraint>
<transport-guarantee>CONFIDENTIAL</transport-guarantee>
</user-data-constraint>
</security-constraint>

Enable IIS secure cookies


1. Navigate to SDL Server\Web
2. Open the web.config file
3. Add the httpCookies node as following:
<system.web>
...
<httpCookies httpOnlyCookies="true" requireSSL="true" />
...
4. Add a redirect rule for secure cookies in web.config
<system.webServer>
<rewrite>
<outboundRules>
<rule name="Use only secure cookies" preCondition="Unsecured cookie">
<match serverVariable="RESPONSE_SET_COOKIE" pattern=".*" negate="false" />
<action type="Rewrite" value="{R:0}; secure" />
</rule>
<preConditions>
<preCondition name="Unsecured cookie">
<add input="{RESPONSE_SET_COOKIE}" pattern="." />
<add input="{RESPONSE_SET_COOKIE}" pattern="; secure" negate="true" />
</preCondition>
</preConditions>
</outboundRules>
</rewrite>
</system.webServer>

Alternatively, you can adjust the script under C:\ProgramData\Package Cache\SDL\TradosGroupShare2020\SecureCookie.ps1 ($configPath
= 'W:\SDL\SDL Server\Web\web.config') and run it as admin.
Parent topic: Securing your Trados GroupShare webserver
Project archiving
Users with Edit Project permission can archive a project or restore an archived project from the Trados GroupShare web interface. Users with
the Delete Project permission (by default, Administrator, Power User and Project Manager accounts) can detach a project from Trados
GroupShare's database.
When the Enable automatic Project Archiving option is selected in Trados GroupShare Console, Trados GroupShare executes an automated
nightly task to archive projects that are in the Completed status for more than the number of days set up in the Trados GroupShare Console.
Archiving completed projects
You can reduce the list which displays all the Trados GroupShare projects by archiving the ones which are completed and are not
imminently needed anymore. Archived projects can be restored at a later date, if necessary.
Restoring archived projects
You can restore archived projects, if necessary. When Trados Studio connects to a Trados GroupShare server, it no longer displays
archived projects into its Projects view, thus improving overall performance and productivity.
Detaching completed projects
Trados GroupShare projects can be fully removed from the system. Unlike archiving, detaching removes all traces of the project from the
server.
Parent topic: Working with projects
Activating single-user licenses offline
Installation IDs
An installation ID is created for the computer on which you install the Trados GroupShare and is unique to each computer.
Activation certificate
You are prompted to enter an activation certificate when you activate your product and do not have an Internet connection on the computer
where Trados GroupShare is installed. An activation certificate incorporates all of the details which would normally be downloaded from the
Activation Server during an online activation.
Activating your product offline with a single-user license
If you are not able to access the Internet from the computer on which you installed Trados GroupShare or if your firewall prevents you from
performing online activation, you can modify your proxy settings or use offline activation to license Trados GroupShare.
Deactivating your product offline with a single-user license
To deactivate Trados GroupShare when you have no Internet connection, you need to use another computer with Internet access to the
RWS website where you can return the deactivation certificate.
Viewing your deactivation certificate offline for a single-user license
Deactivation certificates are generated when you deactivate offline. You then return the deactivation certificate to the Activation Server.
Until you return the certificate, you will not be able to activate Trados GroupShare on the same machine or another machine with the same
activation code.
Parent topic: Single-user licenses
Creating organizations
Every Trados GroupShare installation sets a unique Root Organization by default. You can add as many organizations to the Root Organization.
Then, you can continue adding as many sub-organizations to these organizations.

Procedure
1. Go to the Users view.
2. Select the Root Organization or the organization under which you want to create a (sub-)organization.
3. Select + Organization.
4. In the Add Organization dialog:
a. Type a name for your organization.
b. Optionally, enter a description.
c. Optionally, to give your organization library status, select Is Library.
5. Select Finish.
Parent topic: Organizations and their components
Blurring or hiding unfiltered translations
If you start translating a segment and you want to see whether there are translations in the translation memory that start with the text you entered,
you can do so by blurring or hiding the translations that do not match that text.

Procedure
1. Open the appropriate file in Online Editor.
2. Enter some text in the target segment of your choice.
3. While searching for translation memory matches, on the View tab, in the Lookups group, do one of the following:
To blur the translations that do not start with that text, select Filter Lookups > Blur mismatches.
To hide the translations that do not start with that text, select Filter Lookups > Hide mismatches.
To see all the available translations for that segment, select Filter Lookups > Show All.
Parent topic: Working with translation memories and terminology
Downloading translated project files
You can download the translated project files in their native format, during any project phase, if you are not restricted in this regard by a user who
has the Secure Project File Download permission.

About this task


To restrict the download of project files to some users, users must be assigned a role which has the Secure Project File Download permission. The
Secure Project File Download permission is assigned to the following roles by default: Administrator, Power User and Project Manager. During
project creation, users in these roles must select the Prevent file downloads for this project checkbox, which means that only users with the Secure
Project File Download permission will be able to download the source project files and the translated project files.

Procedure
1. In the Projects view, select the project whose translated files you want to download in their native format.
2. In the project tab, do one of the following:
Select Download all files > Download preview for all target files.
Select the checkboxes corresponding to the files you want to download and select selected files > preview of target version for
selected files.
3. Save the document(s) as a zip archive on a location of your choice.
Parent topic: Project management
Removing resource links
When you want to deny users from other organizations access to your resource, you must remove the resource link.

Procedure
1. Go to the Users view and select the Content tab.
2. Select the organization where the resource link is located.
3. Select Unlink Resource.
Parent topic: Resource Links
Editing users
When no longer up-to-date, the users' account details or assigned roles can be modified to reflect the permissions they are intended to have in
Trados GroupShare.

Procedure
1. Go to the Users view and select the Users tab.
2. Select an organization and then select the user you want to edit.
Tip: Alternatively, you can select the checkbox corresponding to the user whose details you want to edit.
3. Edit the account information, profile picture, or the assigned roles specified for the user.
Parent topic: Users

Update profile pictures


About this task
By default, SDL Trados GroupShare uses a default avatar as your profile picture, showing your initials on a colored background. To personalize
your profile, upload a custom picture in one of the following formats: *.PNG, *JPG or .*GIF.
Your profile picture is visible to other users and is displayed next to the projects and files you are assigned to. If you are a system administrator or
a project manager and you want to update the profile pictures of other users in your account, see Editing users instructions above.
To update your profile picture:

Procedure
1. Click on your user icon in the top-right corner of your screen.
2. In the drop-down menu, select Manage Account.
3. On the Contact information page, click Upload image > Select an image file.
4. Browse to the picture file that you want to insert and click Open.
5. Once your picture is uploaded, drag the corners of the grid to crop the photo and click Save.
6. Click Finish to close the Contact information page.
7. Refresh your browser to make sure your photo has been updated.

Delete current profile photo


If you want to delete your current profile photo, go back to Manage Account > Contact information page and click Remove image.
Change user passwords
You cannot edit the password for users created using their Windows details.
For information on specifying the minimum requirements for the passwords users can create or change, see Customize password complexity rules.
Returning a borrowed network license to Trados GroupShare
If you borrow a network license, you can return it before the borrowing period expires or after the expiry date is reached. If you do not return
your license, it will not be available for use by other users, even if the license expired.

Before you begin


You need to be able to connect to the license server.

Procedure
1. Go to HelpProduct Activation to display the Product Activation dialog.
2. On the Product Activation page, select Return.
The license will now be available for use by other users.
Parent topic: Connecting to the Trados License Manager (users)
Overwriting content in segments
If you copy the content of source segments to target segments, you do not need to delete all the copied content when you start translating; you can
simply overwrite it.

Enable Overwrite mode


To turn on content overwriting, click the segment whose content you want to overwrite and press Insert.

What does Overwrite mode do?


Overwrite writes over existing text when you start typing.
Overwrite inserts revisions if Track Changes is enabled.

What doesn't Overwrite do?


Overwrite does not affect locked content.
Overwrite does not affect revision content if Track Changes is disabled.
Parent topic: Translating content
What's new in Trados GroupShare
This section provides an overview of features and functionality introduced or changed in Trados GroupShare over time.
Changes introduced in Trados Groupshare 2020 SR1 CU9
This page contains an overview of the new features and fixes brought by Cumulative Update 9 for our latest major release, Trados
GroupShare 2020 SR1.
Changes introduced in Trados Groupshare 2020 SR1 CU8
This page contains an overview of the new features and fixed brought by Cumulative Update 8 for our latest major release, Trados
GroupShare 2020 SR1.
Changes introduced in Trados GroupShare 2020 SR1 CU7
This page contains an overview of the new features and fixed brought by Cumulative Update 7 for our latest major release, Trados
GroupShare 2020 SR1.
Changes introduced in Trados GroupShare 2020 SR1 CU6
This page contains an overview of the new features and fixed brought by Cumulative Update 6 to our latest major release, Trados
GroupShare 2020 SR1.
Changes introduced in Trados GroupShare 2020 SR1
This section contains a list of new features and functionality that were introduced with the Trados GroupShare 2020 SR1 release.
Changes introduced in SDL Trados GroupShare 2020
This section provides an overview of the new features, enhancements and other changes introduced in the 2020 version of Trados
GroupShare.
Parent topic: Release notes
Viewing project settings
You can access and manage the project settings if you are assigned the Edit Project permission.

Procedure
1. Go to the Projects view and, in the All projects tab, view the list of all available projects and their details.
2. Select a project to view its details in the project tab.
3. Select Project Settings and consult the available pages: General Settings, Language Pairs, Translation Memories, Termbases, PerfectMatch,
Custom fields.
Parent topic: Project settings
Checking GroupShare logs
Check the event logs to monitor GroupShare process executions, and trace possible issues.

Location of event logs


Each Trados GroupShare service generates its own .LOG file under ....\Program Data\SDL\Service\Logs. In addition, the Trados GroupShare
installation logs are available under ....\Program Data\SDL\Install\SDL GrouShare version number.log
All the information from these separate log files is consolidated in one single location in the Trados GroupShare UI, under System Configuration >
Log Viewer. Here you can examine all log events from a central location, without accessing the Trados GroupShare server, and without opening
multiple .LOG files.

Log Viewer and Logging Service


The SDL Logging Service collects and records all the information from the .LOG files in the Trados GroupShare log database. This information
feeds in the Log Viewer tab where you can sort and analyze log entries more efficiently.
By default, log entries in the Trados GroupShare log database are deleted every 15 days, at 22:30. You can customize this purge frequency by
configuring the CleanUpSettings property in the Appsettings.json file available under ...\SDL\Install\SDL Server\Logging Service.

Required permission
By default only the System Administrator can access the Log Viewer tab. However, you can enable any other user to access the logs by granting
them the View Log Entries permission.

Filter log events


Sort and filter logged events in the Log Viewer to identify relevant log data easier, and troubleshoot issues quicker.
To filter log events in the Log Viewer:
1. Go to System Configuration > Log Viewer tab, and open the Filter pane at the left hand-side of the screen.
2. Specify the period of time and the Trados GroupShare service for which you want to see the logs events.
3. Enable the type of log events that you want to see in the Log Viewer.

Configure event level recording


By default, Trados GroupShare records all Information, Warning and Error events in the .LOG files on the Trados GroupShare server. The
Logging Service only records Warning and Error log events in the log database.
To configure the default log level for the .LOG files and for the Log Viewer, edit the .CONFIG file for each Trados GroupShare service.
Parent topic: Installing Trados GroupShare
Containers
Containers are server-based entities which hold TMs.
A default container is automatically generated for your organization when installing Trados GroupShare. You can add and register other containers
as well if you are assigned an Administrator role or if your role includes the View Infrastructure permission.
Adding containers
Upon Trados GroupShare installation, a default container is set. Depending on your needs and the complexity of your organization, you can
add as many containers as you need. Containers must be added before creating TMs. One container can support several TMs.
Modifying container details
You can update a container's name and description.
Deleting containers
You can delete containers, but this means that you will no longer have access to the TMs they host.
Parent topic: Translation memories (TMs)
Revision modes
Whether you are reviewing a translation or integrating reviews in your translation, there are multiple ways in which you can view the revisions made
with tracked changes.
Revision modes are especially useful for previewing purposes and have no impact on the actual content of the revisions. For example, if you
choose a revision mode that displays changes as accepted, this does not mean that the changes are accepted in the target document, only that they
are displayed as such.
You can choose between the following revision modes:
Original: The file is displayed in the workspace with all the revisions rejected.
Final: The file is displayed in the workspace with all the revisions accepted.
All Markup: All the revisions are displayed in the workspace. This mode is selected by default when you enable change tracking.
To choose how revisions are displayed, on the Review tab, select Revision Mode, and then select the mode of your choice.
Parent topic: Reviewing translated content
Fixed issues
The following list details the issues that were resolved in the Trados GroupShare 2020 SR1 CU9 release.

Core functionality
When using the Language Weaver translation provider, the RequiresSecureProtocol setting is respected. This is a setting stored with
the project template, which you can configure from Trados Studio. If the setting is set to False, Trados GroupShare will connect to the
machine translation server using an HTTP connection. If set to True, an HTTPS connection will be required. (LTGS-11211)
For server-based TMs, the Pre-Translate batch task would not apply available context matches on translation units with existing content in
the target segment. This issue is now fixed. (CRQ-31167, CRQ-33362)
Fixed an issue where the Permissions tab took too long to respond or timed-out trying to display user names that started with a number.
(CRQ-28322)
Filtering TMs by field name ID failed with a 'The TM May contain Invalid Translation Units' error. The issue is now fixed. (CRQ-
26275)
Fixed 'request is invalid' error that occurred when typing in the Organization search field under Resources > Termbases. (CRQ-24309)
TMs from exported project packages used different settings than the main TM used in the project. This caused errors when importing the
return package. The issue is now fixed. (CRQ-32901)
Project TMs associated with detached projects can now be correctly deleted. (CRQ-24021)
Updated the GroupShare installer's behavior so that it doesn't conflict with IIS Rewrite Module whenever IIS Rewrite Module 2.1 or any
newer version is already installed. This would previously result in an error. (CRQ-23804)
Deleted users are now correctly removed from current assignments. (LTGS-10433)
The System value in the translation details would incorrectly display 'SDL GroupShare ETS TranslationProvider' instead of 'Language
Weaver Edge', and 'SDL MT Cloud Translation' instead of 'Language Weaver Cloud'.' These issues are now fixed. (LTGS-11380,
LTGS-11297)
Deleting organizations failed on environments with TM Server-only and MultiTermServer-only. The issue is now fixed. (LTGS-11157)

MultiTerm Online
Added missing HttpOnly flag to cookies used by MultiTerm Online. This was done using outbound rules in IIS, hence it applies to
MultiTerm Online only if it's routed through IIS. (CRQ-29120)
Importing .ZIP files with XML content for termbases would result in a 'Zipping output data failed. Check paths and output data.'' error.
The issue is now fixed. (CRQ-21834)
MultiTerm Online failed to display multimedia fields when creating a termbase with multimedia objects. The issue is now fixed. (CRQ-
31195)
The global Show Edit buttons on the toolbar option in the Administration Overview would be automatically disabled when a user without the
Edit Without Input Model permission would try to edit a termbase that used an input model. This option is now correcly disabled only for
specific users who lack this permission. (CRQ-34236)
Projects with Memsource XLIFF files are now successfully created and published. (LTGS-11563)
The Rest Request API/projectserver/v2/projects/{projectId} now returns the correct OrganizationPath in the response. (LTGS-
11069)
Fixed display issues with PickList values in MultiTerm Online termbases:
Multiple PickList values are now correctly displayed on separate rows. (CRQ-30860)
PickList values are now correctly displayed under the drop-down menu. (CRQ-30842)

Online Editor
Fixed issue that occurred when using Lookup in segments with track changes. (CRQ-32316)
The 'CTRL +' shortcut in the Online Editor would only insert Do Not Translate tags when the source segments included such tags. The
issue is now fixed. (CRQ-31393)
Fixed an issue where adding or editing emojis in target segments failed with different errors. (LTGS-9828)
Fixed Verify Segment issue that occurred on Spanish and German OS. (LTGS-10513)
Accepting or Rejecting parts of a revision affected the entire revision. This issue is now fixed. (CRQ-29389)
The Segments with comments filter now works as expected. (CRQ-32330)
Comments now correctly use the location type 'Segment' when a range comment encloses the entire segment content. (LCC-14733)
The Navigation panel would sometimes keep search results from previous searches. This issue is now fixed. (LCC-12890)
Username in the Comments panel is now displayed as expected. (LCC-14807)
Fragment matches results are now correctly highlighted in source segments. (LCC-9329)
Words defined as using a wrong form in Word list settings are now correctly indicated in the Messages window with error or warning icons.
(CRQ-28858)
Fixed 'Invalid segment' error in the Navigation that would sometimes occur when using filters. (CRQ-32863)
Fixed 'A segment is edited by another user' error that incorrectly occurred when two different users were working on the same file for
different target languages. (CRQ-31735)
Scrolling down fast through segments now loads content as expected and no longer shows a 'Retrieving more content' message. (CRQ-
32659)
Parent topic: Changes introduced in Trados Groupshare 2020 SR1 CU9
Modifying server-based TMs
You can modify the details of server-based TMs when they no longer suit your needs.

Procedure
1. Go to the Resources view.
2. In the Translation Memories tab, select the checkbox for the TM whose details you want to modify.
3. Select Edit.
4. In the [TM name] dialog, go through all the pages and make the necessary changes.
5. Select Finish.
Parent topic: Translation memories (TMs)
Viewing formatting tags
By viewing formatting tags, you can see information about how source segments are formatted. This is also useful if you want to copy tag pairs
from the source segment to the target segment.

Procedure
1. Open the appropriate file in Online Editor.
2. On the View tab, in the Tags group, select Show Formatting Tags.
Parent topic: Formatting segments
Opening files in Online Editor
Use the Online Editor to open files that you want to translate or review online. You can only open one file at a time. You can open files from the
Trados GroupShare interface or from the file-name link in the email notification you receive upon file assignment.

Procedure
1. Do one of the following:
Click the file-name link in the notification email to open your Trados GroupShare assigned documents in Online Editor.
Log in to Trados GroupShare, go to Dashboard, and, under Your Tasks, select near the assignment you want to work on.
Log in to Trados GroupShare, go to Projects, select the project where the assignment is stored, select the checkbox next to the file
you want to work on, and then select Open in Editor.
Important: You cannot check out from Online Editor files which are already checked out in Trados Studio. Wait until the file is checked in
from Trados Studio before you check-it out (open it) in Online Editor.
The file automatically opens in Online Editor and is ready for editing.
2. Edit the file in Online Editor.

Results
The file is opened in Online Editor in a new browser tab.
Parent topic: Working with Online Editor
MultiTerm and Trados GroupShare
MultiTerm Server is a repository for MultiTerm objects including termbases and catalog objects.
Trados GroupShare gives MultiTerm access to all the users who are members of a Trados GroupShare role. However, the level of access to
MultiTerm termbases is controlled by the rights granted in MultiTerm. MultiTerm Administrator can be accessed via MultiTerm Desktop .
Parent topic: Organizations and their components
Network License errors - Retry button
Parent topic: Error message solutions

Symptom
When you try to open Trados GroupShare or are currently working in Trados GroupShare, the Product Activation dialog is displayed with a Retry
button. The error displayed will vary depending on the problem.

About this task


The following message is displayed:

Cause
About this task
The Retry button is displayed for a network license when a request to the server is made for a license and it is unable to obtain the license for one
of the following reasons:
There are currently no available network licenses to use because other users are using them. If there are no more seats left another explicit
message is displayed.
The license server information has changed, so your details are no longer correct.
The license server is not available.
You are not connected to the network.

Solution
About this task
Do one of the following:
Select Retry to attempt to request the license again.
Select Change License Server to display the check or change your license server details.
Select Disconnect to connect using a single-user license instead.
If you are having network problems or the license server is not available, contact your network administrator to help re-establish your
network connection or to check if the license server is still running.
Modifying server details
You can modify the details of server that need adjustment.

Procedure
1. Go to the System Configuration view.
2. In the Servers tab, select the checkbox corresponding to the servers you want to edit.
3. Select Edit.
4. Make the necessary changes.
5. Select Finish.
Parent topic: Servers
Known issues in Online Editor
Consult the list of known issues and limitations.
Opening a file for review with Track Changes on via Google Chrome results in Google Chrome overriding the revision formatting performed
in Online Editor. Consult this KB article to learn how to troubleshoot this behavior.
Parent topic: Working with Online Editor
Tag messages in the Verification panel
This topic lists the verification messages triggered when tag differences are identified after the automatic comparison of source segments and target
segments.

No. Tag verification message Description Default error severity


1. TagsAdded There are more tags in the target segment than in the source Error
segment.
2. TagsDeleted There are fewer tags in the target segment than in the source Error
segment.
3. TagsMoved The order of target tags is different than the order of source Warning
tags.
4. TagSpacing The spacing around target tags is not the same as the spacing Note
around source tags.
Parent topic: Checking verification results
Segmentation rules
Segmentation rules define how a translation memory (TM) or a project divides source text into segments.
Segmentation rules are customizable language resources, defined by the regular expressions that specify a segment. Often a segment is identical to
a sentence, in which case the regular expression specifies the text patterns that constitute a sentence.
The definition of a segment break is defined in two parts:
Before break: A pattern for the text immediately before the segment break.
After break: Another pattern of text that defines the text immediately following the break.
A segment break is created only if some text matches the before break pattern and is immediately followed by text that matches after break
pattern.

Multiple rules
You might want a number of segmentation rules, for example, one rule to define the segmentation where there is a colon, and another rule to cover
the case where there is a period.
In any one project, for the same language pair, you can use multiple (main) TMs with different segmentation rules.

Other language resources that affect segmentation


List of Abbreviations - The list contains abbreviations that finish with a period (.), for example, etc. The period at the end of etc. does not
necessarily mark the end of a sentence, though it might do so, by chance.
List of Ordinal followers - Like abbreviations, ordinal followers provide cases where a period does not necessarily mark the end of a
segment: when followed by some nouns, a set of digits followed by a period (for example 23.) signifies the ordinal (23rd), not the end of a
sentence. For example 23. April, can mean 23rd April.

Rules specifying exceptions


In addition, even if the text does satisfy these rules, if the text also matches the exception rules, a segment break is not created. You might want to
define an exception to cater for the use of a period in a sentence, for example:
You should not use periods (.) in file names.
Segmentation process overview
Segmentation settings define how a translation memory (TM) or a project divides source text into segments.
Example of a segmentation rule
The following rule is used as an exception to the segmentation rule that defines a segment demarcated by a period (full stop).
Specifying segmentation rules
You can customize the segmentation rules that parse your translation memory (TM), in order to adapt the TM to your translation goals.
Parent topic: TM language processing rules and recognized tokens
Activating licensing
Trados GroupShare is licensed using a single-user license. A single-user license can have several 'seats' that can be used within that one license.

Procedure
1. In the Trados GroupShare Console navigation tree, select SDL Trados GroupShare > Settings.
2. In the Actions pane, select Launch Product Activation Tool.
3. Select Activate.
4. Enter an activation code.
Parent topic: Trados GroupShare Console
Rejecting revisions
After you receive a reviewed file, you can directly reject the revisions you do not agree with.

Procedure
1. Open the appropriate file in Online Editor.
2. Find the revision that you want to reject and select it.
3. On the Review tab, in the Tracking group, select Reject.
4. Optional: To reject all the revisions at once, on the right side of the screen, select the Revisions panel, and then select Reject All.
Parent topic: Reviewing translated content
Welcome to the Trados GroupShare 2020 SR1 documentation
Trados GroupShare is a collaboration platform for translation teams. Trados GroupShare enables project managers, translators and reviewers to
work simultaneously, from different locations, on the same translation project. Users can share project files, terminology and translation memories
simply and securely.
In this documentation portal, you can find resources on installing and using Trados GroupShare 2020 SR1.
Customer support
To contact Technical Support, connect to the Customer Support Web Portal at https://gateway.sdl.com/ and log a case for your RWS
product. You need an account to log a case. If you do not have an account, contact your company's RWS Support Account Administrator.
Support articles
You can find a large collection of support articles in the Knowledge Base.
Acknowledgments
Trados GroupShare 2020 SR2 CU9 includes the following open-source, licensed or similar third-party software:
Legal notice
Copyright and trademark information relating to this product release.
Change log
This is a list of changes made to the Trados GroupShare documentation portal since its official release on June 15, 2020.
Sending a help topic
Copy the last link in a breadcrumb trail to send a help link.
REST API information
REST API information is hosted in Swagger. The information can be used interactively to learn more about the actions that can be
performed on projects, translation memories, termbases and any other resources.
GroupShare kit
The kit includes two types of available information: .NET library for Trados GroupShare REST API and TM Search and Terminology
Editing using REST API.
GUID-CA108A42-2DE7-43F7-B7DE-2F77DA92E2B7.html
Activation Failed - The license is already registered
Parent topic: Error message solutions

Symptom
You are activating a single-user license.

About this task


You enter an activation code and the following error is displayed:

Cause 1: The activation code is used by you on another computer


Solution 1: Deactivate the product on the other computer
Before you begin
To deactivate your product online, you need Internet access. If for some reason it cannot access the Activation Server, it will prompt you to
perform an offline deactivation.

Procedure
1. Go to Start > GroupShare [year] > GroupShare [year] Product Activation to display the Product Activation dialog.
2. In the Product Activation dialog, select Deactivate.
3. A prompt is displayed asking if you want to deactivate your product. Select Yes.
4. You can now activate your product on another computer.

Cause 2: Another user is using this activation code


Solution 2: Check that you have the correct activation code from your account.
Cause 3: You deactivated offline but did not return the deactivation certificate
About this task
You deactivated offline and removed the activation code on your computer but did not log onto your My Account and return the deactivation
certificate (license). Therefore, the license is still considered as 'in use' on the Activation Server.

Solution 3: Return the deactivation certificate (license) on your account


About this task
Deactivate your product offline.
After you return the license it can be activated again with a different installation of the software.

Further Troubleshooting
About this task
For further troubleshooting information, visit the Solution Finder.
Updated documentation
Documentation is now more detailed.
We have updated the documentation with detailed Recommendations for configuring Server security. In addition, the installation Guide now
includes instructions for Automatic assignment of user roles in SSO login flows.
Parent topic: Changes introduced in Trados GroupShare 2020 SR1 CU7
Configuring available product editions
As a network-licensing administrator, you can configure what product editions are available to a client user when they try to connect to the license
server. The information in this topic is relevant to you if you have multiple commuter licenses activated on the same license.
Parent topic: Activating the Trados License Manager (administrators)

Reset the network license configuration file to default


About this task
You might want to re-generate the network license configuration file if it gets corrupted or you want the default settings in place.

Procedure
1. On the client machine, go to Help > Product Activation.
2. In the Product Activation dialog, select Activate > Alternative activation options > Use a License Server.
3. Fill in the server name and select Connect.
4. On the multiple license selection page, select the CTRL + F12 key combination to re-create the default network license configuration file.
Modifying revisions
You can modify your revisions if they are no longer relevant. To modify other users' revisions, you must enable Track Changes first.

Procedure
1. Open the appropriate file in Online Editor.
2. Select the Revisions panel.
3. Find the revision that you want to modify.
If it is your revision (edited in the current session), edit it.
If it is a revision added by another user, go to the Review tab, select Track Changes to enable it, and then edit the revision. In the
Revisions panel, check each revision. If you add something, the word Inserted is placed after the user who made the change. If you
delete something, the word Deleted is placed after the user who made the change.
Parent topic: Reviewing translated content
Creating project templates
Project templates are used in Trados GroupShare when creating projects from the web interface.

Before you begin


This is not mandatory, but you can use an Trados Studio project template file (*.sdltpl) to base your Trados GroupShare project template on.
Uploading an *.sdltpl file will populate the wizard with the data from the template file.
See the Trados Studio 2022 SR1 Help for information on how to use Trados Studio to create an *.sdltpl file.

Procedure
1. Go to the Resources view.
2. In the Project Templates tab, select New Project Template.
3. In the General Settings page of the New Project Template wizard:
a. Type a name, and, optionally, a description for your project template.
b. Choose a location for the project template in your organization.
c. Browse for your template file.
4. Select Next
5. In the Language Pairs page of the New Project Template wizard, select a source language and one or more target languages.
6. You can select Finish to save the project template or select Next to continue the wizard with adding translation memories (TMs) or
termbases.
7. In the Translation Memories page of the New Project Template wizard:
under All language pairs, select a TM from the ones available in your organization to use for all your language pairs
under Specific Language Pairs, select a specific TM from the ones available in your organization to use for a specific language pair.
8. In the Termbases page of the New Project Template wizard, select a termbase from the ones available in your organization.
9. Select Finish.
Parent topic: Project templates
Related concepts
File assignment security
File assignment notifications
Release notes
The Trados GroupShare release notes describe new features, changed features, fixed issues and remaining known issues.
The release notes are also available in PDF format. Access Trados GroupShare Release Notes to download the PDF.
What's new in Trados GroupShare
This section provides an overview of features and functionality introduced or changed in Trados GroupShare over time.
Enabling acronyms and URLs
You can configure Trados GroupShare to recognize acronyms and URLs for each translation memory (TM).

Procedure
1. Go to the Resources view.
2. In the Translation Memories tab, select the checkbox corresponding to the TM where you want to enable the recognition.
3. Select Edit.
4. In the [translation memory name] dialog, select Advanced Settings.
5. Under Recognize, select the checkboxes corresponding to the tokens you want to enable.
6. Select Finish.

What to do next
When you enable recognition, the TM does not automatically scan its TUs, so it does not automatically recognize the tokens in existing TUs. To
force the TM to re-scan its TUs, re-index the TM by tuning its performance.
Parent topic: Acronyms and URLs
Organizations and libraries compared
Organizations are needed for permissions and users. Libraries are a restricted form of organizations that power users might find useful.

Organizations Libraries
Store users YES NO
Store resources YES YES
Store libraries YES YES
Store organizations YES NO
Parent topic: Organizations and their components
Deactivating your product online for a single-user license
Deactivating your product returns the license to the Activation Server.

Before you begin


To deactivate your product online, you need Internet access. If for some reason it cannot access the Activation Server, it will prompt you to
perform an offline deactivation.

About this task


Deactivation is recommended if you plan to:
Move your license to another computer.
Reformat your computer and then install the Trados GroupShare on the same machine again.

Procedure
1. Go to Start > GroupShare [year] > GroupShare [year] Product Activation to displat the Product Activation dialog.
2. Select Deactivate.
3. A prompt is displayed asking if you want to deactivate your product. Select Yes.
A message is displayed indicating that the deactivation was successful. The license has now been returned and can be activated again with a
different installation of the software.
Parent topic: Activating single-user licenses online (activation code)
Working with Online Editor
Online Editor is an online tool that you can use to translate and review files online. Online Editor is a scalable, cost-effective component that
combines the core capabilities of a modern desktop translation tool with a friendly interface designed to boost productivity and to ensure a positive
user experience.
Online Editor editions
Online Editor is available in two editions, Basic and Advanced, which can be used concurrently starting from Trados GroupShare 2020
CU2. The previous product version, Trados GroupShare 2020 CU1, offered Online Editor, as either Basic or Advanced. Find out the
differences.
Opening files in Online Editor
Use the Online Editor to open files that you want to translate or review online. You can only open one file at a time. You can open files from
the Trados GroupShare interface or from the file-name link in the email notification you receive upon file assignment.
Checking in files in Online Editor
Once you finish translating or reviewing the assigned file online, you must check in your changes to save them. Online Editor allows several
users to work on the same file, at the same time.
Downloading files in Online Editor
Once your work on the assigned files is finished, you can download the file in its native format directly from Online Editor.
Shortcuts in Online Editor
Shortcuts are a simple and efficient alternative to working with the mouse. As project deadlines near, you might want to use them to save
time.
Navigating the Online Editor user interface
The Online Editor user interface consists of multiple elements designed to help you focus on your work and make each interaction
meaningful.
Translating content
You can translate content in Online Editor using the translation resources (TMs, terminology, MT) originating in the application Online Editor
integrates with.
Verifying translated content
You can verify translations in Online Editor to check for errors and inconsistencies. Verification checks the target segment against the source
segment and reports if there are missing tags or inconsistent QA (Quality Assessment) items.
Reviewing translated content
You can review translations in Online Editor by managing comments, tracking changes, and using other advanced options.
Filtering segments
Filtering segments is particularly useful, for example, in making sure that there are no untranslated segments left in a file.
Undoing or redoing actions
You can undo or redo actions to make sure that the asset you submit does not contain any errors.
Performing batch operations on segments
You can perform several batch operations if you select multiple segments.
Finding and replacing text
Search for words, strings, or expressions in source or target segments and replace existing occurrences with up-to-date text.
Timeout interval in Online Editor
Online Editor times out after 30 minutes of inactivity.
Known issues in Online Editor
Consult the list of known issues and limitations.
Restricting the download of project files
Trados GroupShare can restrict the download of project files to some roles only. The Secure Project File Download permission is assigned to the
following roles by default: Administrator, Power User and Project Manager.

Before you begin


You must be assigned a role which has the Secure Project File Download permission to restrict the download of project files by other users. You
can enable the download restriction during project creation.

Procedure
1. Go to the Projects view and select New Project.
2. In the General Settings tab of the New Project window:
a. Provide a name and a description for your project.
b. Select a location in the organization.
c. Select a project template from the list.
d. Browse for or drag and drop translatable files: the *zip archive (containing all the project files) or individual files.
Restriction: You can create projects either by using a *zip archive or by using individual files. You cannot use both methods at the
same time.
e. Optionally, set a due date and time for your project.
f. If you select the Restrict file downloads for this project checkbox, only the roles which have the Secure Project File Download
permission will be able to download the source files and the translated files. By default, the Secure Project File Download permission
is available for the following roles: Administrator, Power User, Project Manager.
3. In the New Project window, select the Reference Projects tab and configure it. This is a non-standard feature which you can purchase
based on a contractual agreement.
4. Select Finish.
The new project is added to the Projects list and instantly visible to all the users with access to the project. Trados GroupShare also shows
these users an on-screen notification about the new project.

Results
Only the roles which have the Secure Project File Download permission, will be able to download the source files and the translated files.
Parent topic: Project management
Standard roles and permissions
A role is a collection of permissions. Trados GroupShare has seven standard roles, while Trados GroupShare Cloud has six standard roles, which
correspond to the most common jobs that users do. The permissions associated to roles can be changed in Trados GroupShare, but they cannot
be changed in Trados GroupShare Cloud.
As administrator, you give roles to users so that they can carry out job functions in Trados GroupShare, Trados Studio and MultiTerm Server.

Standard roles in Trados GroupShare


Role Description
Administrator The administrator of a Trados GroupShare organization or resource library:
Has all available Trados GroupShare permissions.
Gives default access to the Licensing and Infrastructure views.
By default, the administrator role:
Is a standard, built-in role assigned to the built-in System Administrator account.
Can be added to any other user who should have unrestricted rights in Trados GroupShare and in
MultiTerm Server.
Can customize password complexity rules for the user accounts on the Trados GroupShare server.
Cannot be deleted.
Gives Update Project Files permission.

Power User
The power user role is typically filled by the application expert or the local administrator.

Translator The translator role:


Can update TMs, but cannot create or change their structure.
Cannot create TMs or change their structure.
Change organization or user details.

External Translator The external translator role is filled by people from outside the translation company and they:
Can perform the same jobs as in-house translators can.
Have the same permissions as in-house translators.

Guest
The guest role allows its users to have Read access to some details.

Project Manager The project manager role is filled by users who:


Manage translation resources.
Manage projects.
Manage users.

MultiTerm Guest The MultiTerm guest role:


Is a standard, built-in role.
Cannot be deleted.
Gives public access to MultiTerm termbases, but does not grant any rights in Trados GroupShare.

Standard roles in Trados GroupShare Cloud


The standard roles in Trados GroupShare Cloud are:
Administrator
Project Manager
Translator
External Translator
Reviewer
External Reviewer
These roles and their permissions cannot be changed. Also, in Trados GroupShare Cloud, there is no possibility to add new roles.

Standard permissions by role Trados GroupShare


The following table shows the default permissions associated to the default roles in Trados GroupShare.

Resource type Permission Administrator Power user Project Translator External Guest MultiTerm
manager Translator Guest
Library View Library
Add Library
Edit Library
Delete Library
Link To
Library

Organizations View
Organization
Add
Organization
Edit
Organization
Delete
Organization
Link To
Organization

Users View User


Add User
Edit User
Delete User

Application wide Background


Task
Administrator
View
Background
Tasks
Manage Roles
View License
Info
View
Dashboard
View
Infrastructure
Create
Termbase

TM database View DB
server Server
Resource type Permission Administrator Power user Project Translator External Guest MultiTerm
manager Translator Guest
Add DB
Server
Edit DB
Server
Delete DB
Server

TM container View
Container
Add Container
Edit Container
Delete
Container
Language View
resource Language
Resource
Add Language
Resource
Edit Language
Resource
Delete
Language
Resource

Fields View Fields


Add Fields
Edit Fields
Delete Fields

Translation View TM
memory
Add TM
Edit TM
Delete TM
Write TU
Read TU
Delete TU
Batch Edit TU
Batch Delete
TU
Import TU
Export TU
Re-index TU

Project View Project


Add Project
Edit Project
Delete Project
Resource type Permission Administrator Power user Project Translator External Guest MultiTerm
manager Translator Guest
Check Out My
Project Files
Check Out
Any Project
Files
Cancel Check
Out of Other
Users Project
Files
Add new
Source Files to
a Project
Add new
Source Files to
a Project
Assign Files
View Other
Users
Change
Current Phase
Change Any
Phase
Generate
AuditTrail
report
Download
AuditTrail
report
Secure Project
File Download

Project Add Project


Templates Template
View Project
Template
Delete Project
Template
Edit Project
Template

Termbases View
Termbase
Add Termbase
Edit Termbase
Delete
Termbase
Concept Level
Read
Concept Level
Write
Copy Entry
Merge Entry
Resource type Permission Administrator Power user Project Translator External Guest MultiTerm
manager Translator Guest
Delete Entry
Import Entries
Export Entries
Edit Without
Input Model
Change Entry
Class
Batch
Operations
Reports View Report
Add Report
Edit Report
Delete Report

Standard permissions by role Trados GroupShare Cloud


The following table shows the default permissions associated to the default roles in Trados GroupShare Cloud. These roles and their permissions
cannot be changed. Also, in Trados GroupShare Cloud, there is no possibility to add new roles.

Resource type Permission Administrator Project Translator/Reviewer External GS Read Only


manager Translator/Reviewer
Library View Library
Add Library
Edit Library
Delete Library
Link To Library
Organization View
Organization
Add Organization
Edit Organization
Delete
Organization
Link To
Organization

User View User


Add User
Edit User
Delete User

Application wide Background


Task
Administrator
View
Background
Tasks
Manage Roles
View License
Info
Resource type Permission Administrator Project Translator/Reviewer External GS Read Only
manager Translator/Reviewer
View
Infrastructure

TM database View DB Server


server
Add DB Server
Edit DB Server
Delete DB
Server

TM container View Container


Add Container
Edit Container
Delete Container

Language View Language


resource Resource
Add Language
Resource
Edit Language
Resource
Delete Language
Resource

Field View Fields


Add Fields
Edit Fields
Delete Fields

Translation View TM
memory
Add TM
Edit TM
Delete TM

Translation unit Write TU


Read TU
Delete TU
Batch Edit TU
Batch Delete TU

Import TU
Export TU
Re-index TU

Project View Project


Add Project
Edit Project
Delete Project
Check Out My
Project Files
Resource type Permission Administrator Project Translator/Reviewer External GS Read Only
manager Translator/Reviewer
Check Out Any
Project Files
Add new Source
Files to a Project
Assign Files
View Other
Users
View All Files
Change Current
Phase
Change Any
Phase

Termbase Add Termbase


Parent topic: Working with users, roles and permissions
Related tasks
Step 2: Assigning files to users
Step 3: Updating file phase
Step 4: Completing assignments
Step 5: Advancing assignments to the next phase
Step 6: Completing projects
Step 2: Planning work on assignments
Step 3a: Completing assignments in Trados Studio
Step 3b: Completing assignments in the Online Editor
Step 4: Completing projects
Adding permissions to user roles
Step 1a: Creating projects from scratch
When you create projects from the Trados GroupShare web interface, you create a storage for all the files that need to be translated. At this stage,
you also decide which organization is in charge of your project. You can either create projects from scratch or starting off from previous projects.

Before you begin


Make sure you:
Create a project template. You will need it during the project creation wizard.
If you want to upload a group of translatable files in one shot, you need to create a *zip archive that contains the files for translation.
Starting with SDL Trados Studio 2017 SR1, the project template, which you create in Trados Studio, can include file assignments. This means that
you can decide which users work on your files, for each file phase, when you actually create the template.

Procedure
1. Go to the Projects view and select New Project.
2. In the General Settings tab of the New Project window:
a. Provide a name and a description for your project.
b. Select a location in the organization.
c. Select a project template from the list.
d. Browse for or drag and drop translatable files: the *zip archive (containing all the project files) or individual files.
Restriction: You can create projects either by using a *zip archive or by using individual files. You cannot use both methods at the
same time.
e. Optionally, set a due date and time for your project.
f. If you select the Restrict file downloads for this project checkbox, only the roles which have the Secure Project File Download
permission will be able to download the source files and the translated files. By default, the Secure Project File Download permission
is available for the following roles: Administrator, Power User, Project Manager.
3. Select Finish.
The new project is added to the Projects list and instantly visible to all the users with access to the project. Trados GroupShare also shows
these users an on-screen notification about the new project.

Required folder hierarchy and naming for .ZIP archives


When you create a project from a .ZIP file that contains multiple files, Trados GroupShare automatically identifies all the translatable files from the
root folder and from any subfolders available in the archive.
If your .ZIP archive also contains reference files or PerfectMatch files, make sure to use the structure and file naming described below. This
hierarchy enables Trados GroupShare to map your source files to the corresponding PerfectMatch files:
\SourceFiles - Optional folder containing the individual files or subfolders of files for translation. If you do not want to group all source files into
a single folder, you can also add the source files directly under the root archive folder. If you do add the source files as a single folder, we
recommended naming this folder "SourceFiles" to enable Trados GroupShare to map any corresponding PerfectMatch files easier.
If you name the SourceFiles folder differently, the structure of the PerfectMatch folder must also include your custom-name folder for every
language code subfolder in your PerfectMatch folder. See image 2b: ZIP structure when using a custom name for the Source Files folder.
...\1st Set Of Source Files
...\...\...\First File.docx

...\...\...\Second File.doc
...\2nd Set of Source Files
...\...\Third File.txt
...\...\Fourth File.doc

\PerfectMatchFiles - Optional folder containing already translated files in .SDLXLIFF format. The name of the folder must be
"PerfectMatchFiles". The PerfectMatch structure should match the folder and file name of the corresponding the source folder and source file.
...\de-de
...\...\1st Set Of Source Files
...\...\...\First File.docx.sdlxliff
...\...\...\Second File.doc.sdlxliff
...\...\2nd Set of Source Files
...\...\...\Third File.txt.sdlxliff

...\...\...\Fourth File.doc.sdlxliff
...\fr-fr
...\...\1st Set Of Source Files
...\...\...\First File.docx.sdlxliff

...\...\...\Second File.doc.sdlxliff
...\...\2nd Set of Source Files
...\...\...\Third File.txt.sdlxliff
...\...\...\Fourth File.doc.sdlxliff

\PerfectMatchFiles_1 - If you have more than one version of a PerfectMatch file that you want to apply to a source file, or if you want to add
more than one .SDLXLIFF file with the same name, create additional "PerfectMatchFiles" folders using the following format:
\PerfectMatchFiles_1, \PerfectMatchFiles_2, \PerfectMatchFiles_3,...
...\de-de
...\...\1st Set Of Source Files
...\...\...\First File.docx.sdlxliff
...\...\2nd Set of Source Files
...\...\...\Fourth File.doc.sdlxliff

\ReferenceFiles - Optional folder containing project files that should be used as a reference when translating or reviewing the source files. The
name of the folder must be "ReferenceFiles".
...\Diagram.vdsx
...\Image.png

Image 1: Required .ZIP structure when using the recommended name for the Source Files folder

Image 2: Required .ZIP structure when using a custom name for the Source Files folder
Parent topic: Workflow for shared projects started in Trados GroupShare
Related concepts
File assignment security
File assignment notifications
Changes introduced in Trados Groupshare 2020 SR1 CU8
This page contains an overview of the new features and fixed brought by Cumulative Update 8 for our latest major release, Trados GroupShare
2020 SR1.
We are constantly reviewing and improving our products. We release enhancements and fixes to resolve customer issues as and when required.
All changes and fixes are bundled into the cumulative update which you can install from RWS Account > Downloads.
Changes introduced in Trados GroupShare SR1 CU8.1
This page contains an overview of the changes brought by our latest Cumulative Update for Trados GroupShare 2020 SR1.
New project settings XML REST API endpoint
API changes for third-party developers
Updated MultiTerm Online classic layouts
Fixed issues
Other changes
Known issues
Parent topic: What's new in Trados GroupShare
Trados GroupShare Console settings
The SDL Trados GroupShare branch of the navigation tree gives you access to the GroupShare settings, databases and services.

Navigation tree branch Associated settings


Settings Use the Settings branch:
Specify the language to be used in messages returned by MultiTerm Server
Specify execution server settings:
The number of concurrent tasks that can be performed on the execution server
The correct credentials to access the Trados GroupShare TM, for TM management tasks
View and edit the folder location used by MultiTerm Online when importing and exporting termbase data.
Users require Windows access rights for this folder. The user can be one of these three types and requires
both Read and Write permissions to be able to successfully import and export from the specified path:
Running Tomcat
Running the MTJobs service
Running the Application service
View and edit settings for project archiving
View and edit Project Server file storage location
View and edit Project Server notification settings
Launch product activation

Databases Use the Databases branch to:


Select the SQL server
View or update database configuration settings for the GroupShare System Database and MultiTerm Master
Database
Edit the user account details used to log in to the database

Services Use the Services branch to:


See which services are installed and whether they are running. This shows the Application service and the
Execution service as well as the current MT services.
Restart services
Stop services

Revert to last saved settings option


The Revert to last saved settings option is in the Actions pane. If you have made any changes to the settings on that page and have not yet clicked
Apply, you can click the Revert to last saved settings option and it will return to the settings you had before you made changes.
Warning: Once you click Apply, you cannot revert to previous settings.

After editing GroupShare settings


After editing GroupShare settings, restart the GroupShare Database services. To do this, click Services in the navigation tree in the GroupShare
Console and then click Restart Services in the Actions pane.
Specifying the MultiTerm server message language
You can specify the MultiTerm server message language for more accessibility.
Setting up execution server threads
You can specify the maximum number of execution threads permitted on the server to control resource usage.
Set up translation providers from the Console
Enable server-based translation memories, SDL ETS Translation or Language Weaver from the Trados GroupShare Console to pre-
translate project files using these providers.
Granting permissions automatically
When a file is assigned to a user, you can choose what role that user will have in the project where the file is located.
Changing file storage location
By default, files are saved in %ProgramData%\SDL\SDLServer1\FileStore, on the computer where Trados GroupShare is installed, but this
location can be changed if necessary.
Changing settings for project archiving
When the list of Trados GroupShare projects contains too many Completed projects, the overall performance can be affected and project
management is hindered. That is why it is useful to archive completed projects and reduce the visible list of Trados GroupShare projects.
Setting up project detaching
The detachment process physically removes Completed or Archived projects from the Trados GroupShare database. Trados GroupShare
makes a package of the detached project and stores it in a set location.
Changing the external server address
When users create and edit file assignments in SDL Trados Studio 2015 and later, SDL GroupShare 2015 and later sends out email
notifications to the users assigned to work on the project files. These notifications emails include the project server hyperlink address that
enables users to access the Online Editor and open assignment files directly from the notification email.
Renaming default phases
Change the names of the default phases used by your Trados GroupShare server. The custom phases that you set up for your Trados
GroupShare server will be available in Trados Studio when opening and working with a project based on that Trados GroupShare server.
Specifying project server notification settings
The project server notification settings are used to send email notifications to Trados GroupShare users.
Specifying or updating the database login details
MultiTerm Server stores terms in a Microsoft SQL Server database. MultiTerm Server uses the account information to access the database
when working with terms in a termbase (TB).
Checking service status
You can check service status at any time to manage service operations according to your needs.
Customize password complexity rules
As an Trados GroupShare administrator, you can enforce password requirements for the user accounts on your server. This enables you to
better protect your users' accounts and meet your organization's compliance needs. Password requirements are enforced the next time that
your existing users change their passwords or when new accounts are created.
Parent topic: Trados GroupShare Console
TM performance tuning
You can tune the performance of a translation memory (TM) in terms of: performance, fuzzy index and statistics.
Trados GroupShare performs the re-indexing and recomputation tasks in the background, leaving you free to do other actions. Monitor their
progress in the System Configuration view by going to the Background Tasks tab.

Performance
Trade off speed versus accuracy by changing the minimum match score.
When the match score decreases, the fuzzy search optimizer narrows its search.
When the match score increases, the fuzzy match search is broadened.

Fuzzy index statistics


Words that occur very frequently in translation units (TUs) are not useful for fuzzy indexes. Typically, these are words like a, the, to. Recompute
fuzzy index statistics removes the 1000 most frequent words from the fuzzy indexes.
This can make a difference in performance for large TMs. If the TM has less than 50,000 TUs, it will not make a noticeable difference.

Re-index TM
TM are re-indexed from scratch. The re-indexing process goes through each TU, finds the tokens (words), and then computes the fuzzy indexes.
Do this, for example, if you enable recognition of dates or variables after you change token recognition.
This option includes the previous option (Recompute fuzzy index statistics).
On large TMs, re-indexing can take a long time.

upLIFT alignment status


upLIFT alignment is the fragment alignment (also known as FGA) that automatically occurs for TMs which have 5,000 TUs or more. The
automatic alignment happens between 00:00 AM and 06:00 AM. You can check whether the TUs are aligned or not on the Performance Tuning
page of server-based TM s which meet the minimum 5,000 TU requirement.
Parent topic: Tuning server-based TM performance
You cannot add database server (authentication issues)
Symptom
You try to add a database server specifying Windows authentication, but you get an error. You can add the database server using database
authentication.
Probable causes
The Trados GroupShare database server does not accept the Windows authentication of the Trados GroupShare application server.
Possible reasons are:
The database server is not in the same Windows domain as the application server.
The Trados GroupShare application server is installed to run under a local user account rather than a Windows domain account.
Solution
Ask the system administrator to:
Check that the database server is running in the same Windows domain as the Trados GroupShare application server.
Ensure that the Trados GroupShare application server runs under a domain user account.
For more information, see the .
Workaround
Use database authentication.
If you know details of a suitable user on the database server, use that. Give the user name in the form:
databaseServerComputername \ username
Parent topic: Problems and solutions
Moving single-user license to another computer
To use your license on another computer, which has Trados GroupShare, you must first deactivate the license on the first computer. Then, you can
activate it on the new computer.
Moving single-user license to another computer via Internet
To deactivate Trados GroupShare online, you must be connected to the Internet.
Moving single-user license to another computer without Internet
If you cannot access the Internet from the computer on which the currently activated (licensed) version of Trados GroupShare is installed or
if your firewall prevents you from performing online deactivation, you can either modify your proxy settings or use offline deactivation.
Parent topic: Activating single-user licenses online (activation code)
Saving project level reports
You can save the reports irrespective of the project's file phase. Several formats are available.

About this task


Reports are available only for projects created in Trados GroupShare.

Procedure
1. Go to the Projects view and select a project to open it.
2. In the [project name] tab, select .
3. Consult the report details.
4. Optionally, go to the table columns and:
Sort the data in ascending or descending order.
Customize the columns that are displayed.
Tip: The filters you apply at column level are kept when printing the report.
5. Select Save As and choose an export file format.
6. Save the file locally.
Parent topic: Project-level reports and background tasks
Granting permissions automatically
When a file is assigned to a user, you can choose what role that user will have in the project where the file is located.

Procedure
1. In the Trados GroupShare Console navigation tree, select SDL Trados GroupShare > Settings.
2. In the Settings pane, under Automatic Role Assignment, enable automatic permission assignment.
3. Choose what project role should be assigned to the user that works on a project file. The External Translator role is the default value. You
could create your own role for this use case.
4. In the Actions pane, select Apply Changes to save the change.
Parent topic: Trados GroupShare Console settings
Project management
The Trados GroupShare interface enables you to manage both new and completed projects.
Viewing projects
You can consult the list of available projects at any time. The project list provides information about the project: name, publication date,
delivery date, client, status, language pairs and location within the Trados GroupShare organization hierarchy.
Creating projects
When you create projects from the Trados GroupShare web interface, you create a storage for all the files that need to be translated. At this
stage, you also decide which organization is in charge of your project.
Set up translation providers
During project creation, Trados GroupShare can pre-translate project files using the MT providers that you set up in the Trados
GroupShare webUI or in the Trados GroupShare Console
Step 1c: Updating an existing project
Upload new translatable and reference files to existing projects. This is useful for situations when you receive updated project files from your
customer, or additional files that were missed from the initial drop.
Restricting the download of project files
Trados GroupShare can restrict the download of project files to some roles only. The Secure Project File Download permission is assigned
to the following roles by default: Administrator, Power User and Project Manager.
Downloading project files in .sdlxliff format
You can download the project files in .sdlxliff format to store or consult them irrespective of the project phase they are in, if you are not
restricted in this regard by a user who has the Secure Project File Download permission.
Working with project packages
As a project manager, you can hand off work to team members who do not have access to Trados GroupShare by exporting project files
as .SDLPPX packages.
Downloading translated project files
You can download the translated project files in their native format, during any project phase, if you are not restricted in this regard by a
user who has the Secure Project File Download permission.
Updating TMs after project file download
You can download the translated project files in their native format and update the TMs (translation memories), during any project phase, if
you are not restricted in this regard by a user who has the Secure Project File Download permission.
Editing projects
You can change the planning details of your projects when no longer up-to-date.
Completing projects
When users complete all the assignments, you can mark the projects as Complete. At this stage, all the project files are usually in the
Finalisation phase.
Restoring completed projects
You can restore projects from a Completed status to an In progress status if there is still some work left to do.
Deleting projects
You can delete your projects irrespective of their status, when no longer necessary.
Project settings
Project settings refer to the elements which control a project's behaviour. You can access and manage the project settings if you are
assigned the Edit Project permission.
Project details progress bar
You can consult the progress bar on the Project Details pane of each project.
Parent topic: Working with projects
API changes for third-party developers
With this release, we're introducing API documentation based on OpenAPI. This is available in machine-readable OpenAPI json format, and can be used for automated endpoint
discovery.
You can find documents available for the entire RestAPI at: http(s)://<gserver>/docs/<section>, where <gsserver> is the host server and <section> can be:
supported - contains all supported endpoints. This is the recommended document for regular use.
all - contains all endpoints, including deprecated.
V4 - contains only endpoints belonging to version 4.
V3 - contains only endpoints belonging to version 3.
V2 - contains only endpoints belonging to version 2.
V1 - contains only endpoints belonging to version 1. These endpoints are deprecated for project server and management.
You can find specific APIs at the following links:
http(s)://<gserver>/docs/projectserver/<section>
http(s)://<gserver>/docs/management/<section>
http(s)://<gserver>/docs/multiterm/<section>
http(s)://<gserver>/docs/authentication/<section>
In the links above:
<gserver> is the host server
<section> can be all (contains all available endpoints), or supported (contains only non-deprecated endpoints).

Deprecated endpoints
We have marked the following REST API endpoints as deprecated and we plan to remove them in future releases:

HttpMethod Obsolete routes Alternative Reason


GET /api/management/v2/backgroundtasks/{id} /api/management/v2/backgroundtasks -
POST /api/management/v2/organizationcals/{organizationid} /api/management/v2/organizationcals -
PUT /api/management/v2/organizationresources/{id} /api/management/v2/organizationresources -
DELETE /api/management/v2/organizations /api/management/v2/organizations/{id} -
POST /api/management/v2/organizations/{id} /api/management/v2/organizations -
PUT /api/management/v2/organizations/{id} /api/management/v2/organizations -
DELETE /api/management/v2/organizations/{organizationId}/membership /api/management/v2/organizations/{id} -
POST /api/management/v2/organizations/{organizationId}/membership /api/management/v2/organizations -
PUT /api/management/v2/organizations/{organizationId}/membership /api/management/v2/organizations -
POST /api/management/v2/roles/{id} /api/management/v2/roles -
PUT /api/management/v2/roles/{id} /api/management/v2/roles -
DELETE /api/management/v2/roles/{roleId}/membership /api/management/v2/roles/membership -
GET /api/management/v2/roles/{roleId}/membership /api/management/v2/roles/{roleId}/users -
PUT /api/management/v2/roles/{roleId}/membership /api/management/v2/roles/membership -
PUT /api/management/v2/roles/{roleId}/users /api/management/v2/roles/membership -
DELETE /api/management/v2/roles/membership/{id} /api/management/v2/roles/membership -
GET /api/management/v2/roles/membership/{id} /api/management/v2/roles/{roleId}/users -
PUT /api/management/v2/roles/membership/{id} /api/management/v2/roles/membership -
POST /api/management/v2/users/{id} /api/management/v2/users -
PUT /api/management/v2/users/{id} /api/management/v2/users -
DELETE /api/management/v2/users/{name} /api/management/v2/users/{id} -
POST /api/management/v2/users/{name} /api/management/v2/users -
PUT /api/management/v2/users/{name} /api/management/v2/users -
POST /api/management/v3/organizations/{id} /api/management/v3/organizations -
PUT /api/management/v3/organizations/{id} /api/management/v3/organizations -
GET /api/projectserver/v2/dashboard - -
GET /api/projectserver/v2/dashboard/projectsPerMonth Reporting Service /api/reports/Dashboard/ProjectsPerMonth -
GET /api/projectserver/v2/dashboard/topLanguagePairs Reporting Service /api/reports/Dashboard/TopLanguagePairs -
GET /api/projectserver/v2/dashboard/topLanguagePairs/{noOfTopLanguagePairs} Reporting Service /api/reports/Dashboard/TopLanguagePairs -
GET /api/projectserver/v2/dashboard/wordsPerMonth Reporting Service /api/reports/Dashboard/WordsPerMonth -
GET /api/projectserver/v2/dashboard/wordsPerOrganization Reporting Service /api/reports/Dashboard/WordsPerOrganization -
GET /api/projectserver/v2/projectPredefinedReports Reporting Service /api/reports/Predefined/Projects -
POST /api/projectserver/v2/projects/{id} /api/projectserver/v2/projects -
DELETE /api/projectserver/v2/projects/{projectId}/changestatus/{status} /api/projectserver/v2/projects/{projectId}/detach[/{deleteProjectTMs}] -
PUT /api/projectserver/v2/projects/{projectId}/detach /api/projectserver/v2/projects/{projectId}/changestatus/{status} -
GET /api/projectserver/v2/tasksReport Reporting Service /api/reports/Predefined/Tasks -
GET /api/projectserver/v2/tmLeverageReport Reporting Service /api/reports/Predefined/TMLeverage -
DELETE /management/api/1.0/Membership /api/management/v2/roles/membership -
PUT /management/api/1.0/Membership /api/management/v2/roles/membership -
DELETE /management/api/1.0/Membership/{id} - Accidental
route
PUT /management/api/1.0/Membership/{id} - Accidental
route
DELETE /management/api/1.0/Membership/{name} - Accidental
route
PUT /management/api/1.0/Membership/{name} - Accidental
route
DELETE /management/api/1.0/Organizations /api/management/v2/organizations/{id} -
POST /management/api/1.0/Organizations /api/management/v2/organizations -
GET /management/api/1.0/Organizations /api/management/v2/organizations -
PUT /management/api/1.0/Organizations /api/management/v2/organizations -
DELETE /management/api/1.0/Organizations/{id} /api/management/v2/organizations/{id} -
GET /management/api/1.0/Organizations/{id} /api/management/v2/organizations/{id} -
POST /management/api/1.0/Organizations/{id} - Accidental
route
PUT /management/api/1.0/Organizations/{id} - Accidental
route
DELETE /management/api/1.0/Organizations/{name} - Accidental
route
PUT /management/api/1.0/Organizations/{name} - Accidental
route
GET /management/api/1.0/Organizations/{name} - Accidental
route
POST /management/api/1.0/Organizations/{name} - Accidental
route
GET /management/api/1.0/Permissions /api/management/v2/permissions -
GET /management/api/1.0/Permissions/{id} /api/management/v2/permissions -
GET /management/api/1.0/Permissions/{name} /api/management/v2/permissions -
DELETE /management/api/1.0/Roles /api/management/v2/roles/{id} -
GET /management/api/1.0/Roles /api/management/v2/roles -
POST /management/api/1.0/Roles /api/management/v2/roles -
PUT /management/api/1.0/Roles /api/management/v2/roles -
DELETE /management/api/1.0/Roles/{id} /api/management/v2/roles/{id} -
POST /management/api/1.0/Roles/{id} /api/management/v2/roles -
PUT /management/api/1.0/Roles/{id} /api/management/v2/roles -
GET /management/api/1.0/Roles/{id} /api/management/v2/roles/{id} -
DELETE /management/api/1.0/Roles/{name} /api/management/v2/roles/{id} -
GET /management/api/1.0/Roles/{name} /api/management/v2/roles -
POST /management/api/1.0/Roles/{name} /api/management/v2/roles -
PUT /management/api/1.0/Roles/{name} /api/management/v2/roles -
DELETE /management/api/1.0/roles/{roleId}/membership /api/management/v2/roles/membership -
PUT /management/api/1.0/roles/{roleId}/membership - Accidental
route
DELETE /management/api/1.0/roles/membership /api/management/v2/roles/membership -
PUT /management/api/1.0/roles/membership /api/management/v2/roles/membership -
DELETE /management/api/1.0/Users /api/management/v2/users/{id} -
GET /management/api/1.0/Users /api/management/v2/users -
POST /management/api/1.0/Users /api/management/v2/users -
PUT /management/api/1.0/Users /api/management/v2/users -
DELETE /management/api/1.0/Users/{id} /api/management/v2/users/{id} -
GET /management/api/1.0/Users/{id} /api/management/v2/users/{id} -
POST /management/api/1.0/Users/{id} /api/management/v2/users -
PUT /management/api/1.0/Users/{id} /api/management/v2/users -
DELETE /management/api/1.0/Users/{name} /api/management/v2/users/{id} -
GET /management/api/1.0/Users/{name} /api/management/v2/users/{id} -
POST /management/api/1.0/Users/{name} /api/management/v2/users -
PUT /management/api/1.0/Users/{name} /api/management/v2/users -
DELETE /multiterm/api/1.0/termbases/{termbaseId}/concepts - Accidental
route
GET /multiterm/api/1.0/termbases/{termbaseId}/concepts - Accidental
route
POST /multiterm/api/1.0/termbases/{termbaseId}/concepts/{conceptId} - Accidental
route
PUT /multiterm/api/1.0/termbases/{termbaseId}/concepts/{conceptId} - Accidental
route
GET /multiterm/api/1.0/termbases/{termbaseId}/multimedia - Accidental
route
POST /multiterm/api/1.0/termbases/{termbaseId}/multimedia/{imageId} - Accidental
route
POST /projectserver/api/1.0/CreateProject /api/projectserver/v2/projects/{projectId}/create -
GET /projectserver/api/1.0/FileDownload /api/projectserver/v2/projects/{projectId}/download -
GET /projectserver/api/1.0/FileStatus /api/projectserver/v2/projects/{projectId}/files -
GET /projectserver/api/1.0/phases/{projectId} /api/projectserver/v2/phases/{projectId} -
GET /projectserver/api/1.0/Projects /api/projectserver/v2/projects -
POST /projectserver/api/1.0/Projects /api/projectserver/v2/projects -
DELETE /projectserver/api/1.0/projects/{id} /api/projectserver/v2/projects/{id} -
GET /projectserver/api/1.0/projects/{id} /api/projectserver/v2/projects/{id} -
POST /projectserver/api/1.0/projects/{id} /api/projectserver/v2/projects -
DELETE /projectserver/api/1.0/projects/{id}/Delete /api/projectserver/v2/projects/{id} -
GET /projectserver/api/1.0/projects/{id}/Get /api/projectserver/v2/projects/{id} -
GET /projectserver/api/1.0/projects/{id}/GetByResourceGroupPath /api/projectserver/v2/projects/byresourcegroup -
POST /projectserver/api/1.0/projects/{id}/Post /api/projectserver/v2/projects -
POST /projectserver/api/1.0/projects/{projectId}/changeassignment /api/projectserver/v2/projects/{projectId}/changeassignment -
POST /projectserver/api/1.0/projects/{projectId}/changephase /api/projectserver/v2/projects/{projectId}/changephase -
GET /projectserver/api/1.0/projects/{projectId}/download /api/projectserver/v2/projects/{projectId}/download -
GET /projectserver/api/1.0/projects/{projectId}/download/{type} /api/projectserver/v2/projects/{projectId}/download/{type} -
GET /projectserver/api/1.0/projects/{projectId}/filestatus /api/projectserver/v2/projects/{projectId}/files -
GET /projectserver/api/1.0/projects/{projectId}/filestatus/languagefiles /api/projectserver/v2/projects/{projectId}/files -
GET /projectserver/api/1.0/projects/{projectId}/phaseswithassignees/{phaseId} /api/projectserver/v2/projects/{projectId}/phaseswithassignees/{phaseId} -
GET /projectserver/api/1.0/projects/{projectId}/publishingstatus /api/projectserver/v2/projects/{projectId}/publishingstatus -
POST /projectserver/api/1.0/projects/{projectId}/publishpackage /api/projectserver/v2/projects/{projectId}/publishpackage -
GET /projectserver/api/1.0/PublishingStatus /api/projectserver/v2/projects/{projectId}/publishingstatus -
POST /projectserver/api/1.0/PublishPackage /api/projectserver/v2/projects/{projectId}/publishpackage -
Parent topic: Changes introduced in Trados Groupshare 2020 SR1 CU8
Performing batch operations on segments
You can perform several batch operations if you select multiple segments.

Procedure
1. Open the appropriate file in Online Editor.
2. Select multiple segments by pressing Ctrl+Click (on the segment number) or Shift+Click (on the segment number).
3. Perform one of the allowed batch actions:
No. Operation Enabled / Disabled
1. Clear formatting
2. Change case
3. Copy source to target
4. Clear target segment
5. Lock segment
6. Change segment status
7. Undo / Redo
8. Copy / Paste / Cut
9. Apply formatting
10. Insert symbols and special characters
11. Apply translation
12. Confirm translation (all options)
13. Copy all to target
14. Clear draft segments
15. Segment actions (various)
16. Quality Assessment options
17. Accept revision
18. Reject revision
19. Verify translations

Parent topic: Working with Online Editor


Specifying or updating the database login details
MultiTerm Server stores terms in a Microsoft SQL Server database. MultiTerm Server uses the account information to access the database when
working with terms in a termbase (TB).

Procedure
1. In the Trados GroupShare Console navigation tree, select SDL Trados GroupShare > Databases.
2. In the Databases pane, under Database Type, select the database type (Microsoft SQL Server).
3. Under the GroupShare System Database and MultiTerm Master Database sections decide on an authentication method:
Select Use Windows Authentication, and either use the default database location and name, or update the database location and
name (server name or server IP address).
Select Use Database Authentication, and type the following information: database user and password. If you choose Database
Authentification, make sure that the database user you add is already associated to the specified database.
4. In the Actions pane, select Apply Changes to save the change. Changes are only effective once you restart the services.
Parent topic: Trados GroupShare Console settings
Monitoring clients and license information
As a network-licensing administrator, you can use the SafeNet License Manager (WlmAdmin.exe) to monitor Trados GroupShare licenses and the
clients who are using the license seats.

Procedure
1. Select the license servers you want to monitor:
a. Double-click the Subnet Servers on the left hand-side pane of theWlmAdmin window.
Tip: This displays the hostnames of all the license servers available on the network. If you have an active network license for the
server, WlmAdmin lists all the product features included in your license.
b. Consult the Feature Information section and tab for licensing details, such as:
the number of seats available for the current network license
the number of clients currently using the available license seats
the number of seats currently borrowed by clients who use a license offline
c. To update the license feature status, right-click the feature and select Refresh.
2. Monitor the clients:
a. Select a server and expand a product feature node.
b. Double-click the Clients folder to open it. WlmAdmin shows all the clients that are currently using the license seats for that feature.
c. Select one of the users in the list to open the Client Info tab on the lower side of the WlmAdmin window.
d. The Client Info tab shows information such as:
the time when the client connected to the server
the number of seats that the client is using
the name of the client computer and name of the user
whether the client is a commuter, using a borrowed a license
e. To update the client status, right-click the Clients folder, and select Refresh.
Tip: If you want to contact the users who have checked out license seats from your server, get their user names and the name of their
computers from the Client Info tab. You can use these details to contact them offline
3. Monitor the license information:
a. For details about the network license available for the selected server, expand a product feature and the Licenses folder then select a
license from the list.
b. WlmAdmin displays all the licensing information available for the server in the License Info tab, on the lower side of the right hand-
side panel. Consult the information in the License Info tab:
the start date and the end date of the selected license
the active and inactive licenses for the selected server
the maximum number of concurrent users that can access the network license
c. To update the licensing status, right-click the Licenses folder, and select Refresh.
4. Disconnect users in network. If you are a network administrator and you want to withdraw licenses from specific users, contact them offline
and ask them to disconnect from the server.
Parent topic: Activating the Trados License Manager (administrators)
Update existing projects with PerfectMatch archives
When uploading new files to existing projects, you can now also add .ZIP files that include PerfectMatch folders. Trados GroupShare will
recognize any PerfectMatch files and apply them to the corresponding source files from the .ZIP.
To enable Trados GroupShare to map PerfectMatch files correctly, make sure that your archives use the structure and file naming described in the
Required folder hierarchy and naming for .Zip archives topic.

PerfectMatch for existing project files


PerfectMatch is applicable only for the files added via Update Project. The functionality doesn't apply to the source files that were already added
to the project, even if there are files in the .ZIP that would correspond.
Parent topic: Changes introduced in Trados Groupshare 2020 SR1 CU9
Variables for SDL Trados GroupShare
This Library Topic lists variables related to the SDL Trados GroupShare product.
The following variables are for anyone in SDLDOC to reuse:

Variable name Description ph Element


PRODUCTFULLNAME The full name of your product, Trados GroupShare
including the vendor name, but
without any version
PRODUCTFULLNAMEANDCURRENTVERSION The full name of your product, Trados GroupShare 2020
including the vendor name and
current version
PRODUCTFULLNAMEANDCURRENTPATCHVERSION The full name of your product, Trados GroupShare 2020 SR1
including the vendor name and
current version patch release
PRODUCTSHORTNAME The short name of your product, Trados GroupShare
without the vendor name or
version
PRODUCTFULLNAMEASUICONTROL The full name of your product in a SDL Trados GroupShare
uicontrol element
PRODUCTSHORTNAMEANDCURRENTVERSION The short name of your product, Trados GroupShare 2020
without the vendor name, but
including the current version
PRODUCTSHORTNAMEANDCURRENTPATCHVERSION The short name of your product, Trados GroupShare 2020 SR1
including the vendor name and
current version patch release

PRODUCTCURRENTVERSION Only the current version number 2020


of the release
PRODUCTCURRENTPATCHVERSION Only the current patch version SR1
number of the release
DOCURLCURRENTVERSION A redirect URL to the docs of Trados GroupShare Help
this product release
PRODUCTOLDESTUPGRADEFULLNAMEANDVERSION The full name of the oldest SDL Studio GroupShare 2019, 2017 or
version of the product from which 2015
a direct upgrade is possible.
PRODUCTUPGRADELISTFULLNAMEANDVERSION A list of full names of versions SDL Studio GroupShare 2019, 2017 or
from which a direct upgrade is 2015
possible.
VENDORNAME The name of the vendor of the RWS
product, always RWS
RWSACCOUNT RWS Account My Account
STUDIO Full name of Trados Studio Trados Studio
product
STUDIOSHORTNAME Short name of Trados Studio Trados Studio
product
APPSTORENAME Name of the AppStore RWS AppStore
MULTITERM MultiTerm MultiTerm
LANGUAGECLOUDCUSTOMERPORTAL Language Cloud Customer Portal Language Cloud Customer Portal
PROJECTSERVER Project Server Project Server
MTPROVIDER SDL Machine Translation Cloud Language Weaver

The following variables are specific to SDL Trados GroupShare.


Variable name Description ph Element

PRODUCTFULLNAMESR1 The full name of the SR1 release Trados GroupShare 2020 SR1
PRODUCTFULLNAMECU1 The full name of the CU1 release SDL Trados GroupShare 2019 CU1
PRODUCTFULLNAMEANDPREVIOUSVERSION The full name of your product, SDL Studio GroupShare 2017, 2015
including the vendor name and and 2014
previous version
PRODUCTFULLNAMEANDPREVIOUSPATCHVERSION The full name of your product, SDL Studio GroupShare 2017 and
including the vendor name and 2015
previous version latest patch
PRODUCTFULLNAME2019 The full name of the 2019 release SDL Studio GroupShare 2019
PRODUCTFULLNAME2017 The full name of the 2017 release SDL Trados GroupShare 2017
PRODUCTFULLNAME2015 The full name of the 2015 release SDL Studio GroupShare 2015
PRODUCTFULLNAME2014 The full name of the 2014 release SDL Studio GroupShare 2014
PRODUCTSHORTNAME2017 The short name of the 2017 release Trados GroupShare 2017
PRODUCTSHORTNAME2015 The short name of the 2015 release Studio GroupShare 2015
PRODUCTSHORTNAME2014 The short name of the 2014 release Studio GroupShare 2014
CONSOLEFULLPRODUCTNAME The full product name of the console Trados GroupShare Console
component
CONSOLESHORTPRODUCTNAME The short product name of the Trados GroupShare Console
console component
CONSOLEFULLPRODUCTNAMEANDVERSION The full product name of the console Trados GroupShare Console 2020
component and current version SR1
CONSOLESHORTPRODUCTNAMEANDVERSION The short product name of the Trados GroupShare Console 2020
console component and current SR1
version
TMSERVERLATESTVERSION The name and version of latest TM TM Server 2020 SR1
Server
MULTITERMSERVERLATESTVERSION The name and version of latest MT MultiTerm Server 2020 SR1
Server
CUMULATIVEUPDATESLINK The link to current CU updates article Cumulative Updates for Trados
GroupShare 2020

The following variables relate to the Universal Editor.

Variable name Description ph Element


UNIVERSALEDITORNAME The name of the SDL Universal Editor Online Editor
JOBORPROJECT The name of the project project
JOBSORPROJECTS The name of the projects projects
FILEORASSET The name of the file file
FILESORASSETS The name of the files files
ANASSETORAFILE The name of a file a file
Changes introduced in Trados Groupshare 2020 SR1 CU9
This page contains an overview of the new features and fixes brought by Cumulative Update 9 for our latest major release, Trados GroupShare
2020 SR1.
We are constantly reviewing and improving our products. We release enhancements and fixes to resolve customer issues as and when required. All
changes and fixes are bundled into the cumulative update which you can install from RWS Account > Downloads.
New and improved Dashboard and reporting interface
This release features a new Dashboard and Reporting interface, which brings the following improvements:
API changes for third-party developers
Continuing the initiative started in the Trados Groupshare 2020 SR1 CU8 release, we are adding more endpoints for Trados Studio and
third-party integrations.
Share project via direct link
You'll probably notice the new icon next to each project title. This copies the direct project link to your clipboard and takes your
colleagues to the specific project in the Projects view.
Update existing projects with PerfectMatch archives
When uploading new files to existing projects, you can now also add .ZIP files that include PerfectMatch folders. Trados GroupShare will
recognize any PerfectMatch files and apply them to the corresponding source files from the .ZIP.
Changes in the Online Editor
The Online Editor will be receiving an update with this release. Check the release highlights below.
New .NET runtimes
We've made the following .NET runtime changes for this release.
Retiring legacy Language Weaver URLs
Starting with February 23rd, support for our legacy web domains is discontinued:
Other enhancements
This topic encompass a diverse set of features and optimizations that aim to improve efficiency, flexibility, and user experience across
different areas of the GroupShare platform.
Fixed issues
The following list details the issues that were resolved in the Trados GroupShare 2020 SR1 CU9 release.
Known issues
The following list details the limitations associated with Trados GroupShare 2020 SR1 CU9.
Components update
With this release, we have removed the Microsoft Visual C++ 2008, 2010 and 2013 Redistributable components from the list of
GroupShare's dependencies. Here's the updated list:
Parent topic: What's new in Trados GroupShare
Sending a help topic
Copy the last link in a breadcrumb trail to send a help link.

Procedure
1. Select the last link in the breadcrumb trail.
The breadcrumb trail is next to the home icon at the top of the screen, for example RWS Documentation > Welcome to RWS
documentation > Customer support.
2. Right-click the last link and select the relevant copy option:
Chrome: Copy Link Address
Internet Explorer: Copy Shortcut
Firefox: Copy Link Location
Safari: Copy Link
3. Paste the link into your message.
Parent topic: Welcome to the Trados GroupShare 2020 SR1 documentation
Find your project templates easier
The project template list in the Trados GroupShare Web UI is now displayed alphabetically. (CRQ-24625).
Parent topic: Changes introduced in Trados GroupShare 2020 SR1 CU6
Reference library file
Current version: - 2021
Full Name: - RWS Licensing
Full Name and version: - Licensing 2021
License server manager full name: Trados License Manager
License server manager short: Trados License Manager
License server alternative: - Trados Licensing Manager
SafeNet License Manager : SafeNet License Manager
SafeNet License Manager short: SafeNet
(WlmAdmin) component: (WlmAdmin)
Locking Utility (Wechoid) component (Wechoid)
Licensing Server Toolkit Licensing Server Toolkit
Licensing server Trados License Server
GSTrados GroupShare
Studio Trados Studio
PassoloPassolo
Item categories: translatable and other items
You define the item category when you add the item to a project and the category is shown in the project status. The table in this topic lists
available item categories.
Usually a project contains some items that are not for translation. For example, a project might include some graphics files or translation
instructions.

Translatable
The item is for translation.

Localizable
The item is for translation, but not in this application.

Reference
The item is for reference only (for example,
images).

Instruction
The item contains instructions for the translator.

Parent topic: TM language processing rules and recognized tokens


Other enhancements
This topic lists the additional improvements introduced with Trados GroupShare 2020 SR1.

Finalize task disabled outside Finalisation phase


The Finalize files button is now enabled only when all the selected files are in the Finalisation phase. This ensures that occasional project users do
not finalize documents prematurely.

Fallback to Editor CALs for MultiTerm Server


MultiTerm Server can now consume available Editor CALs when no more Viewer CALs are available.

Performance improvements
now updates user rights much faster after you edit roles and permissions.
Added various SQL Server indexes to improve performance when querying users, resources and language directions.
SDLSystem Stored Procedures now execute faster.
Audit trails are now generated in less than a second.
Projects with TM Update are published and downloaded faster.

Security enhancements
Online Editor: Replaced session token with HTTP cookies. This prevents potential attackers from capturing sensitive data.
MultiTerm Online: Fixed vulnerability issue in the Create New Duplicate Filter Definition dialog.
Parent topic: Changes introduced in Trados GroupShare 2020 SR1
Organizations and their components
Organizations are networks of users that share their work and resources.
Organizations consist of:
Users
Roles
Permissions
Projects

Users
Users work or collaborate with other users on the tasks assigned to them. Typical tasks may include: translations, reviews, translation memory
updates and so on.

Roles and permissions


Within the organization they are part of, users fulfill the role assigned to them. Each organization holds a table of users and their roles in that
organization. Roles are groups of permissions allowing users to access resources and work on projects or tasks. Depending on the roles users are
assigned, they may have more or fewer permissions in an organization. Roles and permissions can be created or adjusted depending on your
organization's needs.

Resources
Users have access to the organization's resources depending on the permission associated to their role. Resources include:
Translation memories (TMs)
Termbases
Language resource templates
Field templates
Project templates

Projects
Projects refer to the total sum of documents that need to be translated and reviewed. Projects may also include the resources needed to complete
the work. Once a project is created, the work is divided into one or more tasks, and assigned to users. You can track the project progress on its
Kanban board.

Example: Organizations and their components


This example shows how a hierarchical organization may be structured.

Organizations and users


Every user has a home organization. To view or change a user's details, you need to have the appropriate permissions to the user's home
organization.
Organizations and libraries compared
Organizations are needed for permissions and users. Libraries are a restricted form of organizations that power users might find useful.
Organizations and resources
To ensure work consistency across the organizations and at project level, organizations create or store common resources for their users.
MultiTerm and Trados GroupShare
MultiTerm Server is a repository for MultiTerm objects including termbases and catalog objects.
Creating organizations
Every Trados GroupShare installation sets a unique Root Organization by default. You can add as many organizations to the Root
Organization. Then, you can continue adding as many sub-organizations to these organizations.
Editing organizations
The structure and purpose of organizations may change over the course of time. To keep up with these changes, you can edit the details of
any organization, even those of the Root Organization.
Delete organizations
You can delete any organization or sub-organization that you no longer need. Deleting an organization removes all the resources available
inside the organization: users, translation memories, termbases, sub-organizations and libraries.
Configuring a basic organization
As administrator, you can create a setup for organizations with various complexity degrees. Complex organizations (like the enterprise ones)
have multiple client organizations or sub-organizations. You can replicate the pattern of a basic organization for complex organizations.
Configuring organizations and users for enterprise
GroupShare enables you to set up an appropriate schematic at enterprise level.
Parent topic: Working with users, roles and permissions
Enabling variables
You can configure Trados GroupShare to identify variables in the source text, so that they are found in the target text as such.

Before you begin


Make sure you define the list of recognized variables.

Procedure
1. Go to the Resources view.
2. In the Translation Memories tab, select the checkbox for which you want to enable variables.
3. Select Edit.
4. In the [translation memory name] dialog, select Advanced Settings.
5. Under Recognize, select Variables.
6. Select Finish.

What to do next
When you enable recognition, the TM does not automatically recognize the tokens in existing TUs. To force the TM to re-scan its TUs, re-index
the TM by tuning its performance.
Parent topic: Variables
Services (Local)
Services are all located under the Services (Local) branch.
The Services (Local) page shows the services that are present on the local computer and the status of those services. All GroupShare-related
services start with SDL in the name. You can manage these services from here.
Parent topic: Trados GroupShare Console
GroupShare kit
The kit includes two types of available information: .NET library for Trados GroupShare REST API and TM Search and Terminology Editing
using REST API.
The following information is available:
.NET library for REST API: https://github.com/sdl/groupsharekit.net
TM Search and Terminology Editing using REST API: http://groupsharekitsampleweb.azurewebsites.net/Account/Login?ReturnUrl=%2F
Parent topic: Welcome to the Trados GroupShare 2020 SR1 documentation
Parent topic: Installing Trados GroupShare
Editing organizations
The structure and purpose of organizations may change over the course of time. To keep up with these changes, you can edit the details of any
organization, even those of the Root Organization.

Procedure
1. Go to the Users view.
2. Under Organizations, select the organization whose details you want to edit.
3. Select .
4. In the [organization name] dialog, make the necessary changes.
5. Select Finish.
Parent topic: Organizations and their components
Adding resource links
Resource links allow users from other organizations to access the resource in your organization. The resources you can link to and from include:
translation memories (TMs), servers and containers.

Procedure
1. Go to the Users view and select the Content tab.
2. Select the organization where the resource is located.
3. Select the resource you want to link.
4. Select Link Resource.
5. In the Link Resources dialog, select the location where you want the resource to be linked.
6. Select Finish.
Parent topic: Resource Links
Time and measurement tokens
Dates, times, numbers and measurements are examples of tokens.
You can configure Trados GroupShare to recognize tokens and to localize them automatically.
For example, if the option to recognize Dates is enabled, and the TM is presented with translatable source text, the TM will treat presented text
such as "1 January 1900", as a single token. If Dates is not enabled, "1 January 1900" is treated as three separate words.
Enabling time and measurement tokens
You can configure Trados GroupShare to recognize tokens and to localize them automatically. Tokens include: dates, times, numbers and
measurements.
Parent topic: Recognized Tokens
Modifying source segments
If some of the source segments you are working on contain mistakes, you can modify them and correct the mistakes.

About this task


This feature is available for Online Editor Advanced.
Modify source segments only after you get confirmation from your customer.

Procedure
1. Open the appropriate file in Online Editor.
2. Select the target area of the source segment that you want to modify.
3. On the Home tab, in the Segments group, select Other Actions > Edit Source.
4. Make the necessary changes in the source segment, and then select another target row.

Results
Your changes are saved automatically.
Parent topic: Translating content
Supported operating systems
The Trados GroupShare server modules run on the following platforms:
Windows Server 2019, with IIS 10
Windows Server 2016, with IIS 10
Windows Server 2012 R2, with IIS 8.5
Windows Server 2022 with IIS 10 (compatible with Trados GroupShare 2020 SR1 CU6 and later)
Parent topic: Installing Trados GroupShare
Set up translation providers from the Console
Enable server-based translation memories, SDL ETS Translation or Language Weaver from the Trados GroupShare Console to pre-translate
project files using these providers.

Procedure
1. In the Trados GroupShare Console navigation tree, select SDL Trados GroupShare > Settings.
2. Click Add and select one of the following options:
Server-based Translation Memory Credentials
Language Weaver Credential
SDL ETS Translation
3. Fill in your credentials. You can also edit or delete current credentials for existing connections.
4. In the Actions pane, select Apply changes.
5. In Trados Studio, create a project template that has a server-based TM, Language Weaver or ETS Translation specified as translation
provider.
6. In Trados GroupShare, add the project template as a resource.
7. Create a new project based on the new project template.
8. When the project is ready and available in the projects list, check that the files you added to the project are pre-translated using the
translation provider you set up.

What to do next
To see if an MT provider is used for a certain project, open the project from the projects list and select Project Settings. Go to the Translation
Memories page and see if the MT provider is available in the list.
Parent topic: Set up translation providers
Parent topic: Trados GroupShare Console settings
Applying terminology
You can apply the existing terminology to translate segments in the current file consistently.

About this task


This feature is available for Online Editor Advanced.
If your terminology includes fields, you can check them in the Lookups panel, below the actual term.

Procedure
1. Open the appropriate file in Online Editor.
In the workspace, recognized terms are marked with a red line above their corresponding words. Also, if you have the required
permissions, the Lookups ( ) panel is displayed on the right side of the screen.
2. Select a term and check its translated versions in the Lookups panel, under Terms. At this point, you can:
Select the icon next to a term to open that term in the terminology editor. Thus, you can
edit the term and make changes to the termbase directly from Online Editor.
Apply the most suitable entry by double-clicking it in the Lookups pane.
Tip: When AutoSuggest detects existing terminology, a box is displayed below the segment you are editing. Use the key arrows to navigate
the suggestions. Choose a suggestion and either press Enter or double-click it.

Results
The terminology is applied to the target segment. Until you confirm it, the target segment has the Draft status.
Parent topic: Working with translation memories and terminology
Translation statuses
A source text and a target text unit form a translation unit (TU). TUs are displayed on one row in Online Editor. Each TU has a translation status
depending on how complete the translation is.
TUs can have one of the following translation statuses at a time:

Not Translated ( ) - This target segment has not been translated or edited yet.
Draft ( ) - One of the following:
This target segment may have been changed, but it is not yet considered fully translated.
A translation memory (TM) match was applied to the segment, but the segment text has since been edited.
Translated ( ) - The initial translator has confirmed this target segment translation.
Locked ( ) - This target segment translation is locked.
Translation rejected( ) - The linguistic reviewer has rejected this target segment translation (for example, during an
internal review by the translation provider).
Translation approved ( ) - The linguistic reviewer has approved this target segment translation in a context such
as the following:
During an internal review performed by the translation provider before sending the file to client review.
As part of a review in the original format performed by the translation provider.
During a linguistic quality evaluation (LQE) performed by the translation provider.
Sign-Off rejected ( ) - The client reviewer has rejected this target segment translation during the sign-off process:
If a client reviewer finalizes the files, they should make the required changes first, and then give the segments the Signed Off status.
If the files go back to the translation provider after client review, the client reviewer should leave the segments as Sign-off Rejected,
so that the translation provider can see what changes are required and implement them.
Signed off ( ) - The client reviewer has approved this target segment translation and has signed off on it.
Parent topic: Filtering segments
Supported browsers
Trados GroupShare supports several browsers as per the following priority order:
1. Google Chrome (latest version) -
Note: We strongly recommend you to use Google Chrome for Online Editor.
2. Mozilla Firefox (latest version)
3. Microsoft Edge (latest version)
Note: Limited support for Online Editor. We strongly recommend you to use Google Chrome.
4. Internet Explorer (11 only)
Restriction: Online Editor does not support Internet Explorer.
5. Safari (latest version)
Parent topic: Installing Trados GroupShare
Standard roles
Trados GroupShare is built with default users/role with predefined permissions for managing the most common actions.

SA (System Administrator)
Trados GroupShare is built with the default System Administrator user which is available in the Users view, from the root organization.
The System Administrator:
Is member of the Administrator role in MultiTerm Administrator and in all Trados GroupShare organizations and resource libraries.
Has unrestricted rights and can perform any activity in Trados GroupShare and in MultiTerm Server.
Is automatically a member of the Expert User role in every MultiTerm termbase.
Has default access to the System Configuration view to check licensing information and manage server and databases.

MultiTerm roles
When you install MultiTerm Server on your computer, two new standard users are added to Trados GroupShare in the Root Organization:
MultiTerm Super user/role
MultiTerm Guest user/role

MultiTerm Super user/role


The first user of MultiTerm Administrator assumes the identity of the Super user/role.
The Super user/role:
Has unrestricted rights and can perform any activity in the MultiTerm system.
Is an administrator and is automatically a member of the Expert User role in every MultiTerm termbase.
Can add other users to the Administrator role.
Cannot be deleted.
Login rules for the MultiTerm Super
MultiTerm server does not allow the MultiTerm Super to log in more than once at the same time.
Provided no super user is already logged in, super can always log in, even if the maximum number of concurrent connections to the server
has been reached.
Recommendations for the MultiTerm Super
Edit the user account for MultiTerm Super as soon as possible, and change the password from its default value, super, to a more secure
one.
Do not use the MultiTerm Super account routinely for administrative tasks. Give administrator rights to one or more other user accounts,
and reserve the MultiTerm Super account for special circumstances.

MultiTerm Guest user/role


The MultiTerm Guest user is a member of the predefined Public role in every termbase on MultiTerm Server.
Because membership of the Public role grants read-only access to termbase entries, the MultiTerm Guest user account might be suitable for
termbase visitors.
The MultiTerm Guest user cannot log in to MultiTerm Administrator as an administrator.
You can customize the MultiTerm Super and MultiTerm Guest user accounts and create new users/role in order to better organize your translation
team.
Parent topic: User roles
Related tasks
Creating roles
Assigning roles to users
Removing roles from users
Dependencies between permissions
Some permissions need other permissions to be useful. For example, to edit any resource, in addition to the Edit permission, you need the
corresponding View permission.
Trados GroupShare does not automatically check if there are underlying dependencies for the permissions that you assign to roles. As a Trados
GroupShare administrator, make sure to give all the additional permissions required so that users can perform the required actions.
Note: Every user needs the View Organization permission.
Write and Delete dependencies

These permissions Need these ones


Any Delete permission
The corresponding Read (or View) and Write permissions

Any Write, Edit or Manage permission


The corresponding Read (or View) permission

Example
To edit an organization, you need the following permissions:
Edit Organization
View Organization
Additional specific dependencies

These permissions Need these ones


View TM
View fields
View language resource

Edit TM
View TM
View fields
View language resource

Add TM
View organization
View container
View TM
View fields
View language resource

Delete TM
Edit TM
View TM
View fields
View language resource
These permissions Need these ones
Re-index TM
View TM
View fields
View language resource
Edit TM
Write TU
Read TU

Read TU
View TM
View fields
View language resource

Write translation unit


View TM
View fields
View language resource
Read TU

Delete translation unit


View TM
View fields
View language resource
Write TU
Read TU

Batch delete translation unit


View TM
View fields
View language resource
Delete TU
Batch edit TU
Write TU
Read TU

Import translation unit


View TM
View fields
View language resource
Write TU
Read TU
These permissions Need these ones
Export translation unit
View TM
View fields
View language resource
Read TU

Parent topic: User permissions


Related tasks
Adding permissions to user roles
Removing permissions from user roles
Assigning permissions to user groups
Step 2: Assigning files to users
Step 3: Updating file phase
Step 4: Completing assignments
Step 5: Advancing assignments to the next phase
Step 6: Completing projects
Step 2: Planning work on assignments
Step 3a: Completing assignments in Trados Studio
Step 3b: Completing assignments in the Online Editor
Step 4: Completing projects
Studio general conrefs
Long name of the product: Trados Studio
Short name of the product: Trados Studio
Full name and current version of the product: Trados Studio 2022 SR1
Standalone current version: 2022 SR1
CURRENT VERSION
Short name and current major version of the product: Trados Studio 2022
Full name and current major version of the product: Trados Studio 2022
Short name and current patched version of the product: Trados Studio 2022 SR1
Full name and current patched version of the product: Trados Studio 2022 SR1
Short name and 2017 SR2 version of the product: Trados Studio 2017
Full name and SR2 version of the product: Trados Studio 2017
PREVIOUS VERSIONS
Previous version Trados Studio 2021
Full name and 2017 SR1 version of the product: Trados Studio 2017 SR1
Short name and 2017 SR1 version of the product: Trados Studio 2017 SR1
Standalone previous version: 2017
ENTERPRISE CONREFS THAT CANNOT BE TAKEN FROM EXTERNAL CONREF/VARIABLE TOPICS
WorldServer full name:WorldServer
WorldServer short name: WorldServer
TMS full name: RWS TMS
TMS short name: TMS
EDITIONS NAMES
Starter short name: Starter
Express Commuter version: Express Commuter
Express version: Express
Freelance edition: Freelance
AUTOMATED TRANSLATION PROVIDERS
BeGlobal long name: BeGlobal
BeGlobal Enterprise: BeGlobal Enterprise
BeGlobal short : BeGlobal
Trados Live: Trados Live
Language Cloud: Language Cloud
Terminology offering from Language Cloud: Trados Terminology
Language Cloud short: Language Cloud
Language Cloud uicontrol: Language Cloud
BestMatch: SDL BestMatch service
AdaptiveMT: AdaptiveMT
Google Translate: Google Cloud Translation
SDL Automated Translation: RWS Automated Translation
SDL ATS Community: SDL ATS Community
BeGlobal Online: BeGlobal Online
WorkGroup edition: Workgroup
SDL Account: RWS Account
Server product Trados GroupShare
Passolo Passolo
Help deliverables links
Migration Guide: Trados Studio 2022 SR1 Migration Guide
Installation Guide: Trados Studio 2022 SR1 Installation Guide
Help location: Trados Studio 2022 SR1 Help
QSG Translating and reviewing: Translating and Reviewing Documents Quick Start Guide
QSG Project management: Project Management Quick Start Guide
QSG TM Management: Translation Memory Management Quick Start Guide
Release Notes: Trados Studio 2022 SR1 Release Notes
WorldServer integration: WorldServer and Trados Studio Integration Guide
WorldServer Help: WorldServer Help
Licensing Help: Licensing Help
GS Install Guide Trados GroupShare Installation Guide
.NET versions
.NET version: 4.8
.NET installer: ndp48-x86-x64-allos-enu.exe
File paths
Studio file path external version: Studio 2022
Studio file path internal version: Studio17
Studio update path: studio16updates
Studio msi version: 17
Studio app version: 17
Studio patch version: 17.0.0
Studio CU version: 7
TranslationStudio17.msi
%TEMP%\Studio17Updates

General
SautinSoft
Translation memory advanced settings
To access the translation memory advanced settings in Trados GroupShare, go to the Resources view, select the Translation Memories tab and
select the name of the TM you want to edit. Then go to the Advanced Settings tab.

Recognize settings
The Recognize settings allow you to:
enable or disable recognized tokens from the check boxes.
enable concordance search

Enable character-based concordance search


Normally, for non-alphabetic writing systems, you need to enable character-based concordance searches.
For alphabetic writing systems, be aware of the size implications. For alphabetic writing systems, character-based concordance searching adds
about 8 KB per TU. Normally you would not enable this feature if you have more than one TM with more than 100 000 TUs. Usually, therefore,
you do not have character-based concordance searching on server-based TMs.

Word Count settings


You can control how the word count engine reports words that are separated by hyphens, dashes or formatting tags for your TM.
If you enable the option to Count as one if words:
Are hyphenated, words that contain hyphens count as single words. For example, with this enabled, "two-wheeled vehicles" counts as two
words, with this disabled, it counts as three words. By default this is enabled.
Are joined by dashes, words that contain dashes count as single words. For example, with this enabled, "two -wheeled vehicles" counts as
two words, with this disabled, it counts as three words. By default this is enabled.
Contain formatting tags, you set the word count engine to not break words that contain formatting tags.
Contain apostrophes, you make words that are separated by apostrophes count as a single word.
Parent topic: Configuring server-based TMs
Related tasks
Step 3: Creating server-based TM
The Activation Server
The Activation Server is the live server hosted by RWS, which manages the products and activation codes for Trados GroupShare.
When you perform online activation for a single-user license, this server validates the activation code for Trados GroupShare.
When an administrator performs online activation for a network license from their installation of the license server, this server validates the
activation code for Trados GroupShare.
Parent topic: Working with single-user and network licenses
WebHooks Notifications (callbacks)
After a WebHook URI was registered for a certain event you will get callbacks when that event occurs. The callback is a POST request.

Request headers
Parameter Explanation
ms-signature An SHA 256 signature on the request body. The signature uses the secret key from the WebHook registration.
Example: "
sha256=275F1BFF2327BBAF7F61A1BB1920BAC0A5295C2F4C78350324247031D37A8031"

X-Correlation-ID A correlation GUID - this is the actual id of a webhook item (from GroupShare)

Request body
Body type Explanation
JSON (application/json)
The event details as a JSON string.
Example request body of an assignment event callback:
{
"Id": "9745600de970448b97f1cff97dbf1860",
"Attempt": 1,
"Properties": {},
"Notifications": [
{
"Action": "Sdl.GroupShare.Events.V2.AssignmentEvent",
"From": [
{
"userEmail": "[email protected]"
}
],
"To": [
{
"userEmail": "[email protected]"
}
],
"LanguageFileId": "1c210645-8b48-4557-b6e3-d50d1ca18ab4",
"ProjectId": "6ed3763d-0a93-4484-89e3-c9b4b824701d",
"RaisedBy": "test",
"Server": "groupshare.local"
}
]
}

Parent topic: Using the Trados GroupShare WebHooks Service


Licensing
When you purchase Trados GroupShare, you must activate it before you can use it. Activation means that the product is licensed for use on the
machine where it is installed.
Licensing videos
Working with single-user and network licenses
Activating Trados GroupShare
The Product Activation dialog is where you can perform all license related functions.
Single-user licenses
A single-user license activates Trados GroupShare on that computer.
Network licenses
Network licensing (or commuter licensing) provides the flexibility required in an enterprise environment to distribute a limited number of
licenses among a large number of clients.
Modifying your proxy settings
If you have problems connecting to the Activation Server during online activation or deactivation, you may want to modify your proxy server
settings. Alternatively, you can choose to activate or deactivate offline.
Viewing your license status
You can view your current license status if you want to check details about license validity or license feature coverage.
Error message solutions
Application Server - restart options
The Application Server may restart or not depending on the changes you make to the configuration or the licensing options.
Splitting segments
If the initial segmentation of a file contains source segments that are too long (perhaps as a result of improper formatting in the source text) and that
should be split, you can correct the segmentation and split the segments.

Before you begin


The project which the file belongs to must have the Allow editing of source text in segments setting enabled.

About this task


This feature is available for Online Editor Advanced.
Changing the initial segmentation of a file may affect the matches delivered by a translation memory, because the segmentation in the translation
memory might become different from the one in the file. You can revert to the initial segmentation of a split segment by merging it.

Procedure
1. Open the appropriate file in Online Editor.
2. Select the target area of the segment that you want to split.
3. On the Home tab, in the Segments group, select Other Actions > Edit Source.
4. In the source segment, click in front of the word that should start the next segment.
5. Select Other Actions > Split Segment.

Results
The segment is split. If the segment already has a translation, that translation is now placed in the first split segment.
Parent topic: Translating content
Copying formatting from the source text to the target text
If you prefer to format segments only after you have translated them, you can do so more quickly by copying formatting from the source text
directly to fragments of the target text.

Procedure
1. Open the appropriate file in Online Editor.
2. In a target segment of your choice, select the text to which you want to copy source formatting.
3. On the Home tab, in the Formatting group, select Apply Formatting.
4. In the source text, select the formatting you want to apply to the selected target text.
Parent topic: Formatting segments
Exporting ordinal followers
You can reuse ordinal followers across translation memories (TMs) by exporting and importing them in .txt format.

Procedure
1. Go to the Resources view.
2. In the Language Resource Templates tab, select the checkbox corresponding to the template of choice.
3. Select Edit.
4. In the [language resource template name] dialog, select Language Resources.
5. Identify the language for which you want to export existing ordinal followers.
6. In the [language resource template name > language] dialog, select Ordinal Followers.
7. Select Export all.
8. Select Finish.
Parent topic: Ordinal followers
Main TMs are not updated
At the end of a project Trados GroupShare updates the main translation memories (TMs) from translation units (TUs) in the project TMs.
Usually Trados GroupShare updates the main TM when you finalize the project. If this is not happening:
Check that the Update main TMs task has run. Usually this task is part of the finalize task sequence. Check this is the case.
Check the permissions needed to write to the main TMs.
Check in the project settings that the project manager is specified as the user to update the main TMs.
Check that the finalize batch task is set to run as a consequence of finalizing the project.
Parent topic: Problems and solutions
Fields
Fields hold supplementary data for each translation unit (TU) in a TM.
You usually modify change fields by changing the field template.

Types of Fields
GroupShare maintained fields ("system fields")
Trados GroupSharemaintains a number of system fields for each TU, such as:
created by and creation date
modified by and modification date
last used by and last used date
For example, when you edit a TM entry, Trados GroupShare automatically updates the value of the modified by and modification date
fields.
User maintained fields ("custom fields")
The value of custom fields is set by a user, for each TU.
In Trados GroupShare, you can add your own custom fields to a field template.
In the client (Trados Studio), view or change the values of user maintained fields in the TM Editor. Use the Fields and settings dialog box
under the TM settings.

How to use fields


You can display field values, and you can filter TUs by their field values, for example to find all TUs that were created after a certain date.
You also add penalties to TUs, based on their field values.
Creating field templates
You can speed up the creation process of TMs that share the same fields. Field templates enable you to work consistently across your
TMs.
Editing field templates
You can modify field templates any time. Any changes you make to your field template impact the way your TM works.
Exporting fields as template
When you export fields from existing TMs, these are saved as a new field template that you can reuse.
Parent topic: Translation memories (TMs)
Step 3b: Completing assignments in the Online Editor
When project managers move project files to a phase in Trados GroupShare, the users who are assigned to that phase receive automatic
notification emails. The notification emails inform users of the tasks they must work on and of the due date. The assigned users can start working
on their translation or review tasks in Online Editor. Another possibility is to work on your translations or reviews in Trados Studio.

Procedure
1. Do one of the following:
Click the file-name link in the notification email to open your Trados GroupShare assigned documents in Online Editor.
Log in to Trados GroupShare, go to Dashboard, and, under Your Tasks, select near the assignment you want to work on.
Log in to Trados GroupShare, go to Projects, select the project where the assignment is stored, select the checkbox next to the file
you want to work on, and then expand the Open in Editor list. Choose Basic or Advanced.
Important: You cannot check out from Online Editor files which are already checked out in Trados Studio. Wait until the file is checked in
from Trados Studio before you check-it out (open it) in Online Editor.
The file automatically opens in Online Editor and is ready for editing.
2. Edit the file in Online Editor.
3. When finished, on the right-hand side corner of the toolbar, select Check-in file.
Important: You can use the Force check-in button if you are assigned one of the following roles: Project Manager, Power User or
Administrator. The Force check-in option is available from Trados GroupShare, when you open the project and select the file which is
checked out in Online Editor.
4. In the Check In dialog, do one of the following:
If you are the only or last user to edit the file, enter a comment and, under Change Phase to, select the next phase the file advances
to. If you still have work to do, do not change the file phase. Select Check-in. All your changes are now saved.
If there are still other people working on the same file as you, enter a comment, if necessary. You cannot change the file phase at this
point. The last user who checks in their changes can change the file phase. All your changes are now saved.
Parent topic: Workflow for shared projects started in Trados GroupShare
Related concepts
Standard roles and permissions
Dependencies between permissions
Translation statuses
Support for right-to-left scripts
If you select a display language that uses a right-to-left script (for example, Arabic) before opening a file in Online Editor, the options on the Online
Editor user interface will be displayed in that language from right to left.

Parent topic: Navigating the Online Editor user interface


Project-level reports and background tasks
Trados GroupShare reports present a detailed account of your translated files. Trados GroupShare completes the actions which require a long
time in the background, as background tasks.

Reports
Reports are available only for projects created in Trados GroupShare. The following three reports are available:

Analyze Files report


This report displays statistics and settings configuration for project at different stages:
Initial project creation report, which is generated automatically when the project is created.
Full report, which contains information on all the files in the project, including any mid-project add/update file changes.
Add project file operation/Update project file operation. This will generate a report based on the files added/updated after the initial project
creation.
Limitation
Projects generated from Trados Studio and corrupted GroupShare projects do not include an Analysis report. Because of this, Trados
GroupShare cannot generate Full reports for such projects. The reports will be generated automatically for individual Add/Update project
operations.

Audit Trail report


This displays the following information per project file:
actions performed on project files in chronological order
details per each performed action: event timestamp, user, file version

Post-translation analysis (PTA) report


Generate this report to get a detailed overview of your TM leverage and translators' effort on individual file. This is useful for checking the work
progress on the file. When the project is complete, this report can help you determine how much each translator can bill for the project file. PTA is
generated automatically as part of the Finalize task.
The PTA report displays the following information for each translator who has worked on the file:
number of translated words, segments and characters
type of match rate: Perfect Match, Context Match, Exact Match, Fuzzy Band, New (no TM leverage)

Background tasks
Background task Description
Field propagation
When a field template is changed, Trados GroupShare updates all the translation
memories (TMs) that use the field.

Language resources propagation


When a language resources template is changed, Trados GroupShare updates all the
TMs that use that language resources template.

Publish projects
When a task is published from Trados GroupShare, the publication process in
Trados GroupShare is a background task.

Re-compute fuzzy indexes Re-index TM


These are TM tuning tasks, started from the Translation memories view.

Translation unit import and export


Trados GroupShare imports and exports translation units as background tasks.
Background task Description
System
The system task.

Post Translation Analysis report Trados GroupShare generates Post Translation Analysis reports as background
tasks.
Delete Organization Trados GroupShare deletes organizations and their resources in the background. If
the containing resources are sourced in a different organization than the one being
deleted, only the references to these resources are deleted instead.
The background task details shows information on task duration and the IDs of every
resource deleted.

Project Package Import and Project Package Export Packages for working with Trados GroupShare projects in an offline workflow are
imported and exported in the background. You can check details about each import
and export and also retrieve the packages from the Background Tasks view.

Required permissions
All users can see the background tasks that they created.
Users with View Background Tasks permission also see the background tasks created by other users on that Trados GroupShare server.
Users with Background Tasks Administrator permission have access to more information about all background tasks, can cancel tasks in
progress or delete tasks from the list.

View background tasks


To open the Background Tasks view and see the list of all background tasks for your Trados GroupShare server, select the Background Tasks
view on the Home page.
By default, Trados GroupShare displays only the tasks that you requested. Check the Show tasks for all users option to see the System tasks and
the tasks that other users triggered. You can also use the filter criteria on the left of the page to filter by keywords, task type or task status. To
combine filtering criteria with sorting options, display the tasks in List View.
Trados GroupShare shows how many of the total number of tasks matching the filter criteria is currently displaying. If there are more tasks
available, scroll down the page to load more task results.
Background tasks older than 60 days are automatically deleted, so as to prevent the failure of import and export operations.
Viewing project level reports
You can view report details irrespective of the project's file phases.
Printing project level reports
You can print the reports irrespective of the project's file phases
Saving project level reports
You can save the reports irrespective of the project's file phase. Several formats are available.
Parent topic: Working with reports
Change log
This is a list of changes made to the Trados GroupShare documentation portal since its official release on June 15, 2020.

Changes Description Date


Trados GroupShare 2020 SR1 CU5 Several updates were made to the help July 21, 2021
updates topics to bring them in line with the
application changes for SR1 CU5
Parent topic: Welcome to the Trados GroupShare 2020 SR1 documentation
Performing concordance searches in the translation memory
When you perform a concordance search, you search through a translation memory (TM) for words or fragments within translation units (TUs).

About this task


This feature is available for Online Editor Advanced.

Procedure
1. Open the appropriate file in Online Editor.

If you have the required permissions, the Lookups panel is displayed on the right side of the screen.
2. Select the target area of the segment for which you want to find translations and press F3.
The translations available for that segment are displayed in the Lookups panel, along with their corresponding scores.
Tip: In the lower part of each entry, you can view details such as the date and time when they were added to the translation memory.
3. In the search box, enter a word, and select whether you want to search for it in the source text or in the target text. Press Enter.
Note: To get the best results, make sure that you enter the entire word that you want to search for, not just a part of it. For example, enter
office instead of offic.
You can also clear your search history by selecting Clear search in the list:

Results
The results are displayed in the Lookups panel.
Parent topic: Working with translation memories and terminology
Importing abbreviations
You can reuse abbreviation lists across translation memories (TMs) by importing and exporting them in .txt format.

Procedure
1. Go to the Resources view.
2. In the Language Resource Templates tab, select the checkbox corresponding to the template of choice.
3. Select Edit.
4. In the [language resource template name] dialog, select Abbreviations.
5. Select Import.
6. Select Finish.
Parent topic: Abbreviations
Modifying the layout of the workspace
The way segments are displayed during translation helps you focus on your task differently. In Online Editor, you can choose between two layout
options: vertical (the source and target segments are displayed in two columns, one next to the other) or horizontal (each target segment is
displayed under its corresponding source segment).

Procedure
1. Open the appropriate file in Online Editor.
2. On the View tab, in the Layout group, do one of the following:
To have the source and target segments displayed in two separate columns, one next to the other, select Vertical.

To have each target segment in the workspace displayed under its corresponding source segment, select Horizontal.

Parent topic: Navigating the Online Editor user interface


Editing roles
When no longer up-to-date, a role's name or its associated permissions can be modified to reflect new requirements.

Procedure
1. Go to the Users view and select the Permissions tab.
2. Select Edit Roles and, from the drop-down menu, select the role you want to edit.
Tip: Alternatively, identify the role in the right-hand side pane and select .
3. Edit the role name or its permissions.
4. Select Finish.
Parent topic: User roles
Reviewing content with Track Changes
You can track all the changes you make to a text, which is useful especially when reviewing translations.

About this task


Reviewing content increases the quality of your translated content.

Procedure
1. Open the appropriate file in Online Editor.
2. On the Review tab, in the Tracking group, select Track Changes.
3. Edit the segments. If you add something, the word Inserted is placed after the user who made the change. If you delete something, the word
Deleted is placed after the user who made the change.

Results
All the changes you make from this point on are tracked.

You can view all of your changes by selecting the Revisions panel on the right side of the
screen. When the file you are working on contains revisions, a small dot is displayed on the Revisions button.
Username for tracked changes
If you are logged into RWS Language Cloud, this username is taken from your cloud account name. The cloud account name is generated from the
First Name and the Last Name information available on your cloud user profile.
If you are not logged into RWS Language Cloud, Trados GroupShare uses your Windows username instead. You first set this ID after installing
Trados GroupShare and you can change it at any time from File > Setup > Users.
Parent topic: Reviewing translated content
Undoing or redoing actions
You can undo or redo actions to make sure that the asset you submit does not contain any errors.

Procedure
1. Open the appropriate file in Online Editor.
2. On the Home tab, in the History group, do one of the following:
To undo your last action, select Undo.
If you undid your last action and you decide to redo it, select Redo.
Note: Replace or Replace All operations cannot be undone.
Parent topic: Working with Online Editor
Workflow for shared projects started in Trados Studio
Trados Studio and Trados GroupShare synchronize continuously to support your projects and file assignments.
Once a project is created in Trados Studio, you can publish it on the Trados GroupShare platform in order to assign the project work to one or
more translators and reviewers. Translations projects can be managed in both Trados Studio and Trados GroupShare but only Trados Studio
offers the infrastructure required for enabling work assignment.
To complete a shared project started in Trados Studio:
1. Make sure that you are a member of the Project Manager role or that you are in a role which includes permissions required for publishing
projects and managing file assignments.
2. Go through the workflow steps below:
a. Step 1 - Publish projects to Trados GroupShare
b. Step 2 - Assign files to users
c. Step 3 - Update file phase
d. Step 4 - Complete assignments
e. Step 5 - Advance assignments to next phase
f. Step 6 - Complete projects
Step 1: Publishing projects to Trados GroupShare
Publish a Trados Studio project to a Trados GroupShare server so that multiple users can work at the same time to complete translation
tasks.
Step 2: Assigning files to users
After publishing your project to Trados GroupShare you must delegate the translation work to specific users, so that they can start
translating or reviewing the project files. Remember that you may have already assigned users to files or phases on the Trados GroupShare
page of the Create a New Project wizard.
Step 3: Updating file phase
Users can access the files assigned to them for a specific phase. When you assign files to a project phase, you inform the assigned users
what their translation tasks are.
Step 4: Completing assignments
When the assigned users receive notification of a pending assignment, they must check out the assigned file from the Trados GroupShare
server.
Step 5: Advancing assignments to the next phase
Once the assigned users complete their translation or review work, they must check in the documents to the server and advance them to the
next project phase.
Step 6: Completing projects
When users complete all the assignments, you can mark the project as Complete. At this stage, all the project files are usually in Finalisation
phase and assigned to the user who can mark it as Complete.
Parent topic: Working with projects
Related tasks
Creating projects
Product editions and features
This topic contains the available product editions and product features that a network-licensing administrator can configure for Trados
GroupShare.

All available options


Configuration file example generated if all edition are available on the Trados License Server
<LicenseDefinition>
<LicenseEdition>
<Name>ProfessionalEdition</Name>
<IsCurrent>true</IsCurrent>
<Features>
<Feature>
<Name>AllowTQA</Name>
<IsDefault>true</IsDefault>
</Feature>
<Feature>
<Name>AllowRegulatedIndustries</Name>
<IsDefault>true</IsDefault>
</Feature>
</Features>
</LicenseEdition>
<LicenseEdition>
<Name>WorkgroupEdition</Name>
<IsCurrent>true</IsCurrent>
<Features>
<Feature>
<Name>AllowTQA</Name>
<IsDefault>true</IsDefault>
</Feature>
<Feature>
<Name>AllowRegulatedIndustries</Name>
<IsDefault>true</IsDefault>
</Feature>
</Features>
</LicenseEdition>
<LicenseEdition>
<Name>ExpressEdition</Name>
<IsCurrent>true</IsCurrent>
<Features>
<Feature>
<Name>AllowTQA</Name>
<IsDefault>true</IsDefault>
</Feature>
<Feature>
<Name>AllowAutoSuggest</Name>
<IsDefault>true</IsDefault>
</Feature>
<Feature>
<Name>AllowPerfectMatch</Name>
<IsDefault>true</IsDefault>
</Feature>
<Feature>
<Name>AllowRegulatedIndustries</Name>
<IsDefault>true</IsDefault>
</Feature>
</Features>
</LicenseEdition>
</LicenseDefinition>

Example for a Professional Edition license


Example using only Professional Edition within a configuration file
<LicenseDefinition>
<LicenseEdition>
<Name>ProfessionalEdition</Name>
<IsCurrent>true</IsCurrent>
<Features>
<Feature>
<Name>AllowTQA</Name>
<IsDefault>true</IsDefault>
</Feature>
</Features>
</LicenseEdition>
</LicenseDefinition>
Parent topic: Activating the Trados License Manager (administrators)
Importing ordinal followers
You can reuse ordinal followers across translation memories (TMs) by importing and exporting them in .txt format.

Procedure
1. Go to the Resources view.
2. In the Language Resource Templates tab, select the checkbox corresponding to the template of choice.
3. Select Edit.
4. In the [language resource template name] dialog, select Language Resources.
5. Identify the language for which you want to import existing ordinal followers.
6. In the [language resource template name>language] dialog, select Ordinal Followers.
7. Select Import.
8. Select Finish.
Parent topic: Ordinal followers
Assigning permissions to user groups
You group users by assigning them roles in the same organization. Working with specific user groups is useful when you want all its members to be
assigned the same role and be given access to the same resources.

Before you begin


Make sure you created an organization for your user group. Make sure you added the relevant users to the user group.

About this task


Organizations can be seen as user groups. For example, you can create a user group that has Translator role permissions to a translation memory.

Procedure
1. Go to the Users view and select the Permissions tab.
2. Select the organization corresponding to the user group of interest.
3. In the right-hand side pane, identify the role you want to assign to your user. If necessary, select .
4. Under the role of your choice, select the Grant [role name] permissions to ... field.
5. In the list, select the user you want to assign the role to.
Note: Roles assigned within an organization propagate to its subsidiaries.
6. Repeat step 5 to add as many users as you need to.
Important: It is possible, but not advisable, to allow a number of people to log in with the same user name.

Example: Assign permissions to a Translator group and to a Reviewer group


You want to make sure that all your translators who specialize in the English-Japanese (EN-JP) language pair work consistently irrespective of the
project they are assigned. You decide to create a user group where all users have Translator role permissions to a translation memory.
1. Create the Translators EN-JPorganization for your user group.
2. Assign your EN-JP translators the Translator role within the Translator EN-JPorganization.
3. Assign the translators the EN-JP language direction.
4. Within the Translators EN-JPorganization, add a link to the translation memory or move the translation memory into the organization.
Next, you want to provide another group of users, a reviewer group, different permissions over the same translation memory. You decide to create
a Reviewers EN-JPorganization where each member has Reviewer role permissions, and then add a link from the translation memory to the
Reviewers EN-JP organization.
Parent topic: User permissions
Related concepts
Dependencies between permissions
Components update
With this release, we have removed the Microsoft Visual C++ 2008, 2010 and 2013 Redistributable components from the list of GroupShare's
dependencies. Here's the updated list:
Microsoft Visual C++ 2019 Redistributable x86/x64
rabbitmq-server-3.11.16
otp_win64_25.3.2
chef-client-13.2.20-1-x64
Microsoft® OLE DB Driver 18 for SQL Server 18.6.5.0_x64
URL Rewrite 2.1
IIS Application Request Routing (ARR) 3
.NET Hosting 6.0.16
.NET Framework 4.8
OpenJDK8U-jre_x64_windows_hotspot_8u372b07
RaptorDBConverter 1.2
Microsoft SQLSysCLRTypes for SQL Server 2012
SQL Server Native Client for SQL Server 2012
SQL Server Shared Management Objects for SQL 2012
Parent topic: Changes introduced in Trados Groupshare 2020 SR1 CU9
Translating and undoing file check-out from Trados
GroupShare
When files are in translation (therefore, checked out), you can revert the check out operation, from Trados GroupShare, if you are assigned one of
the following roles: Project Manager, Power User and Administrator.

About this task


The undo check-out operation disconnects the persons who are currently translating the files in Online Editor and does not preserve the changes
performed on the file in Online Editor. This option is particularly useful if you experience server or file conversion issues.

Procedure
1. Translators do one of the following:
Click the file-name link in the notification email to open their Trados GroupShare assigned files in Online Editor.
Log in to Trados GroupShare, go to Dashboard, and, under Your Tasks, select near the assignment translators want to work on.
Log in to Trados GroupShare, go to Projects, select the project where the assignment is stored, select the checkbox next to the file
translators want to work on, and then select Open in Editor.
Important: Translators cannot check out from Online Editor files which are already checked out in Trados Studio. Wait until the file is
checked in from Trados Studio before you check-it out (open it) in Online Editor.
The file automatically opens in Online Editor and is ready for editing.
2. Translators edit the file in Online Editor.
3. Project Managers, Power Users and Administrators can undo the file check out in Online Editor. In Trados GroupShare, go to the Projects
view, open the project where the file is located, select the file you want to force check in, expand Force check-in, and then select Undo
check-out.
Parent topic: File translation and check-in
Changes introduced in Trados GroupShare 2020 SR1 CU7
This page contains an overview of the new features and fixed brought by Cumulative Update 7 for our latest major release, Trados GroupShare
2020 SR1.
We are constantly reviewing and improving our products. We release enhancements and fixes to resolve customer issues as and when required.
All changes and fixes are bundled into the cumulative update which you can install from RWS Account > Downloads .
Mid-project updates
Update current project with new source and reference files without disrupting current work.
Updated documentation
Documentation is now more detailed.
Upgraded components
Editor Service Rounter and BCM-S now run on .NET 6.
Service password encryption changes
This release changes the encryption method for some services.
Added support for new files types
The CU7 release expands on the range of supported file types.
Fixed issues
This page contains an overview of the new features and fixed brought to Trados GroupShare 2020 SR1 with Cumulative Update 7.
Known issues
This page contains a list of known issues related to Trados GroupShare 2020 SR1 CU7.
Parent topic: What's new in Trados GroupShare
Reference conrefs for SDL Online Editor
Source content copying for segments with revisions
Several changes are made to the information in target segments if you copy source content to target segments that already contain revisions made
with Track Changes.
In target segments, when copying source content:
All the revisions (insertions and deletions) are accepted and the resulting text is displayed as a deleted revision.
The source content is copied as an inserted revision.
The revisions made to the source content are accepted and displayed as plain text.
The comments inserted in the source content are displayed as plain text.
The deleted comments (from the source content) is not displayed at all.
Parent topic: Copying source content to target segments
Changing settings for project archiving
When the list of Trados GroupShare projects contains too many Completed projects, the overall performance can be affected and project
management is hindered. That is why it is useful to archive completed projects and reduce the visible list of Trados GroupShare projects.

Procedure
1. In the Trados GroupShare Console navigation tree, select SDL Trados GroupShare > Settings.
2. In the Settings pane, under Project Archiving Settings, enable automatic project archiving.
3. Type the number of days after which Completed projects are automatically archived. You can set a period of 1 to 365 days. The default
value is 30 days.
4. In the Actions pane, select Apply Changes to save the change.
Parent topic: Trados GroupShare Console settings
Projects status overview in the Dashboard
Project Managers can view a comprehensive status report of all the translation projects that are in progress in the Trados GroupShare Dashboard.
The Dashboard is the first view displayed when logging in the Trados GroupShare website and it provides information and updates relevant to a
project manager.
The Dashboard contains a set of pre-defined reports informing users of the:
Projects due soon - Projects approaching their delivery deadlines.
Tasks due soon - Tasks assigned to the current logged-in user.
Projects created per month - Number of words that were translated.
Words per month - Number of projects created per month (chart format).
Words per organization - Number of words translated per organization (chart format).
Top language pairs - Percentage of language pairs used (chart format).
Statistics - Statistics associated to the objects created in. Trados GroupShare
Downloads - Complete status of a requested download tasks (a link to the requested file is provided).
Locking and unlocking segments or parts of segments
By locking segments or parts of segments, you can protect them from being modified. You can unlock protected segments or parts of segments if
you need to modify them.

About this task


This feature is available for Online Editor Advanced.
When a segment or a selection is locked the following actions (and their associated shortcuts are disabled):

No. Disabled action ...if segments are locked ...if selections are locked
1. Cut
2. Paste
3. Clear Formatting
4. Clear All Formatting
5. Apply Formatting
6. Change Case
7. Insert Characters
8. Confirm Translation
9. Copy Source to Target
10. Copy All Source to Target
11. Clear Target Segments
12. Clear Draft Segments
13. Segment actions (edit, split,
merge, change status)
14. Track Changes
15. Accept revision
16. Reject revision
17. Add comment
18. Delete comment

Procedure
1. Open the appropriate file in Online Editor.
2. Do one of the following:
If you want to lock or to unlock a segment, click that segment.
If you want to lock or to unlock a part of a segment, select it.
Note: You can only lock parts of segments that do not contain formatting tags or revisions made with Track Changes. If you lock a part of a
segment, other users cannot remove the lock.
3. On the Home tab, in the Segments group, do one of the following:
To lock a segment, select Segment Locking > Lock Segment or press Ctrl+L.
To unlock a locked segment, select Segment Locking > Unlock Segment or press Ctrl+L.
To lock a part of a segment, select Segment Locking > Lock Selection
To unlock a locked part of a segment, select Segment Locking > Unlock Selection
Locked segments appear dimmed and have a lock symbol next to their status, on the right side of the screen. Similarly, locked parts of
segments are delimited by two lock symbols—one at the beginning and one at the end of the selection.
Parent topic: Translating content
Filtering segments
Filtering segments is particularly useful, for example, in making sure that there are no untranslated segments left in a file.

Procedure
1. Open the appropriate file in Online Editor.
2. On the right side of the screen, select Filters .
3. In the Filters panel, select the Enable Filters checkbox.
4. Do one or more of the following:
To filter segments according to their status, origin, or origin before adaptation, expand the Segment Attributes node and select the
appropriate attributes in the Status, Origin, and Origin Before Adaptation lists.
Tip: The origin of a segment refers to the way in which it was populated—whether by typing a translation manually, copying it from
the source segment, or applying a translation unit from a translation memory or from an automated translation server. On the other
hand, the origin before adaptation applies to segments which have been changed multiple times and refers to the previous origin of the
segment. For example, if a segment was machine-translated initially, but you made a few corrections later on, its current origin is
Interactive (you performed the last change by typing a translation manually) and its origin before adaptation is Automatic Translation
(the origin before the last change).
The distinction between origin and origin before adaptation is helpful because a new translation origin is created when you change the
segment status.
To filter segments according to the changes suggested during the review phase, expand the Review node and select the appropriate
check boxes or provide the relevant information:
Segments with track changes
Segments with verification messages
Segments with comments
Segments with TQA (quality assessments)
Revisions mismatch - This filter displays segments that contain revision mismatches between source and target. More
specifically, the filter makes a comparison between the deleted and inserted characters in a segment's source and target. In
order for these segments to be displayed in the list, there have to be differences like: the source has two inserted characters
and the target one inserted character, or the source contains a revision and the target does not.
Revisions from - Specify a start date and an end date.
Revisions added by - From the list, select the user who performed the revisions.
To filter locked or unlocked segments, expand the Segment Locking node and select the appropriate checkbox.
The filters are applied as soon as you select them and the number of segments that match the filtering attributes is displayed at the top of the
Filters pane, in a form such as Filtered 16 of 184 segments. If the file you are working on contains segments with comments, only
the comments of the segments that match the filtering attributes are displayed in the Comments pane. Similarly, if the file you are working on
contains segments with revisions, only the revisions of the segments that match the filtering attributes are displayed in the Revisions pane.

Results
When you filter segments, a small dot is displayed on the Filters button. This is helpful especially if you collapse the Filters panel, because it helps
you remember that you are working with a filtered list of segments, not with all the segments in the text.
Translation statuses
A source text and a target text unit form a translation unit (TU). TUs are displayed on one row in Online Editor. Each TU has a translation
status depending on how complete the translation is.
Translation origin
A source text and a target text unit form a translation unit (TU). TUs are displayed on one row in Online Editor. Each TU has a translation
origin, namely a resource where the translation originated.
Parent topic: Working with Online Editor
Exporting TUs from server-based TMs
You can export TUs to use them later, for instance to import them in another TM.

About this task


After you start the export, Trados GroupShare performs the task in the background, leaving you free to perform other tasks. Monitor the task
progress in the Background Tasks tab, of the System Configuration view.

Procedure
1. Go to the Resources view.
2. In the Translation Memories tab, select the checkboxes corresponding to the TMs you want to export.
3. Select Export > Translation Memory.
4. Select the language pair you want to export.

Results
You receive a notification message and a link to export the .tmx file.
TM system fields
You can use these field names in the filter description when exporting translation units (TUs).
Parent topic: Translation memories (TMs)
Checking in files in Online Editor
Once you finish translating or reviewing the assigned file online, you must check in your changes to save them. Online Editor allows several users to
work on the same file, at the same time.

About this task


If multiple users work on the same file, at the same time, all users can check in their changes, but only the last user can change the file phase.

Procedure
1. Open the file in Online Editor by one of the following methods:
Click the file-name link in the notification email to open your Trados GroupShare assigned documents in Online Editor.
Log in to Trados GroupShare, go to Dashboard, and, under Your Tasks, select near the assignment you want to work on.
Log in to Trados GroupShare, go to Projects, select the project where the assignment is stored, select the checkbox next to the file
you want to work on, and then select Open in Editor.
The file automatically opens in Online Editor and is ready for editing.
2. Edit the file in Online Editor.
3. When finished, in the right-hand side corner of the toolbar, select Check-in file.
4. In the Check In dialog, do one of the following:
If you are the only or last user to edit the file, enter a comment and, under Change Phase to, select the next phase the file advances
to. If you still have work to do, do not change the file phase. Select Check-in. All your changes are now saved.
If there are still other people working on the same file as you, enter a comment, if necessary. You cannot change the file phase at this
point. The last user who checks in their changes can change the file phase. All your changes are now saved.

What to do next
In Trados GroupShare, if you are assigned one of the following roles: Project Manager, Power User or Administrator, you may use the following
options for checked-out files:
Force check-in - Select this option to check-in the file with the latest changes performed in Online Editor, despite the fact that it may still be
worked on by translators or reviewers.
Undo check-out - Select this option to revert any check-out operation. The latest changes performed in Online Editor are not saved. This
option is particularly useful if you experience server or file conversion issues.
The Force check-in and Undo check-out options are available from Trados GroupShare, when you open the project and select the file which is
checked out in Online Editor.
Parent topic: Working with Online Editor
Deactivating your product offline with a single-user license
To deactivate Trados GroupShare when you have no Internet connection, you need to use another computer with Internet access to the RWS
website where you can return the deactivation certificate.

Procedure
1. Obtain deactivation authorization:
a. Use a computer that can access the Internet and log into My Account.
b. Select the Licenses link.
c. Select the Can't deactivate online? - Deactivate offline link next to the product key you want to deactivate.
d. Follow the instructions to obtain a deactivation authorization for Trados GroupShare.
e. Copy the deactivation authorization.
2. Go to Start > GroupShare [year] > GroupShare [year] Product Activation to display the Product Activation dialog.
3. In the Product Activation dialog, select the Deactivate offline link.
4. In the Offline Deactivation page, paste the deactivation authorization into the Deactivation authorization text box.
5. Select Generate Certificate to generate the deactivation certificate.
6. Copy the deactivation certificate.
7. Complete deactivation:
a. Switch to the computer that can access the Internet and log into My Account.
b. Select the Licenses link.
c. Select the Can't deactivate online? - Deactivate offline link next to the product key you want to deactivate.
d. Follow the instructions and return the deactivation certificate to complete the deactivation process. With the license returned, you can
now activate it again with a different installation of the software.
8. Confirm deactivation:
a. Back on the computer with Trados GroupShare, check the I have returned the deactivation certificate to my account option.
b. Select the Confirm button to close the dialog.
Tip: If you did not manage to return the deactivation certificate to your account, you will find it when opening Trados GroupShare by
selecting the View certificate from last deactivation option.
Parent topic: Activating single-user licenses offline
Fixed issues
This page contains a list of issues fixed by Trados GroupShare 2020 SR1 CU6.

Fixed issues
Fixed an issue that caused duplicate project versions for Trados GroupShare projects when working with Trados Studio. (CRQ-18227)
Trados Studio projects published on the GroupShare server now correctly display their .sdlxliff translatable files in the Files view if they use
language codes with mismatching capitalization. (CRQ-4301)
You can now edit Windows users whose Display Names contain special characters. (CRQ-26671)
Trados GroupShare now enables you to create projects using any combination of batch tasks, ignoring those that are not supported.
Previously, accessing projects with project templates that included certain batch tasks was not possible from the Web UI. (CRQ-24232,
CRQ-22321)
Fixed "Single sign-on error: Error that occurred when retrieving bearer token. Response (Unauthorized): Authentication failed."
This occurred when trying to log on with an IdP user and the UpdateIdpUserInfo value was set to true. (CRQ-26224)
Trados GroupShare could not use Language Weaver Machine Translation to pre-translate files from projects created with Re-send drafts
and translated segments set to false. This issue is now fixed. (CRQ-25907)
The Reindex task was not working correctly for some TMs. This issue is now fixed. (CRQ-25942)
Reports and word counts now generate correct results when creating new projects based on project templates that have the Report internal
fuzzy match leverage setting enabled. (CRQ-25264)
When editing TMs, the Save button under the Advanced settings field now correctly stores Recognize values. (CRQ-25140)
You can now correctly generate Analyze Files reports for projects created on the Trados GroupShare Web UI. (CRQ-24891)
The Dashboard and Reporting tabs now load correctly on the GroupShare Web UI when the webapp is set to run in a sub-folder. (CRQ-
24739)
Fixed an issue with the Online Editor that caused recognized terms from termbases to disappear after confirming a segment. (CRQ-24535)
Exporting project packages from the Web UI failed for projects with templates that used the NOT condition for the TM filter. This issue is
now fixed. (CRQ-24513)
Projects created in Trados GroupShare with project templates that use the NOT condition for TM filter would result in broken word
counts. This issue is now fixed. (CRQ-21468)
Creating a project template would fail if your termbase friendly name contained the "&" symbol. This issue is now fixed. (CRQ-24057)
Opening the Lookup pane in the Online Editor would result in an error if the termbase you added to the project didn't match the project
language pairs. This issue is now fixed. (CRQ-23909, CRQ-12481)
When multiple files are selected in the project Planning section, the Set as active phase buttons are now correctly disabled. (CRQ-20883)
Projects from sub-organizations are now correctly displayed when selecting an organization in the Projects tab. (CRQ-19356)
Fixed an issue that caused project creation to randomly fail and display the following error: "An error occurred while executing the
command definition. See the inner exception for details". (CRQ-22620)
Creating projects using project templates with invalid characters in their name resulted in the following error: "Illegal characters in path".
To avoid this, it is no longer possible to create project templates that use invalid characters in their names. (CRQ-19159)
"Modified by" and "Created by" fields in MultiTerm Online are now correctly populated with the name of the user currently logged in,
instead of the Windows account that runs the Trados GroupShare services. (CRQ-16853)
Fixed an issue that allowed users without the appropriate permissions to delete termbases. (CRQ-14874)
Downloading files that contain accented characters from the Online Editor will no longer produce target files with incorrect names. (CRQ-
13587)
TM lookup now works correctly in the Online Editor after enabling HTTPS and disabling HTTP or when specifying custom ports during
installation. (CRQ-11469, CRQ-11453)
Termbase restrictions now work correctly in sub-organizations and permissions are now correctly inherited from the root organization.
(CRQ-8823)
You can now log in to the GroupShare Web UI as a user with a username that contains accented characters without getting the "Object
reference not set to an instance of an object" error. (CRQ-8575)
Fixed an issue that prevented users with accented user names from seeing server-based TMs in Trados Studio. (CRQ-8563)
When the Application server role and Web Server role/Multiterm Online roles are installed on different machines, you no longer get the
following error in the GroupShare Console: "An unknown error occurred. Please restart the application. Details: Could not find a
part of the path 'C:\Program Files (x86)\SDL\SDL Server\Web\configs.js". Instead, you will now be notified that you need to update
the configs.jg file by a warning message. (CRQ-9871)
Parent topic: Changes introduced in Trados GroupShare 2020 SR1 CU6
Formatting segments
When working with segments, you can perform multiple actions to make sure that the formatting in your target text is consistent with the one in the
source text.
These actions include:
Viewing white spaces in both the source and the target text
Viewing formatting tags in both the source and the target text
Copying formatting from the source text to the target text
Copying tag pairs
Changing the capitalization of a selected fragment
Clearing the formatting of a selected fragment or of the entire target text
Viewing white spaces and other non-printing characters
Viewing white spaces is particularly useful if you want to remove unnecessary non-printing characters from your text.
Viewing formatting tags
By viewing formatting tags, you can see information about how source segments are formatted. This is also useful if you want to copy tag
pairs from the source segment to the target segment.
Options for displaying tags
In Online Editor, you can choose between multiple ways of having tags displayed.
Copying formatting from the source text to the target text
If you prefer to format segments only after you have translated them, you can do so more quickly by copying formatting from the source text
directly to fragments of the target text.
Copying tag pairs
If you prefer to format target segments before you translate them, copying tag pairs from the source text to the target text helps you to be
more efficient.
Clearing segment formatting
You can remove the formatting from an entire target segment or only from a part of it if that target segment no longer needs to contain the
same formatting tags as its corresponding source segment.
Parent topic: Translating content
Improved defense against cross-site scripting
This CU improves the way GroupShare encodes output data on the Web UI. This ensures potential hackers or malware cannot inject HTML and
script characters that could make Trados GroupShare vulnerable to cross-site scripting. We have also updated Jquery to version 3.6. This version
prevents cross-site scripting better than previous ones. (CRQ-24131 and CRQ-26899).
Parent topic: Changes introduced in Trados GroupShare 2020 SR1 CU6
Online Editor editions
Online Editor is available in two editions, Basic and Advanced, which can be used concurrently starting from Trados GroupShare 2020 CU2. The
previous product version, Trados GroupShare 2020 CU1, offered Online Editor, as either Basic or Advanced. Find out the differences.

Online Editor options in the Trados GroupShare licenses


Online Editor can be accessed under the form of a Basic edition, of an Advanced edition, or a combination of both (mixed edition). The Basic
edition has some limitations, but both editions allow you to open a file for translation or review in Trados GroupShare. If you purchase a mixed
license, you can switch between the Basic or the Advanced mode when opening files.
Trados GroupShare offers you the possibility of purchasing licenses with the following Online Editor entitlements:
Advanced only
Basic only
Basic and Advanced (starting from Trados GroupShare 2020 CU2)
The Online Editor trial version uses the Advanced edition.

Online Editor features per edition


Online Editor Feature Basic Advanced
UpLIFT No Yes
AutoSuggest No Yes
Lookups No Yes
Split and Merge Segments No Yes
Edit Source No Yes
Verification No Yes
Find and Replace Yes Yes
Auto-propagation Yes Yes
Apply Formatting Yes Yes
Change Casing Yes Yes
Change Segment Status Yes Yes
Clear Formatting Yes Yes
Clear Target Segment Yes Yes
Commenting Yes Yes
Contextual Help Yes Yes
Copy Source to Target Yes Yes
Cut, Copy and Paste Yes Yes
Delete word backward (CTRL+Backspace) Yes Yes
Delete word forward (CTRL+DELETE) Yes Yes
Document Navigation Yes Yes
Filtering Yes Yes
Font Adaption Yes Yes

Layout (horizontal/vertical) Yes Yes


Overwrite mode Yes Yes
QuickInserts Yes Yes
Segment Locking Yes Yes
Segment Navigation Yes Yes
Tag Details Yes Yes
Online Editor Feature Basic Advanced
Track Changes Yes Yes
Undo, Redo Yes Yes
Whitespaces Yes Yes
Parent topic: Working with Online Editor
Step 1b: Creating projects based on previous projects
When you create projects from the Trados GroupShare web interface, you create a storage for all the files that need to be translated. At this stage,
you also decide which organization is in charge of your project. This feature is available only on the basis of special contractual agreement, at an
extra cost.

Before you begin


Make sure you:
Create a project template. You will need it during the project creation wizard.
If you want to upload a group of translatable files in one shot, you need to create a *zip archive that contains the files for translation.

About this task


You can either create projects starting off from previous projects or from scratch.

Procedure
1. Go to the Projects view and select New Project.
2. In the New Project window, select the General Settings tab:
a. Provide a name and a description for your project.
b. Select a location in the organization.
c. Select a project template from the list.
d. Browse for or drag and drop translatable files: the .ZIP archive (containing all the project files) or individual files.
Restriction: You can create projects either by using a .ZIP archive or by using individual files. You cannot use both methods at the
same time.
e. Optionally, set a due date and time for your project.
3. If you have custom fields in your account Resources that want to apply to the new project:
a. Click the Custom Fields tab in the New Project window.
b. Select a Custom Field from the drop-down list.
c. Fill in a Value for the custom property.
d. To add more custom fields, select the plus sign and repeat steps b and c.
4. In the New Project window, select the PerfectMatch Settings tab.
5. On the Add Matching Files page, map your source files to previous translations from which you want to extract previous signed-off
segments. You can upload previous translations:
From Previous Projects. Choose this if you have an existing Trados GroupShare project that contains similar files from which you can
Extract PerfectMatch translations. The matches are parsed in the order in which the reference projects are added.
PerfectMatch is correctly applied if the language pair of the current project is the same as or one of the available language pairs of the
reference project.
The first reference project you add receives a LOCK status automatically. If you do now want to prevent translators from editing the
TUs to which PerfectMatch is applied, clear the LOCK checkbox. You can add the same reference project twice, and enable
LOCK on one instance while disabling LOCK on the second instance.
From bilingual Files. Choose this if you have .SDLXLIFF documents available on your computer from which you can extract
PerfectMatch translations. Make sure the names of the .SDLXLIFF files match the name of the corresponding source file. For single-
file projects, Trados GroupShare automatically renames .SDLXLIFF files to use the same name as the source file.
6. Select Finish.
The new project is added to the Projects list and instantly visible to all the users with access to the project. Trados GroupShare also shows
these users an on-screen notification about the new project.

Required folder hierarchy and naming for .ZIP archives


When you create a project from a .ZIP file that contains multiple files, Trados GroupShare automatically identifies all the translatable files from the
root folder and from any subfolders available in the archive.
If your .ZIP archive also contains reference files or PerfectMatch files, make sure to use the structure and file naming described below. This
hierarchy enables Trados GroupShare to map your source files to the corresponding PerfectMatch files:
\SourceFiles - Optional folder containing the individual files or subfolders of files for translation. If you do not want to group all source files into
a single folder, you can also add the source files directly under the root archive folder. If you do add the source files as a single folder, we
recommended naming this folder "SourceFiles" to enable Trados GroupShare to map any corresponding PerfectMatch files easier.
If you name the SourceFiles folder differently, the structure of the PerfectMatch folder must also include your custom-name folder for every
language code subfolder in your PerfectMatch folder. See image 2b: ZIP structure when using a custom name for the Source Files folder.
...\1st Set Of Source Files

...\...\...\First File.docx
...\...\...\Second File.doc
...\2nd Set of Source Files
...\...\Third File.txt
...\...\Fourth File.doc

\PerfectMatchFiles - Optional folder containing already translated files in .SDLXLIFF format. The name of the folder must be
"PerfectMatchFiles". The PerfectMatch structure should match the folder and file name of the corresponding the source folder and source file.
...\de-de
...\...\1st Set Of Source Files

...\...\...\First File.docx.sdlxliff
...\...\...\Second File.doc.sdlxliff
...\...\2nd Set of Source Files

...\...\...\Third File.txt.sdlxliff
...\...\...\Fourth File.doc.sdlxliff
...\fr-fr
...\...\1st Set Of Source Files
...\...\...\First File.docx.sdlxliff
...\...\...\Second File.doc.sdlxliff
...\...\2nd Set of Source Files
...\...\...\Third File.txt.sdlxliff
...\...\...\Fourth File.doc.sdlxliff

\PerfectMatchFiles_1 - If you have more than one version of a PerfectMatch file that you want to apply to a source file, or if you want to add
more than one .SDLXLIFF file with the same name, create additional "PerfectMatchFiles" folders using the following format:
\PerfectMatchFiles_1, \PerfectMatchFiles_2, \PerfectMatchFiles_3,...
...\de-de
...\...\1st Set Of Source Files
...\...\...\First File.docx.sdlxliff
...\...\2nd Set of Source Files

...\...\...\Fourth File.doc.sdlxliff

\ReferenceFiles - Optional folder containing project files that should be used as a reference when translating or reviewing the source files. The
name of the folder must be "ReferenceFiles".
...\Diagram.vdsx
...\Image.png

Image 1: Required .ZIP structure when using the recommended name for the Source Files folder

Image 2: Required .ZIP structure when using a custom name for the Source Files folder
Parent topic: Workflow for shared projects started in Trados GroupShare
Related concepts
File assignment security
File assignment notifications
Supported database servers
Trados GroupShare supports the following SQL Server versions:
SQL Server 2019
SQL Server 2017
RWS recommends always using the latest supported SQL version. For any of the supported SQL versions, make sure you are on the latest
Service Pack release. Trados GroupShare may have performance issues if you use earlier versions of these SQL Server releases.
Make sure that the SQL Server that you use for running Trados GroupShare has the full text search engine installed. MultiTerm requires this for
fully supporting the Full Text Search option.
If you plan to use SQL Express, make sure that you use the Advanced Services edition.
For more information on the prerequisites required for installation, see the Installation Guide.
Parent topic: Installing Trados GroupShare
Language resource templates
Creating language resource templates
You can speed up the creation process of TMs that are similar or identical in the language resources they use. Language resource templates
enable you to work consistently across your TMs.
Editing language resource templates
You can modify the details of your language resource template any time. Any changes you make to your language resource template impact
the way your TM works.
Exporting language resources as template
When you export language resources from existing TMs, these are saved as a new language resource template that you can reuse.
Parent topic: TM language processing rules and recognized tokens
Activating Trados License Manager online
Find out how to activate and remove a network license on a server with Internet access.
Relevant product versions
Trados GroupShare 2020 is using the same version of Trados License Manager as SDL Studio GroupShare 2017, 2015 and 2014.
Activating a network license with Trados License Manager online
Using a key provided by the Licensing Team, you can activate the Trados License Manager to serve licenses of your purchased RWS
products to clients.
Removing a network license from Trados License Manager Manager online
You can remove the license that you added to a network server in several exceptional situations: to return unused licenses or to move a
license from one system to another.
Parent topic: Activating the Trados License Manager (administrators)
Finding and replacing text
Search for words, strings, or expressions in source or target segments and replace existing occurrences with up-to-date text.

Procedure
1. Open the appropriate file in Online Editor.
2. Do one of the following:
On the Home tab, in the Navigation group, select Find.
Select Show Find and Replace Panel .
The Navigation panel is displayed and the Find tab is selected by default.
3. In the Search box, enter the text you want to search for and select the appropriate search options.
The available options are:
In source – Search in the source segments of the file.
In target – Search in the target segments of the file.
Text in tags – Search for text within tags in the source segments, in the target segments, or in both. For this option to work, select
either one or both of the In source and In target options.
Match case – Search for text that has the exact letter case as the text you entered in the Search box.
Whole word – Search for an entire word.
Regular expression – Search for regular expressions.
The search results are displayed automatically.
4. To replace the text you entered with a different text, select the Replace tab.
Note: Replace or Replace All operations cannot be undone.
5. In the Replace with box, enter the text that will replace the existing text, and then do one of the following:
If you want to replace the text in one occurrence at a time, select the occurrence where you want to replace the text, and then select
Replace.
If you want to replace the text in all occurrences at the same time, select Replace All.
Tip: If you are in TQA mode and you want to replace all the occurrences of the same text, a new dialog box is displayed when you select
Replace All. Enter a comment and select the appropriate category, subcategory, and severity before selecting Replace All again.
When you view the translation quality assessments, the first occurrence of the replaced text has the severity that you selected earlier.
However, all other occurrences of the replaced text will have the Repeated severity.
Parent topic: Working with Online Editor
Dropped support for SQL Server 2014
This release introduces changes that are only supported by SQL Server 2017 or later.
If you are using SQL Server 2016, upgrade SQL Server before upgrading to Trados GroupShare 2020SR1.
Parent topic: Changes introduced in Trados GroupShare 2020 SR1
Database backup
Back up the master databases and the individual databases and tables regularly.
Use the backup mechanism of the host database system to back up data. For example, use the SQL Server backup applications to back up SQL
Server data.
Parent topic: Managing termbase data on the host
Step 4: Completing projects
When users complete all the assignments, you can mark the projects as Complete. At this stage, all the project files are usually in the Finalisation
phase.

Procedure
1. Go to the Projects view and select the checkboxes corresponding to the projects you want to complete.
2. Select Mark as Completed.

Results
Trados GroupShare shows the status of the project as Completed.
Parent topic: Workflow for shared projects started in Trados GroupShare
Related concepts
Standard roles and permissions
Dependencies between permissions
Translation statuses
File assignment security
When you work with file assignments from Trados Studio, Trados GroupShare makes each file in a Trados GroupShare project available only to
specific Trados Studio users.
Trados GroupShare checks the roles and permissions of the users who are available on the Trados GroupShare server where the project is
published.
The Trados GroupShare roles and permissions that you assign to Trados GroupShare users control which files these users have access to, and
what actions they can perform on the files that you assign to them.
To further enhance the security of the projects that you publish to Trados GroupShare servers, you should familiarize yourself with the External
Translator role and some of the relevant project permissions.

Roles that impact project security


The External Translator role in Trados GroupShare is mainly intended for projects where you assign translators contracted from outside your
translation organization to work on Trados GroupShare project files. By default, an External Translator can perform the same jobs as a Translator,
but does not have permission to view the other files in the project or the other users working on the project.
Note: Users without the View Other Users permission (by default, members of the External Translator role), see the other users added/removed
from the list of users assigned to work on the same files as Anonymous users.

Permissions that impact project security


Permission Description Assigned by default to
View All Files
Allows Trados Studio users with this permission to see Administrator
all the files in the project, even the files that have not
been assigned to them. Power User

Note: Additional permissions are required to perform Project Manager


actions on the files that the View All Files permission
makes available. Translator

View Other Users


Allows Trados Studio users with this permission to see Administrator
all the other users assigned to work on the same
project files. Power User
Project Manager
Translator

Check Out My Project Files


Allows Trados Studio users to check out only the files Administrator
assigned to them.
Power User
Note: This is the old Check Out Files permission in
earlier versions of Trados GroupShare. Project Manager
Translator
External Translator

Check Out Any Project Files


Allows Trados Studio users with this permission to Administrator
check out any of the files that are visible to them. This
permission allows checking out files regardless of their Power User
current phase and regardless of who is assigned to
work on the files. Project Manager
Permission Description Assigned by default to
Assign Files
Allows Trados Studio users with this permission to Administrator
assign files to other Trados Studio users who are
members of a Trados GroupShare role. Power User
Project Manager

Parent topic: File assignment


Related tasks
Step 2: Assigning files to users
Step 3: Updating file phase
Step 1a: Creating projects from scratch
Step 2: Planning work on assignments
Creating project templates
Step 1b: Creating projects based on previous projects
Timeout interval in Online Editor
Online Editor times out after 30 minutes of inactivity.
Parent topic: Working with Online Editor
Set up Language Weaver from the webUI
To set up Language Weaver from the webUI, first enable access to your Language Weaver account for the relevant Trados GroupShare users.
These users can then pre-translate new projects based on project templates that specify this MT provider.

About this task


Enable user access to Language Weaver

Procedure
1. Go to the Users tab.
2. Select a user to which you want to give access to your Language Weaver account.
3. On the Translation Providers page, enter the account credentials.
4. Click on the+ button to save the credentials into the database, then click on Finish.

Example
Create new projects based on templates
To create new projects that specify Language Weaver as MT provider:
1. In Trados Studio, create a template that specifies Language Weaver as machine translation provider.
2. Open Trados GroupShare to create a new template based on the Trados Studio one.
3. Click Resources tab > Project Templates > New Project Template.
4. Specify a name, description and a location for the template, then browse to the .sdltpl template file generated from Trados Studio.
5. On the Language Pairs page, check the source and target languages specified for the project template. Add additional project target
languages if required. Make sure not to remove the current language pairs as this will also remove the language providers specified in the
template.
6. On the Translation Providers page, check that Trados GroupShare identifies Language Weaver as a translation provider and select any
additional local translation memories required for the template.
7. Add any required termbases, then click Finish to close the New Project Template wizard.
8. Create a new project based on the new project template. As a user with access to the Language Weaver account, all your new projects
that use this template will be pre-translated with Language Weaver. If you also have TMs enabled as translation providers, they will take
priority over machine translation. This is to avoid using up your MT word allowance.
Parent topic: Set up translation providers
Adding permissions to user roles
Permissions are stored in a system-wide list. Roles are permission sets or bundles which can be expanded by adding new permissions to them.

Procedure
1. Go to the Users view and select the Permissions tab.
2. Expand the Edit Roles list and select the role you want to add permissions to.
3. In the [role name] dialog, select the checkboxes corresponding to the permissions you want to add.
Some permissions need other permissions to be useful. For example, to be useful, the Edit permission needs the corresponding View
permission. For more information, see Dependencies between permissions.
4. Select Finish.
Parent topic: User permissions
Related concepts
Dependencies between permissions
Standard roles and permissions
Translation statuses
Navigating between segments
You can navigate between segments either one by one (forwards or backwards) or by going directly to specific segments, according to their
number.

Procedure
1. Open the appropriate file in Online Editor.
2. On the Home tab, in the Navigation group, do one of the following:
To return to the previous segment, select Previous.
To move on to the next segment, select Next.
To navigate to a specific segment, enter the number of the segment in the Go To box, and then select Enter.
Tip: If you want to navigate to a specific segment while a segment filter is applied, you can only do so if the segment matches the criteria
specified through that filter. For example, if you apply a filter to see only segments with the Translated status and the segment to which you
want to navigate has a different status, the Invalid segment number message is displayed. In such a situation, you have to remove the
filter to navigate to that segment.
Parent topic: Navigating the Online Editor user interface
Activating a network license with Trados License Manager
offline
After you installed the Trados License Manager, generate an Installation ID (locking code) and use it to issue an activation certificate. You can
license the server only with this activation certificate.

About this task


The number of product features displayed after licensing the server is NOT the number of user seats available for your license. To check how
many users can access your network license at the same time, select a feature and check the Total column on the Total users row in the Feature
information section.
The product features installed for your network license are listed in the hostname tree under Subnet Servers.

Procedure
1. Use the Locking Utility to get the Installation ID (locking code) of your license server machine to generate the installation ID:
a. Launch the Locking Utility (wechoid).
b. Enable Host Name and Disk ID and disable all the other available criteria.
c. Make sure that the New Style option is selected and that the Selector field shows 0xC. This indicates that only the Host Name and
Disk ID criteria are enabled and that the corresponding code will generate a compatible license file.
d. Copy and save the locking code string available in the Code field.
With the Installation ID, you can then generate the activation certificate that enables you to activate the network license on your
server.
2. Generate the offline activation certificate:
a. Go to Products & Plans > Licenses in your account.
b. Locate your activation code and click Can´t activate online? - Get an offline Activation Certificate.
c. Copy and paste the Installation ID (generated above) into the Installation ID field and click Generate Offline Activation Certificate.
d. Save the generated activation certificate (by default named lservrc).
Tip: The activation certificate is issued based on the Installation ID. This ensures that the network license is used on the system to
which it is locked.
3. License the server:
a. Launch the SafeNet License Manager utility. On startup, the SafeNet License Manager utility automatically discovers all the servers
in the subnet where the Trados License Manager is installed. These are listed under the Subnet Servers tree.
Tip: If your license server is not listed, select Edit > Defined Server List and add the name of your server or IP address. To
automatically add your server to the Defined Servers list, select Edit > Preferences and enable Discover defined servers on startup.
b. Expand the Subnet Servers tree and select the hostname of the license server where you want to add the network license.
c. Right-click the hostname and select Add Feature > From a File > To Server and its File.
d. Browse for and select the generated activation certificate. If the license code corresponds to the locking code, the SafeNet License
Manager utility confirms that the network license is active and shows the number of product features included in your license.

Results
The license server is now good to go - clients can connect to the license server using the server's name. Make sure you have the licensing
computer turned on when users request network license seats.
Parent topic: Activating Trados License Manager offline
Deleting comments
You can delete comments after their corresponding issues have been solved or if the information in them is no longer relevant.

Procedure
1. Open the appropriate file in Online Editor.
2. On the right side of the screen, select Comments .
3. In the Comments panel, find the comment that you want to delete.
4. Place your cursor on the comment, go to the end of the comment row, hover over , and then select Delete Comment.
Parent topic: Working with comments
Defined field is not in project TM
Symptom
You can create a field in a translation memory (TM), but then find that the field is not copied from the main TMs to the project TM.
One symptom is that although you have created penalties based on field values, the penalties do not take effect.
Probable cause
The reason is that Trados GroupShare copies to the project TM only those fields that are common to all the constituent TMs.
System fields are common to all Trados GroupShare TMs.
Parent topic: Problems and solutions
Upgrading from SDL Studio GroupShare 2015 to Trados
GroupShare 2020 SR1
RWS recommends users who have the SDL Studio GroupShare 2015 RTM version to first update toTrados GroupShare 2020 CU1, and only
then to upgrade to Trados GroupShare 2020 SR1. Trados GroupShare remembers all your projects, resources and settings when you migrate
from any older version of Trados GroupShare to Trados GroupShare 2020 SR1.
Parent topic: Upgrading to Trados GroupShare 2020 SR1
Adapting the contrast of colored text
If the file you are working on contains text formatted with very light colors, you can change the way in which it is displayed without affecting its
formatting in the output.

Procedure
1. Open the appropriate file in Online Editor.
2. On the View tab, in the Fonts group, select Adapt Colors.
Parent topic: Navigating the Online Editor user interface
Changes introduced in Trados GroupShare 2020 SR1
This section contains a list of new features and functionality that were introduced with the Trados GroupShare 2020 SR1 release.
Real-time updates and notifications
Trados GroupShare 2020 SR1 introduces real-time updates to make collaborative project management easier than ever. As you change file
phases or assignments, check-out files or make any other changes, your updates are instantly visible to other users with project access.
Users also receive on-screen notifications about new projects so that no one misses important updates.
Post-translation Analysis report
The Reports view now includes an additional report: Post-translation analysis (PTA). Generate this report during any project phase to get a
detailed overview of your TM leverage and translators' effort on individual files.
Possibility to delete non-empty organizations
You can now delete also organizations and sub-organizations that contain users, translation memories, termbases, sub-organizations or
libraries. This means that you no longer have to first manually delete all the resources inside an organization before being able to delete the
organization itself.
Apply Perfect Match from bilingual files
Trados GroupShare 2020 SR1 brings more flexibility for working with Perfect Match. You can now extract matching translations also from
bilingual SDLXLIFF files available on your computer.
User profile pictures
Starting with this release, Trados GroupShare accounts support custom profile pictures. These offer an alternative to the default avatars that
show your initials on a colored background.
Dropped support for SQL Server 2014
This release introduces changes that are only supported by SQL Server 2017 or later.
Other enhancements
This topic lists the additional improvements introduced with Trados GroupShare 2020 SR1.
Parent topic: What's new in Trados GroupShare
Organizations and users
Every user has a home organization. To view or change a user's details, you need to have the appropriate permissions to the user's home
organization.

Organization hierarchy
Every organization except the top level organization is a subsidiary of another organization. This means that organizations form a hierarchy with just
one organization-the root organization-at the top.
If an organization is a subsidiary of another organization, this has the following effect:
Trados GroupShare displays the organizations in a hierarchy.
The roles assigned to the users in a root organization propagate to subsidiary organizations. In other words, the effective set of roles
assigned in an organization is the sum of the roles assigned in that organization and higher ones

Example: Users, roles and permissions for a single-level organization


This example shows how the users of a single-level organization can use a translation memory (TM) resource.

The software requires a user to have the Read permission for a TM. When Adam tries to read the TM, Trados GroupShare searches the roles
assigned in the Europe organization to find Adam's role. It then searches the roles table to find what permissions that role confers.

Example: Users, roles and permissions for a multi-level organization


This example shows how the users of a multi-level organization can use a translation memory (TM) resource.

Parent topic: Organizations and their components


Checking verification results
In the Verification panel there are two options. You can filter the verification results by Severity or by Message type.

About this task


This feature is available for Online Editor Advanced.

Procedure
1. Open the appropriate file in Online Editor.
2. One the right-hand side panel, select the Verification symbol.
3. Select the Severity text box and the tags of the severities that were found in the document are displayed along with the number of instances
that were found in the document. Choose the severity tags that you want to search for: Error, Warning, Note.
4. Select the Message type text box and the tags of the error types that were found in the document are displayed along with the number of
instances that were found in the document. Choose the verification messages that you want to search for: QA messages or tag messages.
QA messages in the Verification panel
This topic lists the verification messages triggered when QA differences are identified after the automatic comparison of source segments
and target segments.
Tag messages in the Verification panel
This topic lists the verification messages triggered when tag differences are identified after the automatic comparison of source segments and
target segments.
Parent topic: Verifying translated content
Real-time updates and notifications
Trados GroupShare 2020 SR1 introduces real-time updates to make collaborative project management easier than ever. As you change file
phases or assignments, check-out files or make any other changes, your updates are instantly visible to other users with project access. Users also
receive on-screen notifications about new projects so that no one misses important updates.
Live updating and notifications means that project members no longer have to manually refresh the page to make sure projects are synced.
For split-installation scenarios, the real-time notifications require an additional port to be opened in the firewall. For more information, see Ports
for split install in the Installation Guide.
Parent topic: Changes introduced in Trados GroupShare 2020 SR1
What is Trados GroupShare WebHooks Service
WebHooks provide a publish/subscribe model for wiring together Web APIs and services. You can subscribe to Trados GroupShare events and
get notified when the event happens through a callback.
When you subscribe to an event, you need to provide a callback URI where you want to be notified when the event occurs. When the event
occurs, an HTTP POST request is sent to your callback URI with information about what happened.

Trados GroupShare WebHooks Service


Trados GroupShare WebHooks Service is implemented as a standalone self-hosted Rest API application that can be run as a Windows Service
or in console mode (using --console switch). The default port that the Rest API self-hosted service listens to is 41239.
Parent topic: WebHooks Service
Downloading files in Online Editor
Once your work on the assigned files is finished, you can download the file in its native format directly from Online Editor.

Procedure
1. Open the file in Online Editor by one of the following methods:
Click the file-name link in the notification email to open your Trados GroupShare assigned documents in Online Editor.
Log in to Trados GroupShare, go to Dashboard, and, under Your Tasks, select near the assignment you want to work on.
Log in to Trados GroupShare, go to Projects, select the project where the assignment is stored, select the checkbox next to the file
you want to work on, and then select Open in Editor.
The file automatically opens in Online Editor and is ready for editing.
2. Edit the file in Online Editor.
3. Check in the file in Online Editor.
4. In the right-hand side corner of the toolbar, select Download and save the file in its native format.
Parent topic: Working with Online Editor
Detaching the side panel
Detaching the side panel in Online Editor means opening it in a different window. This can be particularly useful if you are working with two
monitors, because it makes the translation area larger and it separates the actual translation of content from other operations, such as working with
revisions, lookups, or comments.

Procedure
1. Open the appropriate file in Online Editor.
2. Select Detach Panel .
Parent topic: Navigating the Online Editor user interface
User permissions
User permissions are defined in a system-wide list that is not editable. Permissions are grouped under roles. By assigning roles to users, you can
easily manage the permissions users have to perform tasks in Trados GroupShare.
Adding permissions to user roles
Permissions are stored in a system-wide list. Roles are permission sets or bundles which can be expanded by adding new permissions to
them.
Removing permissions from user roles
Permissions are stored in a system-wide list. Roles are permission sets or bundles whose scope can be narrowed down by removing
permissions from them.
Assigning permissions to user groups
You group users by assigning them roles in the same organization. Working with specific user groups is useful when you want all its
members to be assigned the same role and be given access to the same resources.
Assigning user access to resources
Depending on their assigned roles in an organization, users can have permissions over organization resources. To have access to
organization resources, users must be assigned a role that includes access permission to resources. Several options are available.
Increasing user access to resources
Depending on their assigned role in an organization, users can have a range of user access permissions to some or all organization resources.
Several options are available.
Removing user access to resources
When you no longer want your users to have access to organization resources, you can remove their user access permissions. Several
options are available.
Restricting user access to resources
When you want your users to have fewer user access permissions
Dependencies between permissions
Some permissions need other permissions to be useful. For example, to edit any resource, in addition to the Edit permission, you need the
corresponding View permission.
Parent topic: Users
Related tasks
Creating users
Assigning roles to users
Deleting projects
You can delete your projects irrespective of their status, when no longer necessary.

Procedure
1. In the Projects view, select the checkboxes corresponding to the projects you want to delete.
2. Select Delete and select Yes in the confirmation message.
Parent topic: Project management
Editing language resource templates
You can modify the details of your language resource template any time. Any changes you make to your language resource template impact the
way your TM works.

Procedure
1. Go to the Resources view.
2. In the Language Resource Templates tab, select the checkbox corresponding to the template you want to edit.
3. Select Edit.
4. In the [language resource template name] dialog, make any necessary changes.
5. Select Finish.
Parent topic: Language resource templates
Ordinal followers
Ordinal followers refer to the various symbols used in numbers, figures or dates.
The most common ordinal followers are the full stop and the comma. Usually, the full stop and comma signs are used by segmentation rules to
parse the entire translation memory (TM) based. However, if the full stop and the comma signs are given ordinal follower status in certain
phrases, these contexts will be ignored by and will not interfere with the TM parsing mechanism.
For example, you have a date entry like 23.03.2000. You do not want the TM to interpret the full stop as a full stop, so you give it an ordinal
follower status in this context.
Defining ordinal followers
You can define a list of ordinal followers for each source language of your TMs.
Exporting ordinal followers
You can reuse ordinal followers across translation memories (TMs) by exporting and importing them in .txt format.
Importing ordinal followers
You can reuse ordinal followers across translation memories (TMs) by importing and exporting them in .txt format.
Parent topic: TM language processing rules and recognized tokens
You cannot specify a windows user in add user
Symptom
In User Management > Add User, a user - even one with all privileges such as an administrator - cannot use a Windows domain username
when filling in the user account details.
Probable cause
The Application Server service is running under a local Windows user account and so cannot access Windows domain features, which
include Windows domain user accounts.
Solution
You can specify a local Windows user account.
For a user to be able to use Windows domain user accounts, the Trados GroupShare Application service must run under a Windows
domain user account. The account for that service is specified when Trados GroupShare is installed. For more information, see .
Parent topic: Problems and solutions
Copying tag pairs
If you prefer to format target segments before you translate them, copying tag pairs from the source text to the target text helps you to be more
efficient.

Procedure
1. Open the appropriate file in Online Editor.
2. In a target segment of your choice, click the place where you want to copy a tag pair.
3. Select Ctrl+Comma, and then, in the list, select the tag pair that you want to add.

What to do next
Write the appropriate content inside the newly copied tag pair.
Parent topic: Formatting segments
Glossary
100% match
A match that has a score of 100%. A score of 100% is always an exact match. However, an exact match might not be a 100% match (if the
translation memory or translation unit is penalized, the score is reduced).

Abbreviation
In translation memories (TMs) for TM Server and Trados Studio, a word that is terminated by a period and is in the TM's list of abbreviations.
When a TM is presented with source text, the TM recognizes a period that is part of an abbreviation, and so does not use that period to segment
the text. Abbreviations are a language resource.

Activation certificate
A certificate created during offline activation.

Administrator
A pre-defined role in MultiTerm Administrator. Members of the Administrator server role have access to MultiTerm Administrator and
administrator rights on MultiTerm Server.

Alignment
The creation of translation units (TUs) by examining and segmenting the source and corresponding target texts of previously translated content. The
alignment process starts with completed translations. It divides the source and target texts into segments, attempting to determine which segments
belong together in order to build an aligned translation memory from the content. The resulting translation memory can be used for future
translations.

translation alignment

Authorized
If a user has sufficient access rights to perform an action on configuration settings or stored data (for example to update a TM), the user is said to
be authorized to perform the action.

Auto-localize
The process of applying automatic localization.

Automated translation
Translation without human interaction. Sometimes called machine translation.
Synonyms
machine translation
AT
MT

Automatic localization
The process by which the software can automatically change the format of numbers, dates and times to suit the target language. For example, when
translating English to French, a translation editor can replace the decimal point used in English in 3.141 with a comma as used in French, to
produce 3,141. Automatic localization is available if the translation memory (TM) supports it for the TM's placeables. TMS does not apply
automatic localization. In Trados Studio and TM Server, automatic localization settings are specified per project for each language pair.

Background tasks
Trados GroupShare completes it while you wait. However, some types of actions can require a long time, so does them in the background, as
background tasks.

Browser-based editor
Browser-based editor
An editor that runs within a web browser, and so does not require a lengthy local installation procedure on the local computer. Online Editor is a
browser-based translation editor, in contrast to the translation editor in Trados Studio, which is a desktop editor.

online editor

CAL
A client access license (CAL) is a license for one user (client) of a server based software. Usually a single network license has a number of CALs;
that number specifies the maximum number of concurrent users.

Client access license

Certificate
A set of letters or numbers generated by the Licenses section of My Account which is used to activate a product offline. You need the activation
code and installation ID to generate a certificate. A certificate is either an activation certificate or a deactivation certificate.

Character entity reference


In HTML, XML or SGML a symbolic name for characters. Character entity references start with an ampersand and end with a semi-colon. In
between the letters represent the character. For example a non-breaking space is represented by an ampersand followed by the letters nbsp,
followed by a semi-colon. See also numeric character reference.

character entity

Compound term
A term consisting of more than one word, for example "local area network".
Synonyms:
multi-word units
multiple word terms

Concordance match
The result of a concordance search that matches all words in the search phrase, but not necessarily in the same order as in the phrase. The
translator can pick a match from the list of matches. See also in-order concordance match.

Concordance search
A search through a translation memory (TM) for words or fragments of text within translation units. Contrast with the more common use of a TM,
which is to match a whole segment of text at a time. A concordance search is only performed when requested by a user.

Container
TM Server: A database that holds translation memories. Only used as part of the term TM container.

Content repository
A folder, file, database or other holder of content.

Context match
A match that takes into account the context within which the match occurs. Usually this means surrounding segments. A context match is even
more likely to be correct than a 100% match of a segment. There are different kinds of context match, depending on which aspects of context are
taken into account (for example, formatting).

Context view
A near-final form of preview of a translation.

Conversion program
Conversion program
A software program that converts content from its native format to an intermediate format more suitable for translation. Our translation programs
like Trados Studio, run a convertor on each translatable item to convert the contents from native format (for example Microsoft Word) to
*.sdlxliff format.

Synonyms: convertor

Custom field template


See field template.

Database server
A computer program that provides database services to other computer programs or computers. The term also refers to a computer dedicated to
running such a program. The database server is the server in a client/server installation of TM Server and stores all server-based translation
memories and termbases.

Deactivate
The opposite (antonym) of activate, activation.
Synonym: deactivation

Deactivation certificate
A certificate created during offline deactivation. See certificate.

Draft
The translation status appropriate for a translation that a translator has started but has not finished. Typically, if a segment has a fuzzy match in the
TM, the translation software inserts the TM translation into the target segment, and marks the segment as draft.

DTD
Document Type Definition. A text file that defines the structure, elements and conventions to which an SGML, XML or HTML document must
conform. The DTD file is separate from the document it defines. An example of a widely used DTD is the HTML 4.0 DTD, used to define HTML
4.0 documents.

Document Type Definition

Effective membership list


In Trados GroupShare, the sum of all membership lists that apply to an organization or library. The effective membership list is usually the sum of
the immediate membership list plus the membership lists from all containing organizations and libraries. However, at any level, role inheritance can
be blocked.

Encoding (character encoding)


A set of rules for representing characters in digital form. One common form of character encoding is Unicode.

Exact match
A match in all aspects of text: characters, punctuation and formatting. In an exact match, the text surrounding the source text might be different
from the text surrounding the entry in a translation memory (by contrast, a context match requires the same surrounding text.)

File
A synonym for a translatable file while it is in a translation editor.

document

File category
See item category.

File path
The name of the file plus the directory path to the file.

File-based TM
A translation memory (TM) that is stored in a file and can be accessed by any user that has access to the file. Contrast to server-based TM.

file-based translation memory

File type
WorldServer, , Trados Studio: A program that extracts translatable content from a particular file format, segments the extracted content, and uses
the segments to produce a translatable item in a form such as an *.sdlxliff file. The translatable item can be presented to a translation memory
and translated using a translation editor. Users of Trados GroupShare can configure file types and create new ones. Typically, the purpose of
configuring a file type is to allow or disallow translation of some content.

file filter

Finalize
The finalize task sequence takes a project to the finalized status. The task sequence updates the main translation memories and generates the target
translations.

Finalized
The last status for a project. When a project has a status of finalized, none of the items in that project can be updated.

Fragment alignment
This is a fine-grained alignment that takes place at a sub-segment level. Unlike the normal alignment that only takes place at a segment level, with
fragment alignment, translated text fragments are matched together with their source counterpart to better leverage the previously translated
content.

Fragment match
This is a fine-grained alignment that takes place at a sub-segment level. Unlike the normal alignment that only takes place at a segment level,
translated text fragments are matched together with their source counterpart to better leverage the previously translated content.

Fuzzy band
A range for a fuzzy match, for example, 75% to 84%. In TM Server, there is one set of fuzzy bands for all languages in a project.

Fuzzy index
An index that allows you to find misspelled or transposed terms during a fuzzy search or wildcard search.

Fuzzy match
A match that is less than 100%. A fuzzy match has a percentage, for example, it is a 75% match, or a 90% match. For a translator, translating a
segment that has a fuzzy match is typically easier than translating a segment that has no match, but is more difficult than translating an exact match.
A fuzzy match requires more effort and probably needs editing.
Synonyms:
fuzzy-match value
match value

Fuzzy match threshold


The lowest percentage of a match for the matching text to be used as a fuzzy match. If the match is less than this percentage (which is typically
about 75%), then there is no fuzzy match for the text.

Fuzzy match value


See fuzzy match.

Fuzzy search
A type of search by which the application can find terms that are similar or identical to the search text.

History fields
MultiTerm uses a set of four system fields that show the edit history for each term: Created on, Created by, Modified on and Modified by.
MultiTerm creates and maintains these fields automatically for each entry and term at their respective levels.

History fields are visible in the Full layout and when enabling the Show system fields option in the Default layout.

Inline tag
A markup tag that forms part of a segment. Contrast with structure tag. Common uses of inline tags are to format text, to describe special
characters, or to reference an image or other hyperlink. Formatting tags and hyperlinks come in tag pairs. Special character tags and reference tags
are usually standalone tags.

Installation ID
A unique code which is product and computer specific. This means that a different product on the same computer will produce a different
installation code, and vice versa. This code is used when generating activation or deactivation certificates using SafeNet License Manager or within
the Licenses section of My Account.

Item
Corresponds to one file, document or other text item that is being translated using desktop translation software, or that accompanies the
translatable content. See also, item category. The source of an item is a file, database record, or some other data form. A translatable item needs
to be converted into a format such as .sdlxliff before a translator can use a translation editor to translate the content.

Item category
An item is categorized to show how it is used in the translation process. One categorization of items is: Translatable (the item is to be translated),
Localizable (to be translated outside the application), Reference (for reference only), Instruction (contains instructions for the translator).

Language pair
A source language and a target language, for example English to French, or English (GB) to French (Swiss). A language pair has direction: English
to French is not the same as French to English.

Language resource
Language resources are a set of settings in a translation memory. Each language resource is a list of one of the following: abbreviations, ordinal
followers, segmentation rules, variables

Language variant
A specific form of a language used in a culture, for example German is a language (code de), and German as used in Austria is a language variant
(code de-AT).

sublanguage

Leverage level
The extent to which content can be translated against a TM. The higher the leverage level, the more the TM content is reusable. Leverage levels
are generally categorized as High: ICE, SPICE; Medium: exact, 100%; Low: interval fuzzy ranges.
Synonym: leverage

Library
In Trados GroupShare and its components: a container for resources. A library uses a membership list for specifying permissions. A library can
contain resources and other libraries. A library is contained in another library or in an organization.

resource library

License
A code used to validate whether a product is allowed to run on a computer.
For instructions on how to activate single-user and network licenses for RWS products, see the Licensing Help.

Licensing server
A computer on the LAN which processes product activation requests from client computers. The licensing server is activated using a licensing tool.
You can use Trados License Manager for SafeNet to activate the Licensing server. After activation, any other computer that requires licensing
(client) can connect to the server and request a license (when concurrent licensing is used).

Local translation memory


A translation memory (TM) that is stored on the translator's computer. Usually a local TM can only be used by one user at a time. Compare to
server-based translation memory.
Synonym: local TM

Locale
A geopolitical area. In a computer: the settings that define a language, country and other geopolitical variants. Also the two-or four-letter language
code used to identify a language or language and language variant. The definition of a culture includes the language variant and the default encoding
used to store content in this language (for example, UTF-8).

culture

Main translation memory


A translation memory that is stored on the application database server and is available for all projects. Contrast with project TM.

main TM

Markup
Content in a translatable item that should not be exposed to the translator for translation. This includes layout and formatting information, style
definitions, and font information. Markup is almost always coded in the form of markup tags. Embeddable markup is equivalent to an inline tag;
non-embeddable markup is equivalent to a structure tag.

Match
An equivalence between two segments of text, usually between a segment of presented text and a source segment in a translation memory. A
match has a match score, which is between the fuzzy match threshold and 100%.

Match (filters)
In relation to filters: an equivalence between an entry (for example, a term in a termbase or a translation unit in a translation memory) and a filter
rule. Unlike text matches, a filter match does not have a score.

Match band
Segments that are in the same match band have the same unit rates for the purposes of estimating translation time and costs. The match band of a
segment depends on the source and target language, and on the quality of match that is found (for example the percentage match in a fuzzy match).
Only segments that have a match in a translation memory are classified into match bands.
Match lookup
The process in which presented text is compared with translation units in a TM.

leveraging

Match score
A percentage value that describes the level of equivalence in a match.

Membership list
In Trados GroupShare and its components: a list of users and their roles in an organization or library. Membership lists specify user permissions for
resources. A membership list can only add permissions; it cannot remove any. Membership lists are valid for lower level (contained) organizations
and libraries unless role inheritance is blocked.

Merge
To join two adjacent segments into a single segment.

Network license
A network license can be used by anyone on the network, up to the limit specified in the license. Network licenses require a licensing server to be
running to count the concurrent usage of licenses.
Network licenses activated using Trados License Manager (SafeNet) are called commuter licenses. SafeNet is the licensing system used for RWS
products. You can install Trados License Manager on both server and client operating systems. Windows 10 or 8.1 are examples of client
operating systems.

Not translated
A translation status: no translation has been done on the segment. Typically this means that the segment has no translation in the TM, and the
translator has not yet produced any translation.

Number
If number recognition is enabled for a TM, the TM recognizes a number in the source text as a placeable. If a segment of presented text matches a
translation unit in the TM, except for the value of a number, the TM registers an exact match. For example, if the TM has 'Jane has 5 apples', then
it finds an exact match for the presented text 'Jane has 99 apples'. If the TM settings allow it, the translation editor might also auto-localize
numbers.

Numeric character reference


In HTML, a numeric representation for characters, given by a number surrounded by an ampersand and a semi-colon. For example an ampersand
followed by the characters #160 followed by a semi-colon represents a non-breaking space. See also, character entity reference.

Ordinal follower
A word that follows a period which itself follows a number, and signifies that the number is an ordinal (first, second, third...), rather than a cardinal
(one, two, three...). Its use can be seen by considering the date expressed in German as 4. Juni. If Juni were not in the list of ordinal followers, '4.'
would denote the end of a segment, and Juni would start another segment. Ordinal follower lists are a language resource.

Organization
In Trados GroupShare and its components, a container, analogous to a folder, for users, resources and libraries. Organizations can also contain
other organizations. All organizations except the top level one belong to another organization and ultimately the top level organization contains all
other organizations, users and resources.

Origin
The origin of a segment's translation.

Origin before adaptation


Origin before adaptation
The origin of a segment's translation before it was changed by the user. For example, when a segment originating from machine translation is then
post-edited, the origin before adaptation is machine translation.

Package
A collection of files packaged together and sent to a user or another system. The files in any one package belong to the same project. Examples of
packages are project package and return package.

Path name
The full path name is the name of the file plus the directory path to the file.

Penalize
To apply a penalty score. You can penalize translation memories and translation units.

Penalty
A percentage taken away from the score of a match between a translation unit and source text segments. Trados Studio can apply penalties for a
variety of conditions: for example a penalty for the translation unit or translation memory used for the match, for formatting differences, and so on.
Penalties are specified as project settings.

penalty score

Permission
A right that a user or program has to access an application program, data, files or other resource. Common permissions (access rights) are read,
write, delete. Which permissions are required for certain activities on a resource is determined by the software. In TM Server, a user's permissions
to a resource are granted by the user's role in a resource library, as specified in an applicable membership list.

access right

Placeholder tag
A markup tag that is inline but, unlike most inline tags, is not a formatting tag. Often a placeholder tag is standalone , for example the img tag.

Plug-in
Software that adds functionality, for example to an application. Users or third parties can create plug-ins for TM Server and for WorldServer by
using the SDK.

Preparation
A batch task sequence that TM Server runs when a translatable item is added to a project, to prepare it for a translator. At the end of preparation
the translatable item has been converted to an .sdlxliff file, analyzed and populated with the results of batch translation.

Preview
A representation of a file in translation that shows how the file will appear after translation. There can be different levels of preview, for example
Raw preview (showing the data), Draft preview (showing the result as rendered, but not as published), Standard preview (showing the result as it
will be generated).

Project
A project contains a collection of source language files, and associated files (resource files), which TM Server manages as a unit. All files in the
same project have the same source language, but can be translated to multiple languages. Unit costs for translation are defined per project, for
each target language. Projects have a life-cycle. They go through project stages in a workflow.

Project folder
The Windows folder that holds all the project details, assets and working files.

Project package
A collection of the files needed for a translation, including the translatable items, translation memories, termbases, and instructions, packaged
together in a form that can be sent to a user or another system as part of a translation project. (Usually this means they are put in a zip file.) All the
files in one project package belong to the same project. All our translation applications allow a project manager to export and import project
packages.

Project template
A complete set of project settings, which can be applied as the default settings when creating a project.

Quality model
A set of rules that categorizes translation errors to produce quantifiable measures based on the quality of a translation.

Placeable (recognized token)


A short piece of text, in one of a pre-defined set of formats, that a translation memory (TM) treats as a single word (token). For example, if dates
are enabled as a placeable in a TM, the TM recognizes Monday 1 January, 1900 as one word. Where a segment of presented text contains
placeables, a TM can find a match based on a pattern rather than exact wording. For example, if the TM has a match for He arrived on '1 January
1900', then the TM will provide a translation for the presented text 'He arrived on 2 February 2010'. For translation memories that use
*.sdlxliff format, (such as Trados Studio), the translation editor's QuickPlace shortcut provides suggested translations for placeables.
Translation memories in RWS TMS translate placeables automatically, without presenting them to the translation editor. To change how a
translation memory handles placeables: in TMS, change the configuration settings; in Project Server, TM Server or Trados Studio, change
translation memory settings and project settings.

placeable (obs.)

Regular expression
A way of describing a pattern of text, for example: "any five letter word that starts with a capital letter, and ends with a digit". Regular expressions
can specify sophisticated text patterns. For this reason they are used to specify segmentation rules. Regular expressions are widely used and are
well documented. See, for example, Regular expression.

Re-index TM
Build the fuzzy indexes in a translation memory (TM) from scratch. The system also scans existing translation units (TUs) for placeables. For
example, if you enable variable recognition and then re-index the TM, the TM recognizes variables in all TUs.

re-index translation memory

Repeated segment
The first occurrence of a segment that has repetitions.

Repetition
An occurrence of a segment that has been translated previously. Usually the term refers to repetitions within one translatable item, but sometimes it
can be used to refer to repetitions across a number of items.

Resource
In Trados GroupShare and its components, one of the following: translation memory, project, termbase, language resource template or field
template. A resource belongs to a resource library or to an organization.

Resource group
In Trados GroupShare and its components, a generic term that covers resource libraries and organizations.

Return package
A package that a member of a project sends to the project manager on completion of translation. See also project package.

Role
In Trados GroupShare and its components: a name for a collection of permissions. An organization or library has a list of users and roles that apply
to that organization or library. Some roles (for example, administrator) have a fixed set of permssions; other roles can be edited. Roles are defined
on a system-wide basis. Usually the administrator gives each role a name that describes a job, such as translator or TM manager. See also,
membership lists.

Scoping
The process of comparing content to be translated with past translations, to assess the remaining translation cost and effort.

My account
My account is our web portal where you can:
purchase and download our software
access licenses for certain products
purchase and access Support services
place and view orders
request and view sales quotations
purchase and view Certification and Training options

Trados License Manager


Licensing technology used to activate network licenses for our products. The Trados License Manager installer adds the following two utilities to
your computer:
Locking Utility (Wechoid) - generates locking codes for activating offline network license on the server.
Trados License Manager (WlmAdmin) - monitors all licensing activity and controls the distribution of license seats to clients.

.SDLXLIFF
*.Sdlxliff is an XLIFF format, compliant with XLIFF version 1.2.

RWS has added some standards compliant proprietary extensions.


When you add a translatable item to a project in Trados Studio, Trados Studio converts the item into an *.sdlxliff format file, and preforms all
subsequent translation work on the *.sdlxliff file. For example, when you use a Translation Editor, you edit an *.sdlxliff file, and you save
the result also as an *.sdlxliff file. The *.sdlxliff file has the same name as the source item but with an added file extension .sdlxliff.
At the end of the project, or when the user generates a final format for review, the translated text is extracted and converted to the destination file
format. Usually, the *.sdlxliff working file is kept intact.

Segment
Text that is a single translation unit for the purposes of finding a match in a translation memory. Usually a segment corresponds to a sentence.
Translation memories store translations by segment, and segments are also the unit for matching presented text with stored translations. In a
translation editor, each segment is displayed on a separate row.

Segmentation
The process of dividing text (usually source text) into segments.

Server-based TM
A translation memory (TM) that is stored on a TM server. A server-based TM can be used concurrently by more than one user. Compare to local
TM.
Synonym: server-based translation memory

Server-based translation memory


Server-based translation memories are located on Trados GroupShare servers on your network. Users access server-based translation memories
through a network or through the Internet. You can work online, interactively, with a server-based translation memory as easily as if it was local to
your computer. This means that however widely distributed project team members are, they can all work with the very latest versions of the same
translation memories.

Source
Descriptive of the original, untranslated item. For example: source content, source language, source segment, source text. Contrast with target. See
also, language pair.

Source file
A source file is a program file to be translated in Trados GroupShare. The file type depends on the parser. For example, the source files for
WIN32 are usually .EXE files or .DLL runtime libraries, whereas the source files for the text parser are (structured) text files. The source file may
also refer to a database or an SQL query when working with the database parser. The purpose of Trados GroupShare is to localize these source
files. The translated version of the source file is referred to as the target file.

Split
To divide, usually applied to a segment. Some applications allow you to split segments. This can be useful during the translation process to facilitate
the translation. WorldServer can also automatically split segments. It does this to look for higher quality matches, and so increase the leverage of
the translation memory. Contrast with merge.

Standalone tag
markup tag that can legitimately exist without another closing tag, for example a break tag in HTML. Contrast with tag pair.

Stem
The common root form of a number of words. For example go, going, gone all have the same stem, go. A translation memory can use stems to
find matching entries containing word variations. (Verb) To find the stem of a number of words. Stemming can generate a larger number of match
hits.

String
The smallest translatable unit of text within a source file is a string. All strings are display and can be edited in the string list window. Each string is
assigned to a resource. Strings in a source string list are also called source strings whereas strings in a translation list are referred to as
translation string.

Structure tag
A markup tag that exists between segments, and often defines a segment break. Examples are: line break tag, table tag. Contrast with inline tag.

System field
In the context of a translation memory, a field that the translation memory creates and maintains automatically. Contrast with custom field. In TMS,
the term attribute is used as a synonym for field.

Tag
A keyword assigned to a portion of text, used to specify text attributes (for example bold format), or text flow attributes (for example a page
break). Tags can be categorized into the following, overlapping, categories: Inline or structure; Standalone or one of a tag pair; Translatable or
non-translatable.
Synonym: markup tag

Tag pair
A matching pair of markup tags. Most markup tags come as a tag pair: one opening tag and its matching closing tag, for example <b> to represent
the start of bold text, and </b> to represent the end of bold text. Contrast with standalone tag.

Target
Descriptive of the translated or destination item, for example: target content, target language, target segment. Contrast with source. See also,
language pair.

Target file
A target file is the localized version of a source file. Generally, this is a copy of the source file in which all the resources and strings have been
translated to a target language.

Target language
Refers to the language a project is to be translated to. For example, if your project is to translate a manual from English to Spanish, Spanish is the
target language.

Target language term


A translation of the search term in the currently selected target language. You can apply special formatting and display properties to target language
terms and other target language information.

Target term
First equivalent of the search term in the currently selected target language.

Template
A template is a set of settings that you can use as a basis for settings in a resource such as a translation memory. The behavior of a template with
regard to the applied settings differs between RWS applications: In Trados Studio and , when you link a resource to a template, you cause the
resource to use the settings in the template. When you change the settings in the template, the corresponding settings in all linked resources are also
changed. However, if you change the settings by editing a resource, you break the link between the resource and the template. In TMS, when you
use a template for a resource, the system copies the settings from the template to the resource, but there is no ongoing link between the resource
and the template.

TM container
A named collection of TMs provided by one TM server. TM container and TM are analogous to folder and file. An installation can have more
than one TM container.

TM editor
The TM Server editor that you can use to edit a TM. It is similar to the Translation Editor.

TM sequence
A named collection of TMs that are searched in a specified order.

TM cascade
TM group

TM server
A program that provides access to TMs. One TM server can provide access to TMs that are on different database servers.

TMX
TMX (TM exchange) is an industry standard format for the exchange of translation memories. TM Server can import a translation memory that is
in TMX format, and can export its translation memories into TMX format files.

Translation Memory Exchange

Token
A token corresponds to a word, or short sequence of words and punctuation marks, in translatable text. When a translation memory (TM) is
applied to source text, the TM analyzes the source into tokens. This analysis is independent of the analysis into segments. You can configure a TM
to recognize text patterns as single tokens. For example, you can provide an expression that provides a definition of the patterns of text for dates.
Such text patterns are called placeables. You can provide rules for translating placeables.

Translation editor
An editor that enables translators to translate bilingual files, such as .sdlxliff files.

Translation memory
A translation memory (TM) is a file or database containing source language text segments and translated versions of the text segments. Each pair of
source and translated segments is called a translation unit (TU). In a TM, the source language segments are all in one language. A TM may contain
translations into many languages, but often has just one target language. A TM also maintains supplementary data for each TU, such as who
created the TU, and when. This data is held in fields. A user can also add user defined data to TUs. TMs allow translators to reuse translations,
thus reducing translation time and effort, and increasing consistency.

TM

Translation status (confirmation level)


The status of review and approval that you can assign to a segment or to a document to indicate the degree of confidence that you have in the
translation. The translation statuses of the segments in a document automatically update the translation statuses of the document. Not used in RWS
TMS.

TTX
A file type that was used for TRADOS TagEditor files, and also the file name extension for those files. Trados GroupShare 2021 and later support
TTX files and other legacy files via the Trados Compatibility and Migration Power Pack available from the RWS AppStore.
For information on installing apps, see Install and manage AppStore plug-ins.

TU
An entry in a translation memory (TM), consisting of a segment of source text, its translation text, and supplementary TM data such as translation
date. In TMX, translation unit is equivalent to the element TU. (Less common) text which is a single unit for the purposes of matching, equivalent to
segment.

translation unit
TM entry

Unicode
A standard for representing characters. It covers most of the world's written languages. A Unicode character is a character that has a Unicode
representation.

Unix filter
A matching pair of markup tags. Most markup tags come as a tag pair: one opening tag and its matching closing tag, for example <b> to represent
the start of bold text, and </b> to represent the end of bold text. Contrast with standalone tag. A program that processes an input data stream into
an output data stream in some well-defined way. Hence, a program that converts a file from one data format to another data format.

UTF-8
An encoding for Unicode characters in one to four bytes. The number of bytes depends on the Unicode character. All the ASCII character codes
are single byte UTF-8 codes.

Unicode Transformation Format - 8

Variable
A feature of translation memories (TMs) that are used in TM Server and Trados Studio. TMS does not use variables. However, the way that
RWS TMS treats acronyms is similar to the way that TM Server treats variables. A variable is a word or phrase defined in the variable list of a
TM. A TM considers a variable to be the same in all its languages. Where a translation unit includes a variable, the TM will substitute one variable
for another variable if that provides a match. For example, assume the following are true: - 'Mary Brown' and 'John Smith'are variables in a TM. -
The TM has a translation for 'The head manager is Mary Brown.' - The presented text is: 'The head manager is John Smith.' Then the TM uses the
translation for 'The head manager is Mary Brown.', replaces 'Mary Brown' with 'John Smith' in the translated text and registers an exact match.
Variable lists are a language resource.

(Wechoid) (SafeNet License Manager)


Licensing tool part of Trados License Manager. Use (Wechoid) to generate installation IDs for offline commuter licenses.

WlmAdmin (SafeNet License Manager)


SafeNet utility that controls the distribution of network license seats to clients. You can also use (WlmAdmin) to monitor all network licensing
activity for your RWS products.

Workflow
A model of the stages through which translatable items progress in the translation process.

XLIFF
XLIFF is an XML based file format, designed to be useful for translators.
Some of the features of an *.xliff file are:
It is a bilingual file: it holds the source and target language text.
It separates translatable and non-translatable content, for example it separates translatable text from formatting information.
It structures the translatable content into translatable segments, usually sentences.
It holds useful management information, such as the translation status of each segment.

XPath
A syntax for specifying locations in an XML document. It includes path expressions (analogous to file path expressions) and a number of built-in
functions. XPath is an important part of XSLT.
Working with reports
There are two levels of reporting in Trados GroupShare: project level reports and global reports.

Project level reports


Project level reports present a detailed account of your translated files inside a project. These reports are available only for projects created in
Trados GroupShare.
There are three available reports: Analyze Files report, Audit Trail report and Post Translation Analysis.

Global reports
Besides the project level reports, there is also a global reporting module that project managers can use to visualize and track the translation work.
Note: The reporting modules needs a separate license. Contact your sales representative for more information.
You can use the reporting module in Trados GroupShare to see the status of the work being performed, analyze progress and make planning
decisions.
There are currently three pre-defined reports in the reporting area:
Projects
Tasks
TM leverage
You filter reports to get a more granular view of the translation work. You can also export the reports.
Global reports
There is a set of three predefined reports available to view on the Reporting view of the web UI.
Project-level reports and background tasks
Trados GroupShare reports present a detailed account of your translated files. Trados GroupShare completes the actions which require a
long time in the background, as background tasks.
Termbases
Use MultiTerm Desktop to create server termbases and add them as resources in Trados GroupShare.
You can find more information about this in the MultiTerm Administrator section from MultiTerm 2022 SR1 Help.
The list of termbases that are assigned as resources in Trados GroupShare can be found in the Resources view, by going to the Termbases tab.
You can filter the list by organization.
Parent topic: Working with resources
Changes introduced in SDL Trados GroupShare 2020
This section provides an overview of the new features, enhancements and other changes introduced in the 2020 version of Trados GroupShare.
New solution for reporting and dashboard
We've replaced the reporting engine with one built on the Logi Analytics platform.
Mixed Online Editor licensing options
Online Editor can be accessed under the form of a Basic edition, of an Advanced edition, or a combination of both (a mixed edition).
Verify translations in Online Editor
You can now use the Online Editor in Trados GroupShare to perform QA checks as part of the translation and review process. This feature
is available with Online Editor - Advanced edition.
Parent topic: What's new in Trados GroupShare
Licensing videos
Check the RWS Licensing Youtube playlist for help with common licensing and activation issues.
Parent topic: Licensing
Tuning server-based TM performance
You can optimize the way your TM works in terms of speed and accuracy. Trados GroupShare performs the re-indexing and recomputation tasks
in the background, leaving you free to do other actions.

About this task


When you enable token recognition, the TM does not automatically scan its TUs, so it does not automatically recognize these tokens in existing
TUs. To force the TM to re-scan its TUs, re-index the TM.

Procedure
1. Go to the Resources view.
2. In the Translation Memories tab, select the checkbox for the TM whose performance you want to tune.
3. Select Edit.
4. In the [translation memory name] dialog, select Performance Tuning.
5. Make the necessary changes in terms of Performance, Fuzzy Index and Statistics, and consult whether the TUs are aligned.
Note: upLIFT alignment is the fragment alignment (also known as FGA) that automatically occurs for TMs which have 5,000 TUs or more.
The automatic alignment happens between 00:00 AM and 06:00 AM. You can check whether the TUs are aligned or not on the
Performance Tuning page of server-based TM s which meet the minimum 5,000 TU requirement.
6. Select Finish.
TM performance tuning
You can tune the performance of a translation memory (TM) in terms of: performance, fuzzy index and statistics.
Parent topic: Translation memories (TMs)
Editing project settings
You can access and manage the project settings if you are assigned the Edit Project permission.

Procedure
1. Go to the Projects view > All projects tab to view the list of all available projects and their details.
2. Select a project to view its details in the project tab.
3. Select Project Settings and go through the available pages.
4. On the General Settings page consult the information about: Description, Name, Location and the project creation method (From project,
From server template).
5. Select Next.
6. On the Language Pairs page check the available language pairs.
7. Select Next.
8. On the Translation Memories page, check the available TMs (and their details: associated language pairs and number of TUs).
9. Select Next.
10. On the Termbases page, check the available termbases, their associated language pairs and number of entries.
11. Select Next.
12. On the PerfectMatch page check the previously translated projects used to leverage the current project. This feature is useful if the current
project is very similar (or nearly identical) to other projects which have already been translated.
13. Select Next.
14. On the Custom Fields page:
Check the available custom fields and their values.
Delete the custom fields you no longer need.
Add one or more custom fields.
15. Select Finish.
Parent topic: Project settings
User roles
Every user who is part of an organization has a role. If users are part of several organizations, they may have different roles across organizations. In
Trados GroupShare you can use its standard, default roles or create new roles. Each role has an associated set of permissions.
Creating roles
Roles are the sets of permissions users have within an organization. When you create a role, you create a new set of permissions that you
can assign to your users.
Editing roles
When no longer up-to-date, a role's name or its associated permissions can be modified to reflect new requirements.
Deleting roles
When roles are no longer necessary, you can delete them from the server.
Assigning roles to users
To give your users permissions and access to your projects and resources, you must assign them roles. Roles are helpful because they are
like labels users carry with them. Therefore, it is easy to group, filter or quickly retrieve all your translators or reviewers, for example.
Removing roles from users
When you do not want users to fulfill a role, you can remove the user from that role.
Standard roles
Trados GroupShare is built with default users/role with predefined permissions for managing the most common actions.
Parent topic: Users
Related tasks
Creating users
Assigning roles to users
Other changes
Option to choose which notifications Trados GroupShare sends. System administrators can now configure the type of notifications sent by
the application in theTrados GroupShare configuration. (CRQ-29484)
Updated publisher text from SDL to SDL Limited (a part of the RWS Holding Plc. Group). (LTGS-10595)
Trados GroupShare now supports Service Provider-initiated SSO. (CRQ-31754)
Updated Microsoft .NET to version 6. With this change, dependencies like ASP.NET CORE have also been updated to a version
supported by .NET CORE 6.
Updated RabbitMQ Server to Version 3.11.3 (LTGS-10844)
To simplify REST API documentation, we've dropped the (static) Swagger UI web client (…/swagger-ui). You can now find the updated
Swagger UI documentation tool at …/documentation/api/index. (LTGS-10805)
Xceres has been migrated to java-natice XMP API. With this change, Xceres no longer generates an exception when configuring MultiTerm
Online. (LTGS-10976)
Updated the version of some Trados GroupShare and MultiTrem Online libraries to address recently identified vulnerabilities. (LTGS-
10950, LTGS-10948, LTGS-10655)
Parent topic: Changes introduced in Trados Groupshare 2020 SR1 CU8
REST API information
REST API information is hosted in Swagger. The information can be used interactively to learn more about the actions that can be performed on
projects, translation memories, termbases and any other resources.
Interactive REST API endpoints documentation: http://host/documentation/api/index
Parent topic: Welcome to the Trados GroupShare 2020 SR1 documentation
Parent topic: Installing Trados GroupShare
Added support for new files types
The CU7 release expands on the range of supported file types.
In addition to the current list of supported file types, this release brings support for:
YAML (*.yml)
Email (*.msg, *.eml, *.emlx, *.oft)
XML V2 (*.xml)
Billingual Adobe Framemaker (*.mif)
.NET Library (*.exe, *.dll)
Markdown (.md)
Parent topic: Changes introduced in Trados GroupShare 2020 SR1 CU7
Step 4: Completing assignments
When the assigned users receive notification of a pending assignment, they must check out the assigned file from the Trados GroupShare server.

Procedure
1. In Trados Studio, go to the Projects view, and double-click a project published on Trados GroupShare to open it.
Tip: Alternatively, click the link in the notification email to open your Trados GroupShare project to your assigned documents.
2. In the Files view, select the file you want to check out.
3. On the Home tab, select Check out.
Tip: When users check out their assigned files, Trados GroupShare shows this information in the Checked out to column in the Projects
view.
Important: You cannot check out from Trados Studio, files which are already checked out in Online Editor. You can open these files in
Trados Studio for consultation purposes only.
Do not make any local changes to the file while it is checked out in Online Editor. Wait until the file is checked in from Online Editor, and
only then check it out from Trados Studio.
4. On the Home tab, select one of the following: Open For Translation, Open For Review, Open For Sign-off, depending on your assigned
tasks and project phases.
5. Start working on the file.
Parent topic: Workflow for shared projects started in Trados Studio
Related concepts
Standard roles and permissions
Dependencies between permissions
File assignment notifications
Translation statuses
Copying source content to target segments
If a source segment contains long numbers or other characters which are easily mistyped, you can copy the entire content of a source segment into
the target segment and translate around those characters. Do the same if the segment translation is the same in both the source and in the target
language.

About this task


This feature is available for Online Editor Advanced.
You can copy a source segment or all the source content.

Procedure
1. Open the appropriate file in Online Editor.
2. Select the target segment to which you want to copy source content.
3. On the Home tab, in the Segments group, do one of the following:
To copy source content only to that particular target segment, select Copy Source to Target > Copy Source to Target.
Note: If the segment already contains some content, the source content overwrites the current content in the target segment. If the
segment has already been confirmed, the source content also overwrites the current content and the status of the segment is changed
to Draft.
To copy all the content in the source segments to all the target segments, select Copy Source to Target > Copy All Source to Target.
Note: When copying all the source content, the content is added only to empty segments that have the Draft or the Not Translated
status and that are not locked.
Source content copying for segments with revisions
Several changes are made to the information in target segments if you copy source content to target segments that already contain revisions
made with Track Changes.
Parent topic: Translating content
Adding comments
By adding comments, you can make suggestions to translators and reviewers and help improve the overall quality of the translation. You can add
comments only to target segments.

Procedure
1. Open the appropriate file in Online Editor.
2. On the right side of the screen, select Comments .
The Comments panel is displayed.
3. In the Comments panel, in the text box, enter your comment.
4. Do one of the following:
Scope Action
Add a comment to the current selection, to the current segment, or Select a fragment of text in the target segment. You cannot add
to the entire file. comments over locked segments. If a segment contains a
combination of locked and non-locked content, you can add
comments over the latter.
After you select a fragment of text, under Applies to select one of
the options: Current Selection, Current Segment, or File.

Add a comment to the current segment or to the entire file. Click anywhere inside a target segment that has text in it, and under
Applies to select either Current Segment or File.
Add a comment to the entire file. Click anywhere inside an empty target segment, and under Applies
to select File.
5. In the Severity list, select the severity level (or importance) of your comment: Information, Warning, Error.
6. Select Add.

Results
If you added a comment to a selection or to a segment, that selection or segment is highlighted. If you select a segment with comments, you can
see all the users who added comments for that segment.
Tip: When the file you are working on contains comments, a small dot is displayed on the Comments button.
Also, segment-level comments are marked with an icon next to the segment number. For example, in the following image, there is a segment-level
comment on segment 22:

Parent topic: Working with comments


Apply Perfect Match from bilingual files
Trados GroupShare 2020 SR1 brings more flexibility for working with Perfect Match. You can now extract matching translations also from
bilingual SDLXLIFF files available on your computer.
This adds to the existing option to extract translations from Trados GroupShare projects that you can specify as a reference. Uploading bilingual
files instead of reference projects gives you more control over which translation file is mapped to which source file.
Parent topic: Changes introduced in Trados GroupShare 2020 SR1
Viewing projects
You can consult the list of available projects at any time. The project list provides information about the project: name, publication date, delivery
date, client, status, language pairs and location within the Trados GroupShare organization hierarchy.

Procedure
1. Go to the Projects view and, in the All projects tab, view the list of all available projects and their details.
2. Select a project to view its details in the project tab.
Parent topic: Project management
Set up translation providers
During project creation, Trados GroupShare can pre-translate project files using the MT providers that you set up in the Trados GroupShare
webUI or in the Trados GroupShare Console

About this task


You can use the following translation providers for your Trados GroupShare projects:
Server-based Translation Memories
Language Weaver
SDL ETS Translation
To pre-translate projects using these providers, enable them from the Trados GroupShare console and use a relevant project template.
If you work with Language Weaver, you can also set up this provider easier from the Trados GroupShare webUI.
Set up Language Weaver from the webUI
To set up Language Weaver from the webUI, first enable access to your Language Weaver account for the relevant Trados GroupShare
users. These users can then pre-translate new projects based on project templates that specify this MT provider.
Set up translation providers from the Console
Enable server-based translation memories, SDL ETS Translation or Language Weaver from the Trados GroupShare Console to pre-
translate project files using these providers.
Parent topic: Project management
Task conrefs for SDL Online Editor
Procedure
1. Open the appropriate file in Online Editor.
2.
Renaming default phases
Change the names of the default phases used by your Trados GroupShare server. The custom phases that you set up for your Trados GroupShare
server will be available in Trados Studio when opening and working with a project based on that Trados GroupShare server.

About this task


Note that only future projects will make use of your custom phase names. Email notifications are also changed to reflect the custom names. When
opening a project from an Trados GroupShare server with custom phase names with SDL Trados Studio 2015 or older, the phases names will
revert to the default ones for compatibility.

Procedure
1. In the Trados GroupShare Console navigation tree, select SDL Trados GroupShare > Settings.
2. In the Settings pane, under Phases Naming, change the default phase names by filling in your custom names in the corresponding text boxes.
3. In the Actions pane, select Apply Changes to save the change. Changes are effective once you restart the services.
Parent topic: Trados GroupShare Console settings
Opening Trados GroupShare Console
To manage the Trados GroupShare settings, you must first open Trados GroupShare Console.

Procedure
1. On the server where Trados GroupShare is installed, select Start.
2. Launch Trados GroupShare Console from the computer Start menu.
If your current user account does not have access to the SDL System Database, you will be prompted to provide credentials for a user with
Read database permissions. If you cannot provide valid credentials, you will not be able to change any of the settings.
Parent topic: Trados GroupShare Console
Configuring a basic organization
As administrator, you can create a setup for organizations with various complexity degrees. Complex organizations (like the enterprise ones) have
multiple client organizations or sub-organizations. You can replicate the pattern of a basic organization for complex organizations.

Before you begin


Make sure you are either an administrator or member of a role that has Add User and View Infrastructure rights and all the additional permission
dependencies before creating the setup.

About this task


You can follow the steps in this procedure when configuring the root organization or its subsidiary organizations.

Procedure
1. Create users.
2. Edit user roles.
Tip: You might find it useful to create a role that has no permissions and use that role for suspended or unapproved users.
3. Assign permissions to users.
4. Configure server-based translation memories (TMs) or other resources.
Tip: The servers and containers that you add at Root organization level can be used when creating TMs for subsidiary organizations.
5. Add links to the resources your organization's users will have access to.
6. Create translation projects.
Parent topic: Organizations and their components
Acknowledgments
Trados GroupShare 2020 SR2 CU9 includes the following open-source, licensed or similar third-party software:
A2v10.Web.Runtime
Version: 10.0.7848
Vendor: Oleksandr Kukhtin
Copyright: Copyright © 2015-2022 Oleksandr Kukhtin
License type:
License details:
AlphaFS
Version: 2.2.6
Vendor: Peter Palotas, Jeffrey Jangli, Alexandr Normuradov
Copyright: Copyright (c) 2008-2018 Peter Palotas, Jeffrey Jangli, Alexandr Normuradov
License type: MIT
License details: https://opensource.org/license/mit/
Antlr
Version: 3.5.0.2
Vendor: Sam Harwell, Terence Parr
Copyright: Copyright (c) 2011 The ANTLR Project
License type: BSD4CLAUSE
License details:
App.Metrics.Abstractions
Version: 4.1.0
Vendor: Allan Hardy
Copyright: Allan Hardy 2016
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
App.Metrics.Concurrency
Version: 2.0.1
Vendor: Allan Hardy
Copyright: Allan Hardy 2016
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
App.Metrics.Core
Version: 4.1.0
Vendor: Allan Hardy
Copyright: Allan Hardy 2016
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
App.Metrics.Formatters.Ascii
Version: 4.1.0
Vendor: Allan Hardy
Copyright: Allan Hardy 2016
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
App.Metrics.Formatters.Graphite
Version: 4.1.0
Vendor: Allan Hardy
Copyright: Allan Hardy 2016
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
App.Metrics.Reporting.Graphite
Version: 4.1.0
Vendor: Allan Hardy
Copyright: Allan Hardy 2016
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
Aspose.Cells
Version: 22.9.0
Vendor: Aspose
Copyright: © Aspose Pty Ltd 2001-2021. All Rights Reserved.
License type: Commercial
License details: https://about.aspose.com/legal/eula
Aspose.Diagram
Version: 21.11.0
Vendor: Aspose
Copyright: © Aspose Pty Ltd 2001-2021. All Rights Reserved.
License type: Commercial
License details: https://about.aspose.com/legal/eula
Aspose.Email
Version: 21.8.1
Vendor: Aspose
Copyright: © Aspose Pty Ltd 2001-2021. All Rights Reserved.
License type: Commercial
License details: https://about.aspose.com/legal/eula
Aspose.PDF
Version: 23.2.0
Vendor: Aspose
Copyright: © Aspose Pty Ltd 2001-2021. All Rights Reserved.
License type: Commercial
License details: https://about.aspose.com/legal/eula
Aspose.PSD
Version: 22.7.0
Vendor: Aspose
Copyright: © Aspose Pty Ltd 2001-2021. All Rights Reserved.
License type: Commercial
License details: https://about.aspose.com/legal/eula
Aspose.Slides.NET
Version: 21.9.0
Vendor: Aspose
Copyright: © Aspose Pty Ltd 2001-2021. All Rights Reserved.
License type: Commercial
License details: https://about.aspose.com/legal/eula
Aspose.Words
Version: 22.2.0
Vendor: Aspose
Copyright: © Aspose Pty Ltd 2001-2021. All Rights Reserved.
License type: Commercial
License details: https://about.aspose.com/legal/eula
Autofac
Version: 4.8.1
Vendor: Autofac
Copyright: Copyright © 2015 Autofac Contributors
License type: MIT
License details: https://opensource.org/license/mit/
AutoFixture
Version: 4.18.0
Vendor: Ploeh
Copyright: Copyright © Ploeh 2011
License type: MIT
License details: https://opensource.org/license/mit/
AutoFixture.AutoNSubstitute
Version: 4.18.0
Vendor: Ploeh
Copyright: Copyright © Ploeh 2011
License type: MIT
License details: https://opensource.org/license/mit/
AutoMapper
Version: 7.0.1
Vendor: Jimmy Bogard
Copyright: Copyright (c) 2010 Jimmy Bogard
License type: MIT
License details: https://opensource.org/license/mit/
AXP.Web.Optimization
Version: 1.0.0
Vendor: AntoXa.PRO
Copyright:
License type: UNKNOWN
License details:
Azure.Core
Version: 1.6.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Azure.Core
Version: 1.25.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Azure.Core
Version: 1.24.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Azure.Identity
Version: 1.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Azure.Identity
Version: 1.7.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Azure.Identity
Version: 1.6.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
BouncyCastle.NetCore
Version: 1.9.0
Vendor: Chris Huang
Copyright:
License type:
License details:
Castle.Core
Version: 4.4.1
Vendor: http://www.castleproject.org/
Copyright: Copyright (c) 2004-2019 Castle Project
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
Castle.Core
Version: 5.0.0
Vendor: http://www.castleproject.org/
Copyright: Copyright (c) 2004-2019 Castle Project
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
CommandLineParser
Version: 1.9.71
Vendor:
Copyright:
License type:
License details:
Common.Logging
Version: 3.0.0
Vendor: https://net-commons.github.io/common-logging/
Copyright: Copyright 2006-2011 the Common Infrastructure Libraries Team
License type: Apache 2.0
License details: https://www.apache.org/licenses/LICENSE-2.0
Common.Logging.Core
Version: 3.0.0
Vendor: https://net-commons.github.io/common-logging/
Copyright: Copyright 2006-2011 the Common Infrastructure Libraries Team
License type: Apache 2.0
License details: https://www.apache.org/licenses/LICENSE-2.0
CompareNETObjects
Version: 4.76.0
Vendor: Kellerman Software
Copyright: Copyright © 2022 Kellerman Software
License type: MSPL
License details: https://opensource.org/license/ms-pl-html/
CompareNETObjects
Version: 4.63.0
Vendor: Kellerman Software
Copyright: Copyright © 2019 Kellerman Software
License type: MSPL
License details: https://opensource.org/license/ms-pl-html/
Confluent.Kafka
Version: 1.8.2
Vendor: Confluent
Copyright: Copyright 2016-2020 Confluent Inc., Andreas Heider
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
Confluent.Kafka
Version: 2.0.2
Vendor: Confluent
Copyright: Copyright 2016-2020 Confluent Inc., Andreas Heider
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
Confluent.Kafka
Version: 1.9.2
Vendor: Confluent
Copyright: Copyright 2016-2020 Confluent Inc., Andreas Heider
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
coverlet.collector
Version: 3.1.2
Vendor: tonerdo
Copyright: Copyright (c) 2018 Toni Solarin-Sodara
License type: MIT
License details: https://opensource.org/license/mit/
coverlet.collector
Version: 3.2.0
Vendor: tonerdo
Copyright: Copyright (c) 2018 Toni Solarin-Sodara
License type: MIT
License details: https://opensource.org/license/mit/
devprime.cli
Version: 6.0.0
Vendor: Devprime
Copyright:
License type:
License details:
devprime.cli
Version: 5.2.1
Vendor: Devprime
Copyright:
License type:
License details:
Diga.WebView2.Wrapper
Version: 9.0.1
Vendor: Dipl.-Ing.(FH) Guido Agnesmeyer
Copyright: Copyright (c) 2021 Dipl.-Ing.(FH) Guido Agnesmeyer
License type: MIT
License details: https://opensource.org/license/mit/
DnsClient
Version: 1.7.0
Vendor: Michael Conrad
Copyright: Copyright (c) 2021 Michael Conrad
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
DocumentFormat.OpenXml
Version: 2.15.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
DocumentFormat.OpenXml
Version: 2.9.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
DotNetOpenAuth.Core
Version: 4.3.4.13329
Vendor: Andrew Arnott
Copyright: Copyright © 2012 Outercurve Foundation
License type: MSPL
License details: https://opensource.org/license/ms-pl-html/
DotNetOpenAuth.OAuth.Common
Version: 4.3.4.13329
Vendor: Andrew Arnott
Copyright: Copyright © 2012 Outercurve Foundation
License type: MSPL
License details: https://opensource.org/license/ms-pl-html/
DotNetOpenAuth.OAuth2.AuthorizationServer
Version: 4.3.4.13329
Vendor: Andrew Arnott
Copyright: Copyright © 2012 Outercurve Foundation
License type: MSPL
License details: https://opensource.org/license/ms-pl-html/
DotNetOpenAuth.OAuth2.Client
Version: 4.3.4.13329
Vendor: Andrew Arnott
Copyright: Copyright © 2012 Outercurve Foundation
License type: MSPL
License details: https://opensource.org/license/ms-pl-html/
DotNetOpenAuth.OAuth2.ClientAuthorization
Version: 4.3.4.13329
Vendor: Andrew Arnott
Copyright: Copyright © 2012 Outercurve Foundation
License type: MSPL
License details: https://opensource.org/license/ms-pl-html/
DotNetOpenAuth.OAuth2.Core
Version: 4.3.4.13329
Vendor: Andrew Arnott
Copyright: Copyright © 2012 Outercurve Foundation
License type: MSPL
License details: https://opensource.org/license/ms-pl-html/
DotNetOpenAuth.OAuth2.ResourceServer
Version: 4.3.4.13329
Vendor: Andrew Arnott
Copyright: Copyright © 2012 Outercurve Foundation
License type: MSPL
License details: https://opensource.org/license/ms-pl-html/
Elmah.MVC.ODataLogs.dll
Version: 1.0.0
Vendor: akomarov
Copyright:
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
EnterpriseLibrary.TransientFaultHandling
Version: 6.0.1304
Vendor: Microsoft
Copyright: © 2013 Microsoft Corporation
License type: MSPL
License details: https://opensource.org/license/ms-pl-html/
EnterpriseLibrary.TransientFaultHandling.Data
Version: 6.0.1304.1
Vendor: Microsoft
Copyright: © 2013 Microsoft Corporation
License type: MSPL
License details: https://opensource.org/license/ms-pl-html/
EntityFramework
Version: 6.4.4
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
EntityFramework
Version: 6.1.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
EntityFrameworkCoreMock.NSubstitute
Version: 1.0.0.26
Vendor: huysentruitw
Copyright: Copyright 2017-20139 Wouter Huysentruit, Paul Michaels
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.83
EntityFrameworkCoreMock.NSubstitute
Version: 2.4.0
Vendor: huysentruitw
Copyright: Copyright 2017-2021 Cup of Tea
License type: MIT
License details: https://opensource.org/license/mit/
Evolve.Tool
Version: 2.3.0
Vendor: Philippe Lécaillon
Copyright: Copyright © P.Lécaillon 2019
License type: MIT
License details: https://opensource.org/license/mit/
Flee
Version: 1.2.2
Vendor: Muhammet Parlak
Copyright: Copyright 2017
License type:
License details:
FluentValidation
Version: 11.2.2
Vendor: Jeremy Skinner
Copyright: Copyright (c) Jeremy Skinner, .NET Foundation, and contributors 2008-2022
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
FluentValidation
Version: 8.5.0
Vendor: Jeremy Skinner
Copyright: Copyright (c) Jeremy Skinner, .NET Foundation, and contributors 2008-2022
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
Hopex.Yandex
Version: 23.0.1
Vendor: Schizo
Copyright: Hopex Development, 2023
License type: MIT
License details: https://opensource.org/license/mit/
HtmlAgilityPack
Version: 1.11.16
Vendor: ZZZ Projects
Copyright: Copyright © ZZZ Projects Inc.
License type: MIT
License details: https://opensource.org/license/mit/
Humanizer.Core
Version: 2.2.0
Vendor: Humanizer, .NET Foundation
Copyright: Copyright 2012-2016
License type: MIT
License details: https://opensource.org/license/mit/
ICSharpCode.Decompiler
Version: 7.1.0.6543
Vendor: ICSharpCode
Copyright: Copyright 2011-2021 AlphaSierraPapa
License type: MIT
License details: https://opensource.org/license/mit/
icu.net
Version: 2.5.4
Vendor: SIL International
Copyright: Copyright © 2007-2019 SIL International
License type: MIT
License details: https://opensource.org/license/mit/
icu.net
Version: 2.9.0
Vendor: SIL International
Copyright: Copyright © 2007-2023 SIL International
License type: MIT
License details: https://opensource.org/license/mit/
Icu4c.Win.Full.Lib
Version: 59.1.15
Vendor: SIL International
Copyright: Copyright (c) 2016-2017 SIL International
License type: ICU
License details: https://spdx.org/licenses/ICU.html
IIS.Microsoft.Web.Administration
Version: 8.5.9600.17042
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation. All rights reserved.
License type:
License details:
Infragistics
Version: 22.2.0
Vendor:
Copyright: © Infragistics, Inc. 2003-2019
License type: Commercial
License details:
J2N
Version: 2.0.0
Vendor: Shad Storhaug
Copyright: Copyright © 2019 - 2022 J2N
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
JsonDiffPatch.Net
Version: 2.3.0
Vendor: William Bishop
Copyright: Copyright © William Bishop 2017
License type: MIT
License details: https://opensource.org/license/mit/
librdkafka.redist
Version: 1.8.2-RC5
Vendor: math, edenhill, confluent
Copyright: Copyright 2012-2017
License type: MIT
License details: https://opensource.org/license/mit/
librdkafka.redist
Version: 1.8.2
Vendor: math, edenhill, confluent
Copyright: Copyright 2012-2017
License type: MIT
License details: https://opensource.org/license/mit/
log4net
Version: 2.0.14
Vendor: The Apache Software Foundation
Copyright: Copyright 2004-2017 The Apache Software Foundation
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
Lucene.Net
Version: 4.8.0-beta00016
Vendor: ApacheLuceneNet
Copyright: Copyright © 2006 - 2022 The Apache Software Foundation
License type: MIT
License details: https://opensource.org/license/mit/
Lucene.Net.Analysis.Common
Version: 4.8.0-beta00016
Vendor: ApacheLuceneNet
Copyright: Copyright © 2006 - 2022 The Apache Software Foundation
License type: MIT
License details: https://opensource.org/license/mit/
Lucene.Net.Queries
Version: 4.8.0-beta00016
Vendor: ApacheLuceneNet
Copyright: Copyright © 2006 - 2022 The Apache Software Foundation
License type: MIT
License details: https://opensource.org/license/mit/
Lucene.Net.QueryParser
Version: 4.8.0-beta00016
Vendor: ApacheLuceneNet
Copyright: Copyright © 2006 - 2022 The Apache Software Foundation
License type: MIT
License details: https://opensource.org/license/mit/
Lucene.Net.Sandbox
Version: 4.8.0-beta00016
Vendor: ApacheLuceneNet
Copyright: Copyright © 2006 - 2022 The Apache Software Foundation
License type: MIT
License details: https://opensource.org/license/mit/
MangoSeed
Version: 1.0.0
Vendor: Giovanni Galbo
Copyright: Copyright (c) 2021 Giovanni Galbo
License type: MIT
License details: https://opensource.org/license/mit/
Markdig.Signed
Version: 0.30.4
Vendor: Alexandre Mutel
Copyright: Alexandre Mutel
License type: BSD2
License details: https://opensource.org/license/bsd-2-clause/
MessagePack
Version: 2.2.113
Vendor: Yoshifumi Kawai
Copyright: © Yoshifumi Kawai and contributors. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
MessagePack.Annotations
Version: 2.2.113
Vendor: Yoshifumi Kawai
Copyright: © Yoshifumi Kawai and contributors. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
MessagePackAnalyzer
Version: 2.1.152
Vendor: Yoshifumi Kawai
Copyright: © Yoshifumi Kawai and contributors. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.AspNet.WebApi.Client
Version: 5.2.9
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.AspNet.WebApi.Client
Version: 5.2.7
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.AspNet.WebApi.Core
Version: 5.2.7
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.AspNet.WebApi.Owin
Version: 5.2.3
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.AspNet.WebApi.OwinSelfHost
Version: 5.2.3
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.AspNet.WebApi.OwinSelfHost
Version: 5.2.7
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.AspNet.WebApi.SelfHost
Version: 5.2.9
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.AspNet.WebApi.Tracing
Version: 5.2.3
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.AspNet.WebHooks.Common
Version: 1.2.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.AspNet.WebHooks.Custom
Version: 1.2.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.AspNet.WebHooks.Custom.Api
Version: 1.2.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.AspNet.WebHooks.Custom.SqlStorage
Version: 1.2.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.AspNet.WebPages
Version: 3.2.9
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.AspNetCore.Authentication.Abstractions
Version: 2.2.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
Microsoft.AspNetCore.Authentication.Core
Version: 2.2.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
Microsoft.AspNetCore.Authorization
Version: 2.2.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
Microsoft.AspNetCore.Authorization
Version: 7.0.5
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.AspNetCore.Authorization.Policy
Version: 2.2.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
Microsoft.AspNetCore.Connections.Abstractions
Version: 7.0.5
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.AspNetCore.Connections.Abstractions
Version: 6.0.15
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.AspNetCore.Cors
Version: 2.2.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
Microsoft.AspNetCore.Cryptography.Internal
Version: 1.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.AspNetCore.DataProtection
Version: 1.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.AspNetCore.DataProtection.Abstractions
Version: 1.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.AspNetCore.Hosting.Abstractions
Version: 2.2.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
Microsoft.AspNetCore.Hosting.Abstractions
Version: 1.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.AspNetCore.Hosting.Server.Abstractions
Version: 2.2.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
Microsoft.AspNetCore.Hosting.Server.Abstractions
Version: 1.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.AspNetCore.Http
Version: 2.2.2
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
Microsoft.AspNetCore.Http
Version: 2.2.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
Microsoft.AspNetCore.Http.Abstractions
Version: 2.2.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
Microsoft.AspNetCore.Http.Abstractions
Version: 1.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.AspNetCore.Http.Connections
Version: 1.1.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
Microsoft.AspNetCore.Http.Connections.Common
Version: 7.0.5
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.AspNetCore.Http.Extensions
Version: 2.2.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
Microsoft.AspNetCore.Http.Features
Version: 5.0.17
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
Microsoft.AspNetCore.Http.Features
Version: 1.0.2
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.AspNetCore.JsonPatch
Version: 5.0.17
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
Microsoft.AspNetCore.JsonPatch
Version: 6.0.15
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.AspNetCore.JsonPatch
Version: 6.0.9
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.AspNetCore.Metadata
Version: 7.0.5
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.AspNetCore.Mvc.Abstractions
Version: 2.2.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
Microsoft.AspNetCore.Mvc.Core
Version: 2.2.5
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
Microsoft.AspNetCore.Mvc.NewtonsoftJson
Version: 5.0.17
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
Microsoft.AspNetCore.Mvc.NewtonsoftJson
Version: 6.0.15
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.AspNetCore.Mvc.NewtonsoftJson
Version: 6.0.5
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.AspNetCore.Mvc.NewtonsoftJson
Version: 6.0.4
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.AspNetCore.Mvc.NewtonsoftJson
Version: 6.0.9
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.AspNetCore.Mvc.Testing
Version: 6.0.7
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.AspNetCore.Mvc.Testing
Version: 6.0.6
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.AspNetCore.OData
Version: 8.0.9
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.AspNetCore.OData
Version: 8.0.11
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.AspNetCore.OData
Version: 8.0.10
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.AspNetCore.Razor.Language
Version: 6.0.16
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.AspNetCore.Razor.Language
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.AspNetCore.ResponseCaching.Abstractions
Version: 2.2.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
Microsoft.AspNetCore.Routing
Version: 2.2.2
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.0
Microsoft.AspNetCore.Routing
Version: 2.2.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.1
Microsoft.AspNetCore.Routing.Abstractions
Version: 2.2.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.2
Microsoft.AspNetCore.SignalR
Version: 1.1.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.3
Microsoft.AspNetCore.SignalR.Common
Version: 7.0.5
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.AspNetCore.SignalR.Common
Version: 6.0.15
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.AspNetCore.SignalR.Core
Version: 1.1.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.4
Microsoft.AspNetCore.SignalR.Protocols.Json
Version: 7.0.5
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.AspNetCore.SignalR.Protocols.NewtonsoftJson
Version: 6.0.9
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.AspNetCore.TestHost
Version: 6.0.7
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.AspNetCore.TestHost
Version: 6.0.9
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.AspNetCore.WebSockets
Version: 2.2.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.5
Microsoft.AspNetCore.WebUtilities
Version: 2.2.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.6
Microsoft.Bcl
Version: 1.1.10
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.Bcl.AsyncInterfaces
Version: 5.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Bcl.Build
Version: 1.0.14
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.Build
Version: 17.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Build.Framework
Version: 17.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Build.Locator
Version: 1.4.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.CodeAnalysis.Analyzers
Version: 3.3.2
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.7
Microsoft.CodeAnalysis.Analyzers
Version: 3.3.4
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.CodeAnalysis.AnalyzerUtilities
Version: 3.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.8
Microsoft.CodeAnalysis.Common
Version: 4.3.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.CodeAnalysis.Common
Version: 4.5.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.CodeAnalysis.Common
Version: 4.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.CodeAnalysis.Common
Version: 2.10.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.CodeAnalysis.CSharp
Version: 4.3.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.CodeAnalysis.CSharp
Version: 4.5.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.CodeAnalysis.CSharp
Version: 4.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.CodeAnalysis.CSharp
Version: 2.10.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.CodeAnalysis.CSharp.Features
Version: 4.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.CodeAnalysis.CSharp.Scripting
Version: 4.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.CodeAnalysis.CSharp.Scripting
Version: 2.10.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.CodeAnalysis.CSharp.Workspaces
Version: 4.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.CodeAnalysis.Features
Version: 4.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.CodeAnalysis.NetAnalyzers
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.CodeAnalysis.Razor
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.CodeAnalysis.Scripting.Common
Version: 4.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.CodeAnalysis.Scripting.Common
Version: 2.10.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.CodeAnalysis.VisualBasic
Version: 4.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.CodeAnalysis.VisualBasic
Version: 2.10.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.CodeAnalysis.VisualBasic.Features
Version: 4.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.CodeAnalysis.VisualBasic.Workspaces
Version: 4.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.CodeAnalysis.Workspaces.Common
Version: 4.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.CodeAnalysis.Workspaces.MSBuild
Version: 4.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.CodeCoverage
Version: 17.6.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.CodeCoverage
Version: 17.5.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.CodeDom.Providers.DotNetCompilerPlatform
Version: 1.0.3
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.CSharp
Version: 4.5.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.CSharp
Version: 4.7.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.CSharp
Version: 4.4.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Data.Edm
Version: 5.8.4
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Data.Edm
Version: 5.8.5
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT0
License details: https://github.com/aws/mit-0
Microsoft.Data.OData
Version: 5.8.4
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Data.OData
Version: 5.8.5
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT0
License details: https://github.com/aws/mit-0
Microsoft.Data.SqlClient
Version: 4.1.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Data.SqlClient
Version: 2.1.4
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Data.SqlClient
Version: 5.1.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Data.SqlClient
Version: 5.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Data.SqlClient
Version: 5.0.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Data.SqlClient.SNI
Version: 5.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.Data.SqlClient.SNI.runtime
Version: 4.0.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.Data.SqlClient.SNI.runtime
Version: 2.1.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.Data.SqlClient.SNI.runtime
Version: 5.1.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.Data.SqlClient.SNI.runtime
Version: 5.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.Data.Sqlite.Core
Version: 6.0.15
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Diagnostics.Tracing.EventSource.Redist
Version: 1.1.28
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.DiaSymReader
Version: 1.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.DiaSymReader.Native
Version: 1.7.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.DotNet.PlatformAbstractions
Version: 2.1.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.DotNet.PlatformAbstractions
Version: 2.0.4
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.DotNet.Scaffolding.Shared
Version: 6.0.6
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.9
Microsoft.DotNet.UpgradeAssistant.Extensions.Default.Analyzers
Version: 0.4.346202
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.EntityFrameworkCore
Version: 2.1.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.10
Microsoft.EntityFrameworkCore
Version: 6.0.6
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.EntityFrameworkCore
Version: 6.0.15
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.EntityFrameworkCore
Version: 6.0.4
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.EntityFrameworkCore
Version: 6.0.9
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.EntityFrameworkCore.Abstractions
Version: 2.1.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.11
Microsoft.EntityFrameworkCore.Abstractions
Version: 6.0.6
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.EntityFrameworkCore.Abstractions
Version: 6.0.15
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.EntityFrameworkCore.Abstractions
Version: 6.0.4
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.EntityFrameworkCore.Analyzers
Version: 6.0.6
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.EntityFrameworkCore.Analyzers
Version: 6.0.15
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.EntityFrameworkCore.InMemory
Version: 6.0.11
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.EntityFrameworkCore.Relational
Version: 2.1.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.12
Microsoft.EntityFrameworkCore.Relational
Version: 6.0.6
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.EntityFrameworkCore.Relational
Version: 6.0.15
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.EntityFrameworkCore.Relational
Version: 6.0.4
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.EntityFrameworkCore.Sqlite
Version: 6.0.15
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.EntityFrameworkCore.Sqlite.Core
Version: 6.0.15
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.EntityFrameworkCore.SqlServer
Version: 2.1.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.13
Microsoft.EntityFrameworkCore.SqlServer
Version: 6.0.6
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.EntityFrameworkCore.SqlServer
Version: 6.0.4
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.EntityFrameworkCore.SqlServer
Version: 6.0.9
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.ApiDescription.Server
Version: 3.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.14
Microsoft.Extensions.ApiDescription.Server
Version: 6.0.5
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Caching.Abstractions
Version: 5.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Caching.Abstractions
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Caching.Memory
Version: 5.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Caching.Memory
Version: 6.0.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Configuration
Version: 5.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Configuration
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Configuration
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Configuration
Version: 1.1.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.Extensions.Configuration.Abstractions
Version: 2.0.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.15
Microsoft.Extensions.Configuration.Abstractions
Version: 5.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Configuration.Abstractions
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Configuration.Abstractions
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Configuration.Binder
Version: 5.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Configuration.Binder
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Configuration.Binder
Version: 7.0.4
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Configuration.CommandLine
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Configuration.CommandLine
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Configuration.EnvironmentVariables
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Configuration.EnvironmentVariables
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Configuration.EnvironmentVariables
Version: 6.0.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Configuration.FileExtensions
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Configuration.FileExtensions
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Configuration.Json
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Configuration.Json
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Configuration.UserSecrets
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Configuration.UserSecrets
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Configuration.UserSecrets
Version: 6.0.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.DependencyInjection
Version: 5.0.2
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.DependencyInjection
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.DependencyInjection
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.DependencyInjection
Version: 6.0.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.DependencyInjection
Version: 1.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.Extensions.DependencyInjection.Abstractions
Version: 5.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.DependencyInjection.Abstractions
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.DependencyInjection.Abstractions
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.DependencyInjection.Abstractions
Version: 1.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.Extensions.DependencyModel
Version: 2.1.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.DependencyModel
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.DependencyModel
Version: 2.0.4
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Diagnostics.HealthChecks
Version: 6.0.6
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Diagnostics.HealthChecks
Version: 6.0.2
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Diagnostics.HealthChecks.Abstractions
Version: 6.0.6
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Diagnostics.HealthChecks.Abstractions
Version: 6.0.2
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Diagnostics.HealthChecks.Abstractions
Version: 6.0.5
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Features
Version: 7.0.5
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Features
Version: 6.0.15
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.FileProviders.Abstractions
Version: 2.0.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.16
Microsoft.Extensions.FileProviders.Abstractions
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.FileProviders.Abstractions
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.FileProviders.Physical
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.FileProviders.Physical
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.FileSystemGlobbing
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.FileSystemGlobbing
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Hosting
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Hosting
Version: 6.0.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Hosting.Abstractions
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Hosting.Abstractions
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Hosting.WindowsServices
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Hosting.WindowsServices
Version: 6.0.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Hosting.WindowsServices
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Http
Version: 3.1.8
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.17
Microsoft.Extensions.Http
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Http
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Logging
Version: 3.1.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.18
Microsoft.Extensions.Logging
Version: 5.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Logging
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Logging
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Logging.Abstractions
Version: 5.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Logging.Abstractions
Version: 6.0.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Logging.Abstractions
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Logging.Abstractions
Version: 6.0.3
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Logging.Abstractions
Version: 1.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.Extensions.Logging.Configuration
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Logging.Configuration
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Logging.Console
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Logging.Console
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Logging.Debug
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Logging.Debug
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Logging.EventLog
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Logging.EventLog
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Logging.EventSource
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Logging.EventSource
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.ObjectPool
Version: 2.2.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.19
Microsoft.Extensions.ObjectPool
Version: 7.0.5
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.ObjectPool
Version: 6.0.18
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Options
Version: 5.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Options
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Options
Version: 7.0.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Options
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Options
Version: 1.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.Extensions.Options.ConfigurationExtensions
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Options.ConfigurationExtensions
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.PlatformAbstractions
Version: 1.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.Extensions.Primitives
Version: 2.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.20
Microsoft.Extensions.Primitives
Version: 5.0.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Primitives
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Extensions.Primitives
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.FeatureManagement.AspNetCore
Version: 2.5.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.ICU.ICU4C.Runtime
Version: 68.2.0.9
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: ICU
License details: https://spdx.org/licenses/ICU.html
Microsoft.ICU.ICU4C.Runtime.linux-arm64
Version: 68.2.0.9
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: ICU
License details: https://spdx.org/licenses/ICU.html
Microsoft.ICU.ICU4C.Runtime.linux-x64
Version: 68.2.0.9
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: ICU
License details: https://spdx.org/licenses/ICU.html
Microsoft.ICU.ICU4C.Runtime.win-arm64
Version: 68.2.0.9
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: ICU
License details: https://spdx.org/licenses/ICU.html
Microsoft.ICU.ICU4C.Runtime.win-x64
Version: 68.2.0.9
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: ICU
License details: https://spdx.org/licenses/ICU.html
Microsoft.ICU.ICU4C.Runtime.win-x86
Version: 68.2.0.9
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: ICU
License details: https://spdx.org/licenses/ICU.html
Microsoft.Identity.Client
Version: 4.22.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Identity.Client
Version: 4.21.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Identity.Client
Version: 4.47.2
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Identity.Client
Version: 4.45.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Identity.Client.Extensions.Msal
Version: 2.16.5
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Identity.Client.Extensions.Msal
Version: 2.19.3
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.IdentityModel.Abstractions
Version: 6.30.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.IdentityModel.Abstractions
Version: 6.28.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.IdentityModel.Abstractions
Version: 6.23.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.IdentityModel.JsonWebTokens
Version: 6.30.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.IdentityModel.JsonWebTokens
Version: 6.8.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.IdentityModel.JsonWebTokens
Version: 6.24.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.IdentityModel.JsonWebTokens
Version: 6.21.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.IdentityModel.JsonWebTokens
Version: 6.23.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.IdentityModel.Logging
Version: 6.30.1
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.IdentityModel.Logging
Version: 6.8.0
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.IdentityModel.Logging
Version: 6.24.0
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.IdentityModel.Logging
Version: 6.21.0
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.IdentityModel.Logging
Version: 6.23.1
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.IdentityModel.Protocols
Version: 6.8.0
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.IdentityModel.Protocols
Version: 6.24.0
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.IdentityModel.Protocols
Version: 6.21.0
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.IdentityModel.Protocols.OpenIdConnect
Version: 6.8.0
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.IdentityModel.Protocols.OpenIdConnect
Version: 6.24.0
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.IdentityModel.Protocols.OpenIdConnect
Version: 6.21.0
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.IdentityModel.Tokens
Version: 6.30.1
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.IdentityModel.Tokens
Version: 6.8.0
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.IdentityModel.Tokens
Version: 6.24.0
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.IdentityModel.Tokens
Version: 6.21.0
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.IdentityModel.Tokens
Version: 6.23.1
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.IdentityModel.Tokens
Version: 6.27.0
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Net.Compilers
Version: 2.10.0
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Net.Http
Version: 2.2.29
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.Net.Http.Headers
Version: 2.2.8
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.21
Microsoft.Net.Http.Headers
Version: 2.2.0
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.22
Microsoft.NET.StringTools
Version: 17.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.NET.Test.Sdk
Version: 17.5.0
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.NET.Test.Sdk
Version: 17.2.0
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.NET.Test.Sdk
Version: 17.4.1
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.NET.Test.Sdk
Version: 17.4.0
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.NET.Test.Sdk
Version: 17.3.2
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.NET.Test.Sdk
Version: 16.4.0
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.NET.Test.Sdk
Version: 17.1.0
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.NETCore.Platforms
Version: 3.1.0
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.NETCore.Platforms
Version: 7.0.2
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.NETCore.Platforms
Version: 1.1.1
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.NETCore.Platforms
Version: 1.1.0
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.NETCore.Targets
Version: 1.1.3
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.NETCore.Targets
Version: 1.1.0
Vendor: Microsoft
Copyright: Copyright (c) Microsoft Corporation
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.OData.Core
Version: 7.9.4
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT0
License details: https://github.com/aws/mit-0
Microsoft.OData.Core
Version: 7.10.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT0
License details: https://github.com/aws/mit-0
Microsoft.OData.Edm
Version: 7.9.4
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT0
License details: https://github.com/aws/mit-0
Microsoft.OData.ModelBuilder
Version: 1.0.8
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.OpenApi
Version: 1.2.3
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Owin
Version: 4.2.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.23
Microsoft.Owin
Version: 2.0.2
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.Owin.Host.HttpListener
Version: 2.0.2
Vendor: Microsoft
Copyright: Copyright (c) .NET Foundation and Contributors
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.Owin.Hosting
Version: 2.0.2
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.QualityTools.Testing.Fakes
Version: 16.11.230815
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.Reactive.Testing
Version: 4.4.1
Vendor: rxteam, dotnetfoundation
Copyright: Copyright (c) .NET Foundation and Contributors.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Reactive.Testing
Version: 5.0.0
Vendor: rxteam, dotnetfoundation
Copyright: Copyright (c) .NET Foundation and Contributors.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Spatial
Version: 7.9.4
Vendor: Microsoft
Copyright: Copyright (c) 2018 Microsoft. All rights reserved.
License type: MIT0
License details: https://github.com/aws/mit-0
Microsoft.SqlServer.DacFx
Version: 150.5282.3
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSRTW
License details:
Microsoft.SqlServer.DacFx.x64
Version: 150.5282.3
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSRTW
License details:
Microsoft.SqlServer.DacFx.x86
Version: 150.4200.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSRTW
License details:
Microsoft.SqlServer.Server
Version: 1.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.SqlServer.SqlManagementObjects
Version: 161.47027.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MICROSOFTSQL
License details:
Microsoft.TestPlatform.AdapterUtilities
Version: 17.4.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.TestPlatform.ObjectModel
Version: 17.5.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.TestPlatform.TestHost
Version: 17.5.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.TestPlatform.TestHost
Version: 17.4.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.Tpl.Dataflow
Version: 4.5.24
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.VisualStudio.Azure.Containers.Tools.Targets
Version: 1.9.10
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.VisualStudio.Azure.Containers.Tools.Targets
Version: 1.15.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSPRSDK
License details:
Microsoft.VisualStudio.Azure.Containers.Tools.Targets
Version: 1.14.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSPRSDK
License details:
Microsoft.VisualStudio.Azure.Containers.Tools.Targets
Version: 1.17.2
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSPRSDK
License details:
Microsoft.VisualStudio.Azure.Containers.Tools.Targets
Version: 1.18.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSPRSDK
License details:
Microsoft.VisualStudio.Azure.Containers.Tools.Targets
Version: 1.17.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSPRSDK
License details:
Microsoft.VisualStudio.Azure.Containers.Tools.Targets
Version: 1.15.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSPRSDK
License details:
Microsoft.VisualStudio.Debugger.Contracts
Version: 17.2.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSVS2017
License details:
Microsoft.VisualStudio.Threading.Analyzers
Version: 17.5.22
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.VisualStudio.Web.CodeGeneration
Version: 6.0.6
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.24
Microsoft.VisualStudio.Web.CodeGeneration.Core
Version: 6.0.6
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.25
Microsoft.VisualStudio.Web.CodeGeneration.Design
Version: 6.0.6
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.26
Microsoft.VisualStudio.Web.CodeGeneration.EntityFrameworkCore
Version: 6.0.6
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.27
Microsoft.VisualStudio.Web.CodeGeneration.Templating
Version: 6.0.6
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.28
Microsoft.VisualStudio.Web.CodeGeneration.Utils
Version: 6.0.6
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.29
Microsoft.VisualStudio.Web.CodeGenerators.Mvc
Version: 6.0.6
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.30
Microsoft.Web.Administration
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type:
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.Web.Infrastructure
Version: 1.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.Web.WebView2
Version: 1.0.864.35
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: BSD4CLAUSE
License details:
Microsoft.Win32.Primitives
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Microsoft.Win32.Registry
Version: 4.7.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Win32.Registry
Version: 5.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Win32.SystemEvents
Version: 4.7.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Win32.SystemEvents
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Microsoft.Win32.SystemEvents
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
MongoDB.Bson
Version: 2.13.2
Vendor: MongoDB
Copyright: Copyright © 2019–present MongoDB Inc.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.31
MongoDB.Bson
Version: 2.19.1
Vendor: MongoDB
Copyright: Copyright © 2019–present MongoDB Inc.
License type:
License details:
MongoDB.Driver
Version: 2.13.2
Vendor: MongoDB
Copyright: Copyright © 2019–present MongoDB Inc.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.32
MongoDB.Driver
Version: 2.19.1
Vendor: MongoDB
Copyright: Copyright © 2019–present MongoDB Inc.
License type:
License details:
MongoDB.Driver.Core
Version: 2.13.2
Vendor: MongoDB
Copyright: Copyright © 2019–present MongoDB Inc.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.33
MongoDB.Libmongocrypt
Version: 1.2.2
Vendor: MongoDB
Copyright: Copyright © 2019–present MongoDB Inc.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.34
MSTest.TestAdapter
Version: 3.0.3
Vendor: Microsoft
Copyright: Copyright (c) 2020 Microsoft Corporation
License type: MIT
License details: https://opensource.org/license/mit/
MSTest.TestAdapter
Version: 3.0.2
Vendor: Microsoft
Copyright: Copyright (c) 2020 Microsoft Corporation
License type: MIT
License details: https://opensource.org/license/mit/
MSTest.TestAdapter
Version: 2.2.10
Vendor: Microsoft
Copyright: Copyright (c) 2020 Microsoft Corporation
License type: MIT
License details: https://opensource.org/license/mit/
MSTest.TestAdapter.symbols
Version: 3.0.3
Vendor: Microsoft
Copyright: Copyright (c) 2020 Microsoft Corporation
License type: MIT
License details: https://opensource.org/license/mit/
MSTest.TestFramework
Version: 3.0.3
Vendor: Microsoft
Copyright: Copyright (c) 2020 Microsoft Corporation
License type: MIT
License details: https://opensource.org/license/mit/
MSTest.TestFramework
Version: 3.0.2
Vendor: Microsoft
Copyright: Copyright (c) 2020 Microsoft Corporation
License type: MIT
License details: https://opensource.org/license/mit/
MSTest.TestFramework
Version: 2.2.10
Vendor: Microsoft
Copyright: Copyright (c) 2020 Microsoft Corporation
License type: MIT
License details: https://opensource.org/license/mit/
MSTest.TestFramework.symbols
Version: 3.0.3
Vendor: Microsoft
Copyright: Copyright (c) 2020 Microsoft Corporation
License type: MIT
License details: https://opensource.org/license/mit/
murmurhash-signed
Version: 1.0.2
Vendor: Darren Kopp
Copyright: Copyright 2013 Darren Kopp
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.35
murmurhash-signed
Version: 1.0.3
Vendor: Darren Kopp
Copyright: Copyright 2013 Darren Kopp
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.36
NETStandard.Library
Version: 2.0.3
Vendor: .NET Foundation and Contributors
Copyright: .NET Foundation and Contributors
License type: MIT
License details: https://opensource.org/license/mit/
Newtonsoft.Json
Version: 13.0.2
Vendor: James Newton-King
Copyright: Copyright © James Newton-King 2008
License type: MIT
License details: https://opensource.org/license/mit/
Newtonsoft.Json
Version: 13.0.1
Vendor: James Newton-King
Copyright: Copyright © James Newton-King 2008
License type: MIT
License details: https://opensource.org/license/mit/
Newtonsoft.Json.Bson
Version: 1.0.2
Vendor: James Newton-King
Copyright: Copyright © James Newton-King 2017
License type: MIT
License details: https://opensource.org/license/mit/
Nexlib.Net
Version: 7.22.9.1
Vendor: Gennaro Cannolicchio
Copyright: Gennaro Cannolicchio
License type: MIT
License details: https://opensource.org/license/mit/
Ninject
Version: 3.3.4
Vendor: Ninject Project Contributors
Copyright: 2007-2010 Enkari, Ltd. 2010-2017 Ninject Project Contributors.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.37
Ninject.MockingKernel.NSubstitute
Version: 3.3.0
Vendor: Ninject Project Contributors
Copyright: Copyright (c) 2011 Andre Loker IT Services. 2012-2017 Ninject Project Contributors.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.38
NLog
Version: 4.7.15
Vendor: Jarek Kowalski, Kim Christensen, Julian Verdurmen
Copyright: Copyright (c) 2004-2020 NLog Project - https://nlog-project.org/
License type: BSD4CLAUSE
License details: https://spdx.org/licenses/BSD-4-Clause.html
NLog
Version: 4.6.7
Vendor: Jarek Kowalski, Kim Christensen, Julian Verdurmen
Copyright: Copyright (c) 2004-2020 NLog Project - https://nlog-project.org/
License type: BSD4CLAUSE
License details: https://spdx.org/licenses/BSD-4-Clause.html
NLog
Version: 5.0.1
Vendor: Jarek Kowalski, Kim Christensen, Julian Verdurmen
Copyright: Copyright (c) 2004-2020 NLog Project - https://nlog-project.org/
License type: BSD3
License details: https://opensource.org/license/bsd-3-clause/
NLog
Version: 5.1.3
Vendor: Jarek Kowalski, Kim Christensen, Julian Verdurmen
Copyright: Copyright (c) 2004-2020 NLog Project - https://nlog-project.org/
License type: BSD3
License details: https://opensource.org/license/bsd-3-clause/
NLog
Version: 5.0.0
Vendor: Jarek Kowalski, Kim Christensen, Julian Verdurmen
Copyright: Copyright (c) 2004-2020 NLog Project - https://nlog-project.org/
License type: BSD3
License details: https://opensource.org/license/bsd-3-clause/
NLog.Database
Version: 5.1.3
Vendor: NLog Project
Copyright: Copyright (c) 2004-2023 NLog Project - https://nlog-project.org/
License type: BSD3
License details: https://opensource.org/license/bsd-3-clause/
NLog.Database
Version: 5.0.0
Vendor: NLog Project
Copyright: Copyright (c) 2004-2023 NLog Project - https://nlog-project.org/
License type: BSD3
License details: https://opensource.org/license/bsd-3-clause/
NLog.Extensions.Logging
Version: 1.7.5
Vendor: Microsoft, Julian Verdurmen
Copyright: Copyright (c) 2016, NLog
License type: BSD2
License details: https://opensource.org/license/bsd-2-clause/
NLog.Extensions.Logging
Version: 5.0.1
Vendor: Microsoft, Julian Verdurmen
Copyright: Copyright (c) 2016, NLog
License type: BSD2
License details: https://opensource.org/license/bsd-2-clause/
NLog.Extensions.Logging
Version: 5.2.3
Vendor: Microsoft, Julian Verdurmen
Copyright: Copyright (c) 2016, NLog
License type: BSD2
License details: https://opensource.org/license/bsd-2-clause/
NLog.Extensions.Logging
Version: 5.0.0
Vendor: Microsoft, Julian Verdurmen
Copyright: Copyright (c) 2016, NLog
License type: BSD2
License details: https://opensource.org/license/bsd-2-clause/
NLog.Extensions.Logging
Version: 1.7.4
Vendor: Microsoft, Julian Verdurmen
Copyright: Copyright (c) 2016, NLog
License type: BSD2
License details: https://opensource.org/license/bsd-2-clause/
NLog.Web.AspNetCore
Version: 5.2.3
Vendor: NLog Project
Copyright: Copyright (c) 2015-2023 NLog Project - https://nlog-project.org/
License type: BSD3
License details: https://opensource.org/license/bsd-3-clause/
NLog.Web.AspNetCore
Version: 4.14.0
Vendor: NLog Project
Copyright: Copyright (c) 2015-2021 NLog Project - https://nlog-project.org/
License type: BSD3
License details: https://opensource.org/license/bsd-3-clause/
NLog.Web.AspNetCore
Version: 5.2.2
Vendor: NLog Project
Copyright: Copyright (c) 2015-2023 NLog Project - https://nlog-project.org/
License type: BSD3
License details: https://opensource.org/license/bsd-3-clause/
NLog.Web.AspNetCore
Version: 4.15.0
Vendor: NLog Project
Copyright: Copyright (c) 2015-2022 NLog Project - https://nlog-project.org/
License type: BSD3
License details: https://opensource.org/license/bsd-3-clause/
Npgsql
Version: 4.0.13
Vendor: Npgsql
Copyright: Copyright 2019 © The Npgsql Development Team
License type: POSTGRESQL
License details:
Npgsql
Version: 6.0.7
Vendor: Npgsql
Copyright: Copyright 2021 © The Npgsql Development Team
License type: POSTGRESQL
License details:
Npgsql.EntityFrameworkCore.PostgreSQL
Version: 6.0.4
Vendor: Npgsql
Copyright: Copyright 2021 © The Npgsql Development Team
License type: POSTGRESQL
License details:
NSubstitute
Version: 4.4.0
Vendor: David Tchepak
Copyright: Copyright (c) 2009 Anthony Egerton ([email protected]) and David Tchepak ([email protected])
License type: BSD3
License details: https://opensource.org/license/bsd-3-clause/
NSubstitute
Version: 5.0.0
Vendor: David Tchepak
Copyright: Copyright (c) 2009 Anthony Egerton ([email protected]) and David Tchepak ([email protected])
License type: BSD3
License details: https://opensource.org/license/bsd-3-clause/
NSubstitute
Version: 4.3.0
Vendor: David Tchepak
Copyright: Copyright (c) 2009 Anthony Egerton ([email protected]) and David Tchepak ([email protected])
License type: BSD3
License details: https://opensource.org/license/bsd-3-clause/
NSubstitute
Version: 4.2.1
Vendor: David Tchepak
Copyright: Copyright (c) 2009 Anthony Egerton ([email protected]) and David Tchepak ([email protected])
License type: BSD3
License details: https://opensource.org/license/bsd-3-clause/
NSubstitute.Analyzers.CSharp
Version: 1.0.15
Vendor: NSubstitute
Copyright: Copyright (c) 2018 Tomasz Podolak
License type: MIT
License details: https://opensource.org/license/mit/
NuGet.Common
Version: 6.5.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.39
NuGet.Configuration
Version: 6.5.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.40
NuGet.DependencyResolver.Core
Version: 5.11.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.41
NuGet.Frameworks
Version: 6.5.0
Vendor: Jean-Pierre Briedé
Copyright: Copyright (c) .NET Foundation and Contributors.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.42
NuGet.Frameworks
Version: 5.11.0
Vendor: Jean-Pierre Briedé
Copyright: Copyright (c) .NET Foundation and Contributors.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.43
NuGet.LibraryModel
Version: 5.11.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.44
NuGet.Packaging
Version: 6.5.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.45
NuGet.ProjectModel
Version: 5.11.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.46
NuGet.Protocol
Version: 6.5.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.47
NuGet.Versioning
Version: 6.5.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.48
Owin
Version: 1.0.0
Vendor: Louis DeJardin
Copyright:
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.49
PactNet
Version: 4.1.0
Vendor: Pact Foundation
Copyright: Copyright 2021 (c) Pact Foundation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
Pipelines.Sockets.Unofficial
Version: 2.2.0
Vendor: Marc Gravell
Copyright: Marc Gravell 2018
License type: MIT
License details: https://opensource.org/license/mit/
Polly
Version: 7.2.3
Vendor: Michael Wolfenden, App vNext
Copyright: Copyright (c) 2021, App vNext
License type: BSD3
License details: https://opensource.org/license/bsd-3-clause/
Polly.Contrib.WaitAndRetry
Version: 1.1.1
Vendor: App vNext and contributors
Copyright: Copyright (c) 2020, App vNext and contributors
License type: BSD3
License details: https://opensource.org/license/bsd-3-clause/
Polly-Signed
Version: 5.9.0
Vendor: App vNext
Copyright: Copyright © 2018, App vNext
License type: BSD4CLAUSE
License details: https://spdx.org/licenses/BSD-4-Clause.html
Quartz
Version: 3.0.7
Vendor: Marko Lahma, Quartz.NET
Copyright: Copyright Marko Lahma
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.50
RabbitMQ.Client
Version: 5.1.2
Vendor: VMware
Copyright: Copyright © 2007-2020 VMware, Inc. or its affiliates.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.84
RabbitMQ.Client
Version: 6.4.0
Vendor: VMware
Copyright: Copyright © 2007-2020 VMware, Inc. or its affiliates.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.85
RabbitMQ.Client
Version: 6.5.0
Vendor: VMware
Copyright: Copyright © 2007-2020 VMware, Inc. or its affiliates.
License type:
License details:
RazorEngine.NetCore
Version: 3.1.0
Vendor: RazorEngine
Copyright: RazorEngine Copyright © RazorEngine Project 2011-2020
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.51
Remotion.Linq
Version: 2.2.0
Vendor: rubicon IT
Copyright: Copyright (c) rubicon IT GmbH, www.rubicon.eu
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.52
RichardSzalay.MockHttp
Version: 6.0.0
Vendor: Richard Szalay
Copyright: Copyright 2018 Richard Szalay
License type: MIT
License details: https://opensource.org/license/mit/
RichardSzalay.MockHttp
Version: 5.0.0
Vendor: Richard Szalay
Copyright: Copyright 2018 Richard Szalay
License type: MIT
License details: https://opensource.org/license/mit/
runtime.debian.8-x64.runtime.native.System.Security.Cryptography.OpenSsl
Version: 4.3.2
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
runtime.debian.8-x64.runtime.native.System.Security.Cryptography.OpenSsl
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
runtime.fedora.23-x64.runtime.native.System.Security.Cryptography.OpenSsl
Version: 4.3.2
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
runtime.fedora.23-x64.runtime.native.System.Security.Cryptography.OpenSsl
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
runtime.fedora.24-x64.runtime.native.System.Security.Cryptography.OpenSsl
Version: 4.3.2
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
runtime.fedora.24-x64.runtime.native.System.Security.Cryptography.OpenSsl
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
runtime.native.System
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
runtime.native.System.Data.SqlClient.sni
Version: 4.7.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
runtime.native.System.IO.Compression
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
runtime.native.System.Net.Http
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
runtime.native.System.Security.Cryptography.Apple
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
runtime.native.System.Security.Cryptography.OpenSsl
Version: 4.3.2
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
runtime.native.System.Security.Cryptography.OpenSsl
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
runtime.opensuse.13.2-x64.runtime.native.System.Security.Cryptography.OpenSsl
Version: 4.3.2
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
runtime.opensuse.13.2-x64.runtime.native.System.Security.Cryptography.OpenSsl
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
runtime.opensuse.42.1-x64.runtime.native.System.Security.Cryptography.OpenSsl
Version: 4.3.2
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
runtime.opensuse.42.1-x64.runtime.native.System.Security.Cryptography.OpenSsl
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
runtime.osx.10.10-x64.runtime.native.System.Security.Cryptography.Apple
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
runtime.osx.10.10-x64.runtime.native.System.Security.Cryptography.OpenSsl
Version: 4.3.2
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
runtime.osx.10.10-x64.runtime.native.System.Security.Cryptography.OpenSsl
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
runtime.rhel.7-x64.runtime.native.System.Security.Cryptography.OpenSsl
Version: 4.3.2
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
runtime.rhel.7-x64.runtime.native.System.Security.Cryptography.OpenSsl
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
runtime.ubuntu.14.04-x64.runtime.native.System.Security.Cryptography.OpenSsl
Version: 4.3.2
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
runtime.ubuntu.14.04-x64.runtime.native.System.Security.Cryptography.OpenSsl
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
runtime.ubuntu.16.04-x64.runtime.native.System.Security.Cryptography.OpenSsl
Version: 4.3.2
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
runtime.ubuntu.16.04-x64.runtime.native.System.Security.Cryptography.OpenSsl
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
runtime.ubuntu.16.10-x64.runtime.native.System.Security.Cryptography.OpenSsl
Version: 4.3.2
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
runtime.ubuntu.16.10-x64.runtime.native.System.Security.Cryptography.OpenSsl
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
runtime.win-arm64.runtime.native.System.Data.SqlClient.sni
Version: 4.4.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
runtime.win-x64.runtime.native.System.Data.SqlClient.sni
Version: 4.4.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
runtime.win-x86.runtime.native.System.Data.SqlClient.sni
Version: 4.4.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
SAML v2.0
Version: 2.8.6.0
Vendor:
Copyright: Copyright (c) ComponentSpace 2004 - 2017
License type: Commercial
License details: https://www.componentspace.com/license-agreement
sautinsoft.pdffocus
Version: 8.6.1.18
Vendor: SautinSoft
Copyright: Copyright(C) 2002-2023
License type:
License details:
Sentinel RMS
Version: 10.0.0.0121
Vendor: SafeNet
Copyright:
License type: Commercial
License details:
Serilog
Version: 2.6.0
Vendor: Serilog Contributors
Copyright: Copyright © 2016 Serilog Contributors
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.53
Serilog.Settings.AppSettings
Version: 2.1.2
Vendor: Serilog Contributors
Copyright: Copyright © 2016 Serilog Contributors
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.54
Serilog.Sinks.ColoredConsole
Version: 3.0.1
Vendor: Serilog Contributors
Copyright: Copyright © 2016 Serilog Contributors
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.55
Serilog.Sinks.Console
Version: 3.0.1
Vendor: Serilog Contributors
Copyright: Copyright © 2016 Serilog Contributors
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.56
Serilog.Sinks.File
Version: 3.2.0
Vendor: Serilog Contributors
Copyright: Copyright © 2016 Serilog Contributors
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.57
Serilog.Sinks.RollingFile
Version: 3.3.0
Vendor: Serilog Contributors
Copyright: Copyright © 2016 Serilog Contributors
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.58
SerilogTraceListener
Version: 3.0.10041
Vendor: Serilog Contributors
Copyright: Copyright © 2016 Serilog Contributors
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.59
SharpCompress
Version: 0.23.0
Vendor: Adam Hathcock
Copyright: Copyright (c) 2014 Adam Hathcock
License type: MIT
License details: https://opensource.org/license/mit/
SharpZipLib
Version: 1.4.2
Vendor: SharpDevelop
Copyright: Copyright © 2000-2019 SharpZipLib Contributors
License type: MIT
License details: https://opensource.org/license/mit/
SharpZipLib
Version: 1.4.1
Vendor: SharpDevelop
Copyright: Copyright © 2000-2019 SharpZipLib Contributors
License type: MIT
License details: https://opensource.org/license/mit/
siccarcmd
Version: 1.0.0
Vendor: Siccar
Copyright: Wallet.Services (Scotland) Limited
License type:
License details:
SpecFlow.Assist.Dynamic
Version: 1.4.2
Vendor: Marcus Hammarberg
Copyright: Copyright © Marcus Hammarberg 2020
License type: MIT
License details: https://opensource.org/license/mit/
SpecFlow.MsTest
Version: 3.9.74
Vendor: SpecFlow Team
Copyright: Copyright © SpecFlow Team
License type: BSD4CLAUSE
License details: https://spdx.org/licenses/BSD-4-Clause.html
Spring.Core
Version: 2.0.1
Vendor: Spring
Copyright: Copyright 2002-2021 Spring.NET Framework Team.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.60
SQLitePCLRaw.bundle_e_sqlite3
Version: 2.1.2
Vendor: Eric Sink
Copyright: Copyright 2014-2022 SourceGear, LLC
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.61
SQLitePCLRaw.core
Version: 2.1.2
Vendor: Eric Sink
Copyright: Copyright 2014-2018 Zumero, LLC
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.62
SQLitePCLRaw.lib.e_sqlite3
Version: 2.1.2
Vendor: Eric Sink
Copyright: Copyright 2014-2023 SourceGear, LLC
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.63
SQLitePCLRaw.provider.e_sqlite3
Version: 2.1.2
Vendor: Eric Sink
Copyright: Copyright 2014-2023 SourceGear, LLC
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.64
StackExchange.Redis
Version: 2.2.88
Vendor: Stack Exchange
Copyright: 2014 - 2023 Stack Exchange, Inc.
License type: MIT
License details: https://opensource.org/license/mit/
StackExchange.Redis
Version: 2.5.43
Vendor: Stack Exchange
Copyright: 2014 - 2023 Stack Exchange, Inc.
License type: MIT
License details: https://opensource.org/license/mit/
StackExchange.Redis.StrongName
Version: 1.2.6
Vendor: Stack Exchange, Inc., marc.gravell
Copyright: 2017 Stack Exchange, Inc.
License type: MIT
License details: https://opensource.org/license/mit/
Steeltoe.Common
Version: 3.2.0
Vendor: Steeltoe
Copyright: Copyright 2023 Steeltoe
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.65
Steeltoe.Common.Abstractions
Version: 3.2.0
Vendor: Steeltoe
Copyright: Copyright 2023 Steeltoe
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.66
Steeltoe.Common.Http
Version: 3.2.0
Vendor: Steeltoe
Copyright: Copyright 2023 Steeltoe
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.67
Steeltoe.Connector.Abstractions
Version: 3.2.0
Vendor: Steeltoe
Copyright: Copyright 2023 Steeltoe
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.68
Steeltoe.Connector.ConnectorBase
Version: 3.2.0
Vendor: Steeltoe
Copyright: Copyright 2023 Steeltoe
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.69
Steeltoe.Discovery.Abstractions
Version: 3.2.0
Vendor: Steeltoe
Copyright: Copyright 2023 Steeltoe
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.70
Steeltoe.Discovery.ClientBase
Version: 3.2.0
Vendor: Steeltoe
Copyright: Copyright 2023 Steeltoe
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.71
Steeltoe.Discovery.Eureka
Version: 3.2.0
Vendor: Steeltoe
Copyright: Copyright 2023 Steeltoe
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.72
Steeltoe.Extensions.Configuration.Abstractions
Version: 3.2.0
Vendor: Steeltoe
Copyright: Copyright 2023 Steeltoe
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.73
Swashbuckle.AspNetCore
Version: 6.3.1
Vendor: Richard Morris
Copyright: Copyright (c) 2016 Richard Morris
License type: MIT
License details: https://opensource.org/license/mit/
Swashbuckle.AspNetCore
Version: 6.5.0
Vendor: Richard Morris
Copyright: Copyright (c) 2016 Richard Morris
License type: MIT
License details: https://opensource.org/license/mit/
Swashbuckle.AspNetCore.Swagger
Version: 6.3.1
Vendor: Richard Morris
Copyright: Copyright (c) 2016 Richard Morris
License type: MIT
License details: https://opensource.org/license/mit/
Swashbuckle.AspNetCore.Swagger
Version: 6.5.0
Vendor: Richard Morris
Copyright: Copyright (c) 2016 Richard Morris
License type: MIT
License details: https://opensource.org/license/mit/
Swashbuckle.AspNetCore.SwaggerGen
Version: 6.3.1
Vendor: Richard Morris
Copyright: Copyright (c) 2016 Richard Morris
License type: MIT
License details: https://opensource.org/license/mit/
Swashbuckle.AspNetCore.SwaggerGen
Version: 6.5.0
Vendor: Richard Morris
Copyright: Copyright (c) 2016 Richard Morris
License type: MIT
License details: https://opensource.org/license/mit/
Swashbuckle.AspNetCore.SwaggerUI
Version: 6.3.1
Vendor: Richard Morris
Copyright: Copyright (c) 2016 Richard Morris
License type: MIT
License details: https://opensource.org/license/mit/
Swashbuckle.AspNetCore.SwaggerUI
Version: 6.5.0
Vendor: Richard Morris
Copyright: Copyright (c) 2016 Richard Morris
License type: MIT
License details: https://opensource.org/license/mit/
Swashbuckle.Core
Version: 5.6.0
Vendor: Richard Morris
Copyright: Copyright (c) 2013, Richard Morris
License type: BSD4CLAUSE
License details:
System.AppContext
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Buffers
Version: 4.5.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Buffers
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.CodeDom
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Collections
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Collections.Concurrent
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Collections.Immutable
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Collections.Immutable
Version: 1.5.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Collections.Immutable
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.ComponentModel
Version: 4.0.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.ComponentModel.Annotations
Version: 4.5.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Composition
Version: 1.0.31
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Composition.AttributedModel
Version: 1.0.31
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Composition.Convention
Version: 1.0.31
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Composition.Hosting
Version: 1.0.31
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Composition.Runtime
Version: 1.0.31
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Composition.TypedParts
Version: 1.0.31
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Configuration.Abstractions
Version: 2.0.2.45
Vendor: David Whitney
Copyright: Copyright 2015
License type: MIT
License details: https://opensource.org/license/mit/
System.Configuration.ConfigurationManager
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Configuration.ConfigurationManager
Version: 4.7.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Configuration.ConfigurationManager
Version: 4.5.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Configuration.ConfigurationManager
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Configuration.ConfigurationManager
Version: 6.0.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Console
Version: 4.3.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Console
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Data.SqlClient
Version: 4.8.5
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Data.SqlClient
Version: 4.8.3
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Data.SQLite.Core
Version: 1.0.111
Vendor: SQLite
Copyright: Public domain
License type:
License details:
System.Diagnostics.Debug
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Diagnostics.DiagnosticSource
Version: 6.0.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Diagnostics.DiagnosticSource
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Diagnostics.DiagnosticSource
Version: 4.5.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Diagnostics.DiagnosticSource
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Diagnostics.EventLog
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Diagnostics.EventLog
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Diagnostics.FileVersionInfo
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Diagnostics.PerformanceCounter
Version: 5.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Diagnostics.StackTrace
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Diagnostics.Tools
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Diagnostics.Tracing
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Drawing.Common
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Drawing.Common
Version: 4.7.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Drawing.Common
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Dynamic.Runtime
Version: 4.0.11
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Formats.Asn1
Version: 5.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Globalization
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Globalization.Calendars
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Globalization.Extensions
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.IdentityModel.Tokens.Jwt
Version: 6.30.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.IdentityModel.Tokens.Jwt
Version: 6.8.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.IdentityModel.Tokens.Jwt
Version: 6.24.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.IdentityModel.Tokens.Jwt
Version: 6.21.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.IdentityModel.Tokens.Jwt
Version: 6.23.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Interactive.Async
Version: 3.2.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.74
System.IO
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.IO.Abstractions
Version: 16.1.26
Vendor: Tatham Oddie
Copyright: Copyright © Tatham Oddie 2010
License type: MIT
License details: https://opensource.org/license/mit/
System.IO.Compression
Version: 4.0.0-beta-22231
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.IO.Compression
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.IO.Compression.ZipFile
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.IO.FileSystem
Version: 4.0.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.IO.FileSystem
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.IO.FileSystem.Primitives
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.IO.Packaging
Version: 4.5.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.IO.Pipelines
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.IO.Pipelines
Version: 5.0.2
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.IO.Pipelines
Version: 6.0.3
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Linq
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Linq.Async
Version: 6.0.1
Vendor: Microsoft
Copyright: Copyright (c) .NET Foundation and Contributors.
License type: MIT
License details: https://opensource.org/license/mit/
System.Linq.Expressions
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Management
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Management.Automation.dll
Version: 10.0.10586
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type:
License details:
System.Memory
Version: 4.5.5
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Memory
Version: 4.5.4
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Memory.Data
Version: 1.0.2
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Net.Http
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Net.Http
Version: 4.3.4
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Net.Http
Version: 4.3.2
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Net.Http.Formatting.Extension
Version: 5.2.3
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSL
License details: https://github.com/FINRAOS/MSL/blob/master/LICENSE
System.Net.Primitives
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Net.Sockets
Version: 4.3.0-preview1-24530-04
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Net.Sockets
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Net.WebSockets.WebSocketProtocol
Version: 5.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Net.WebSockets.WebSocketProtocol
Version: 4.5.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Numerics.Vectors
Version: 4.4.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Numerics.Vectors
Version: 4.5.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.ObjectModel
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Private.DataContractSerialization
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Private.ServiceModel
Version: 4.10.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Private.Uri
Version: 4.3.2
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Reactive
Version: 5.0.0
Vendor: .NET Foundation and Contributors
Copyright: Copyright (c) .NET Foundation and Contributors.
License type: MIT
License details: https://opensource.org/license/mit/
System.Reactive.Linq
Version: 5.0.0
Vendor: Microsoft
Copyright: Copyright (c) .NET Foundation and Contributors.
License type: MIT
License details: https://opensource.org/license/mit/
System.Reflection
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Reflection.DispatchProxy
Version: 4.7.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Reflection.Emit
Version: 4.7.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Reflection.Emit
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Reflection.Emit.ILGeneration
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Reflection.Emit.Lightweight
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Reflection.Extensions
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Reflection.Metadata
Version: 7.0.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Reflection.Metadata
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Reflection.Metadata
Version: 1.6.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Reflection.MetadataLoadContext
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Reflection.MetadataLoadContext
Version: 4.6.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Reflection.Primitives
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Reflection.TypeExtensions
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Resources.Extensions
Version: 5.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Resources.ResourceManager
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Runtime
Version: 4.3.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Runtime
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Runtime.Caching
Version: 4.7.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Runtime.Caching
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Runtime.Caching
Version: 5.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Runtime.CompilerServices.Unsafe
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Runtime.CompilerServices.Unsafe
Version: 4.5.3
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Runtime.Extensions
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Runtime.Handles
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Runtime.InteropServices
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Runtime.InteropServices.RuntimeInformation
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Runtime.Numerics
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Runtime.Serialization.Primitives
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Runtime.Serialization.Xml
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Security.AccessControl
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Security.AccessControl
Version: 4.7.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Security.AccessControl
Version: 4.5.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Security.Cryptography.Algorithms
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Security.Cryptography.Algorithms
Version: 4.3.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Security.Cryptography.Algorithms.Extensions
Version: 1.0.0
Vendor: Thierry Habart
Copyright:
License type:
License details:
System.Security.Cryptography.Cng
Version: 4.5.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Security.Cryptography.Cng
Version: 5.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Security.Cryptography.Cng
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Security.Cryptography.Csp
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Security.Cryptography.Encoding
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Security.Cryptography.OpenSsl
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Security.Cryptography.Pkcs
Version: 5.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Security.Cryptography.Primitives
Version: 4.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Security.Cryptography.Primitives
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Security.Cryptography.ProtectedData
Version: 4.5.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Security.Cryptography.ProtectedData
Version: 4.7.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Security.Cryptography.ProtectedData
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Security.Cryptography.X509Certificates
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Security.Cryptography.Xml
Version: 5.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Security.Permissions
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Security.Permissions
Version: 4.7.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Security.Permissions
Version: 4.5.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Security.Permissions
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Security.Principal.Windows
Version: 5.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Security.Principal.Windows
Version: 4.7.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Security.Principal.Windows
Version: 4.5.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.ServiceModel.Primitives
Version: 4.10.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.ServiceModel.Security
Version: 4.10.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.ServiceProcess.ServiceController
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.ServiceProcess.ServiceController
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Spatial
Version: 5.8.4
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Spatial
Version: 5.8.5
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT0
License details: https://github.com/aws/mit-0
System.Text.Encoding
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Text.Encoding.CodePages
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Text.Encoding.CodePages
Version: 4.5.0-rc1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Text.Encoding.CodePages
Version: 4.7.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Text.Encoding.CodePages
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Text.Encoding.Extensions
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Text.Encodings.Web
Version: 5.0.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Text.Encodings.Web
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Text.Encodings.Web
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Text.Json
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Text.Json
Version: 7.0.2
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Text.RegularExpressions
Version: 4.3.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Text.RegularExpressions
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Threading
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Threading.Channels
Version: 4.7.1
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Threading.Channels
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Threading.Tasks
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Threading.Tasks.Dataflow
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Threading.Tasks.Extensions
Version: 4.5.2
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Threading.Tasks.Extensions
Version: 4.5.4
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Threading.Tasks.Extensions
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Threading.Timer
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.ValueTuple
Version: 4.5.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.ValueTuple
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Windows.Extensions
Version: 4.7.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Windows.Extensions
Version: 7.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Windows.Extensions
Version: 6.0.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MIT
License details: https://opensource.org/license/mit/
System.Xml.ReaderWriter
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Xml.XDocument
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Xml.XmlDocument
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Xml.XmlSerializer
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Xml.XPath
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
System.Xml.XPath.XDocument
Version: 4.3.0
Vendor: Microsoft
Copyright: © Microsoft Corporation. All rights reserved.
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
Umble.Construct
Version: 10.0.2
Vendor: Umble
Copyright:
License type:
License details:
Validation
Version: 2.4.22
Vendor: Andrew Arnott
Copyright:
License type: MSPL
License details: https://opensource.org/license/ms-pl-html/
Validation
Version: 2.4.18
Vendor: Andrew Arnott
Copyright:
License type: MSPL
License details: https://opensource.org/license/ms-pl-html/
Wdc.System.Net.Http.Formatting.NetStandard
Version: 1.0.4
Vendor: Atila Tosta
Copyright: Copyright 2017, Atila Tosta
License type: UNKNOWN
License details:
WebGrease
Version: 1.6.0
Vendor: Microsoft
Copyright: Copyright © Microsoft 2012
License type: MSEULA
License details: https://www.microsoft.com/web/webpi/eula/net_library_eula_enu.htm
WiX.Toolset.UnofficialFork
Version: 3.11.2
Vendor: Jozef Izso
Copyright: Copyright (c) 2015-2019 Jozef Izso
License type: MIT
License details: https://opensource.org/license/mit/
xunit
Version: 2.4.2
Vendor: Brad Wilson
Copyright: Copyright (c) .NET Foundation and Contributors All Rights Reserved
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.75
xunit
Version: 2.4.1
Vendor: Brad Wilson
Copyright: Copyright (c) .NET Foundation and Contributors All Rights Reserved
License type: MIT
License details: https://opensource.org/license/mit/
xunit.abstractions
Version: 2.0.3
Vendor: Brad Wilson
Copyright: Copyright (c) .NET Foundation and Contributors All Rights Reserved
License type: MIT
License details: https://opensource.org/license/mit/
xunit.analyzers
Version: 0.10.0
Vendor: James Newkirk, Brad Wilson
Copyright: Copyright (C) .NET Foundation
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.76
xunit.analyzers
Version: 1.0.0
Vendor: James Newkirk, Brad Wilson
Copyright: Copyright (C) .NET Foundation
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.77
xunit.assert
Version: 2.4.2
Vendor: Brad Wilson
Copyright: Copyright (c) .NET Foundation and Contributors All Rights Reserved
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.78
xunit.assert
Version: 2.4.1
Vendor: Brad Wilson
Copyright: Copyright (c) .NET Foundation and Contributors All Rights Reserved
License type: MIT
License details: https://opensource.org/license/mit/
xunit.core
Version: 2.4.2
Vendor: Brad Wilson
Copyright: Copyright (c) .NET Foundation and Contributors All Rights Reserved
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.79
xunit.core
Version: 2.4.1
Vendor: Brad Wilson
Copyright: Copyright (c) .NET Foundation and Contributors All Rights Reserved
License type: MIT
License details: https://opensource.org/license/mit/
xunit.extensibility.core
Version: 2.4.2
Vendor: Brad Wilson
Copyright: Copyright (c) .NET Foundation and Contributors All Rights Reserved
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.80
xunit.extensibility.core
Version: 2.4.1
Vendor: Brad Wilson
Copyright: Copyright (c) .NET Foundation and Contributors All Rights Reserved
License type: MIT
License details: https://opensource.org/license/mit/
xunit.extensibility.execution
Version: 2.4.2
Vendor: Brad Wilson
Copyright: Copyright (c) .NET Foundation and Contributors All Rights Reserved
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.81
xunit.extensibility.execution
Version: 2.4.1
Vendor: Brad Wilson
Copyright: Copyright (c) .NET Foundation and Contributors All Rights Reserved
License type: MIT
License details: https://opensource.org/license/mit/
xunit.runner.console
Version: 2.4.2
Vendor: James Newkirk, Brad Wilson
Copyright: Copyright (C) .NET Foundation
License type: APACHE20
License details: https://www.apache.org/licenses/LICENSE-2.82
xunit.runner.console
Version: 2.4.1
Vendor: James Newkirk, Brad Wilson
Copyright: Copyright (C) .NET Foundation
License type: MIT
License details: https://opensource.org/license/mit/
xunit.runner.visualstudio
Version: 2.4.5
Vendor: Brad Wilson
Copyright: Copyright (c) .NET Foundation and Contributors All Rights Reserved
License type: MIT
License details: https://opensource.org/license/mit/
xunit.runner.visualstudio
Version: 2.4.3
Vendor: Brad Wilson
Copyright: Copyright (c) .NET Foundation and Contributors All Rights Reserved
License type: MIT
License details: https://opensource.org/license/mit/
YamlDotNet
Version: 8.1.0
Vendor: Microsoft
Copyright: Copyright (c) 2008, 2009, 2010, 2011, 2012, 2013, 2014 Antoine Aubry and contributors
License type: MIT
License details: https://opensource.org/license/mit/
Parent topic: Welcome to the Trados GroupShare 2020 SR1 documentation
MultiTerm general conrefs
Current version: - 2022 SR1
Long name of the product: MultiTerm
Short name of the product: MultiTerm
SDL MultiTerm Desktop full: - MultiTerm Desktop
MultiTerm Desktop short: - MultiTerm Desktop
Word Integration: - MultiTerm Word Integration
MultiTerm Full: MultiTerm 2022 SR1
MultiTerm version short: MultiTerm 2022 SR1
MultiTerm previous version short MultiTerm 2019
MultiTerm previous version long SDL MultiTerm 2019
MultiTerm Widget: - MultiTerm Widget
MultiTerm Extract: - MultiTerm Extract
MultiTerm Extract: - MultiTerm Extract
MultiTerm Convert: - MultiTerm Convert
MultiTerm Convert Long: - MultiTerm Convert
MultiTerm full: - MultiTerm 2022 SR1
MultiTerm short: - MultiTerm 2022 SR1
MultiTerm 2015: - MultiTerm 2015
MultiTerm 2014: - MultiTerm 2014
MT Widget Full: - MultiTerm Widget
MultiTerm Release Notes: MultiTerm 2022 SR1 Release Notes
MultiTerm Help link: - MultiTerm 2022 SR1 Help
Installation Guide link: - MultiTerm 2022 SR1 Installation Guide
MultiTerm Extract Tools Guide: - MultiTerm Extract 2022 SR1 Tools Guide
MultiTerm Widget Automated Deployment: - MultiTerm Widget 2022 SR1 Automated Deployment Guide
MultiTerm WebHelp: - MultiTerm WebHelp 2022 SR1
Help location: - Trados Studio 2022 SR1 Help

File paths
MultiTerm17
% Program Files%(x86)%\Trados\MultiTerm\MultiTerm17\Templates
%Program Files%\Trados\MultiTerm\MultiTerm17\Templates
%programfiles%\Trados\MultiTerm\MultiTerm17
%programfiles(x86)%\Trados\MultiTerm\MultiTerm17\Templates
%programfiles%\Trados\MultiTerm\MultiTerm17\Templates
%programfiles%\Trados\MultiTerm\MultiTerm17
%programfiles(x86)%\Trados\MultiTerm\MultiTerm17
%ALLUSERSPROFILE%\Package Cache\Trados\MultiTermDesktop2022SR1
%ALLUSERSPROFILE%\Package Cache\Trados\MultiTermDesktop2022SR1\modules
%ProgramFiles%\Trados\MultiTerm\MultiTerm17
%temp%\multiterm17Updates
%ALLUSERSPROFILE%\Trados\MultiTerm\MultiTerm17\Updates
%appdata%\Trados\MultiTerm\MultiTerm17\WidgetSettings.xml
Clearing segment formatting
You can remove the formatting from an entire target segment or only from a part of it if that target segment no longer needs to contain the same
formatting tags as its corresponding source segment.

Procedure
1. Open the appropriate file in Online Editor.
2. Do one of the following:
To clear the formatting of a certain part of a target segment, select the part whose formatting you want to clear, and then, on the
Home tab, in the Formatting group, select Clear Formatting > Clear Formatting.
To clear all the formatting of an entire target segment, select the segment whose formatting you want to clear, and then, on the Home
tab, in the Formatting group, select Clear Formatting > Clear All Formatting.
Parent topic: Formatting segments
Known issues
The following list details the limitations associated with Trados GroupShare 2020 SR1 CU9.
Support for SQL Server aliases might break after upgrading to GroupShare 2020 CU9. This is due to migrating a number of services to
.NET 6.
The Translation Model Container database cannot be created when using SQL user for the connection between Trados GroupShareand
SQL server. Since we don't recommend using SQL authentication for security reasons, there are no plans to address this in a future release.
For more information, see Server security configuration recommendations (CRQ-30640)
When a language pair is added to an existing Trados GroupShare project from Studio, no project files are added for the new languages.
This will be addressed with the next Trados Studio update. (LTGS-11782)
Finalized files are sometimes excluded from the Tasks report. (LTGS-11763)
Adding 'yyyy' as a Date & Time pattern to a new Language Resource rule fails with an 'invalid language resource data fortype
DateTimeRecognizer' error message. (LTGS-11472)
MultiTerm Online: Opening termbases created with specific definition files fails with a NullPointerException error message. A potential
workaround to this issue is to avoid having commas in the termbase name. (LTGS-11775)
Emoji-only segment cannot be saved in TM and show a 'empty target cannot be saved in the Translation Memory ' error. (LTGS-
11787)
When running batch tasks on native files of a server-based project, the Upload and Check in files step fails to complete. (LTGS-11825)
Adding reference files from Trados Studio by using the Add Reference Files option results in an error when trying to check in. (LTGS-
11830)
In the Reporting tab, sorting the Tasks table will not work or will order the tasks incorrectly. Contact support for a custom SQL script
that improves this if needed. This will be addressed in future versions. (LTGS-11851)
Parent topic: Changes introduced in Trados Groupshare 2020 SR1 CU9
Format of variables
Variables are recognized tokens and also a language resource.
Theoretically, you can use any character in a variable. However, a translation memory (TM) segments text before it checks for variables, so you
should not use any character that might cause a segment break in variables. For example, you would normally not use a period, colon, semicolon
or question mark in a variable.
Also, although you can have spaces within a variable, do not start or end a variable with a space.
For most languages, a variable must be followed by a punctuation mark or a space (or other white space character), so that a TM can recognize
the variable in source text. However, this is not the case for languages which do not use blanks to separate words, such as Japanese, Chinese or
Thai.

Example
Assume:
The TM contains the following variables:
Mary Brown
John Smith
A TM entry contains the source language text: Mary Brown works here.
The source text presented for translation is: John Smith works here.
The TM recognizes an exact match for its stored source, and provides the translation, substituting John Smith for Mary Brown.
Parent topic: Variables
Step 1c: Updating an existing project
Upload new translatable and reference files to existing projects. This is useful for situations when you receive updated project files from your
customer, or additional files that were missed from the initial drop.

Pre-requisites
Only users with Update Project Files permission can add or cancel files for an existing project. As an Administrator make sure to add this
permissions to relevant users. For more information, see Add permissions to existing users roles.

Add new source files


Add new single files, multiple files, or .ZIP files. When you create a project from a .ZIP file, Trados GroupShare automatically identifies all the
translatable files from the root folder and from any subfolders available in the archive. If you add files that have already been added to a project,
the files will be ignored.
If your .ZIP archive also contains reference files or PerfectMatch files, make sure to use the structure and file naming described in the Required
folder hierarchy and naming for .ZIP archives. This hierarchy enables Trados GroupShare to map your source files to the corresponding
PerfectMatch files.
To add new source files to an existing project:
1. Go to the Projects view > All projects tab, and select the project that you want to update.
2. Click on the Update Project drop-down menu and select Add Files.
3. Select Add project files if you want new source files for your projects, or select Add reference files.
4. In the Add Project Files window, browse for or drag-and-drop your new source files.
5. Select Finish.

Update files
To replace existing project files with new versions that includes updated content:
1. Go to the Projects view, All projects tab, and select the project that you want to update.
2. Click on the Update Project drop-down menu and select Update Files. Optionally, you can first select the individual project files which you
want to update. Otherwise, Trados GroupShare will automatically map the corresponding original files name and relative project path,
based on their file names.
3. Select Update project files if you want to update source files for your projects, or select Update reference files if you are updating any
reference files in the project.
4. In the Update project files window, browse for or drag-and-drop the updated files.
If you are uploading a .ZIP archive which also contains reference files or PerfectMatch files, make sure to use the structure and file naming
described in the Required folder hierarchy and naming for .ZIP archives. This hierarchy enableTrados GroupShare to map your source files
to the corresponding PerfectMatch files.
5. Click Finish.

Canceling files
Note: If you want to add or update files from an archive, remember that the action will be performed separately for each type of files. A reference
file will not be added or updated from an archive if the Add Files/Update files operation was used and the rule applies vice versa.
Note: When you update files to a project, the initial translation will be applied and nothing will be lost in the process.
If you added a file to a project that doesn't need to be translated anymore, you can cancel the file. Remember that this operation is irreversible.
1. Go to the Projects view, All projects tab, and select the project that you want to cancel.
2. Click on the Update Project drop-down menu, and select Cancel files.
After you confirm the action, the file will be marked as canceled in the files list.
After you cancel a file, any actions that could be performed on regular files are disabled. (Phase change, External/Online check-out, Change
assignment/File planning, Triggering a PTA report, Finalization)

Analyze files reports for project updates


If you need to check how each file that you are adding or updating is impacting your project, reports will be generated automatically for each
individual project operation. Compare the results against the statistics for the current project or for the initial project.
To view full and individual reports, go to the Report view for your project, select the Analyze Files reports and a target language, then choose from
the available Analyze Files reports:
Initial project creation report, which is generated automatically when the project is created.
Full report, which contains information on all the files in the project, including any mid-project add/update file changes.
Add project file operation/Update project file operation. This will generate a report based on the files added/updated after the initial project
creation.
Limitation
Projects generated from Trados Studio and corrupted GroupShare projects do not include an Analysis report. Because of this, Trados
GroupShare cannot generate Full reports for such projects. The reports will be generated automatically for individual Add/Update project
operations.
Parent topic: Workflow for shared projects started in Trados GroupShare
Parent topic: Project management
Step 1: Adding database server
After you installTrados GroupShare, a default server is set. However, you can add as many servers as you need in order to create as many server-
based TMs as you need.

Procedure
1. Go to the System Configuration view.
2. In the Servers tab, select New Server.
3. In the Create Server dialog:
a. Choose a location for your server within the organization.
b. Enter a server name in the Name field.
c. Optionally, provide a description for your server.
d. Choose an authentication method.
4. Select Finish.
Parent topic: Configuring server-based TMs
Using smart actions
Smart actions are actions designed to boost your productivity while updating target segment in Online Editor. These actions include inserting tags,
placeables, terms, or fragment matches.

About this task


Placeables are elements which can be copied from the source segment to the target segment exactly as they are – for example, a phone number or
the year in which a book was written. Insert tags and placeables directly from the source text to make sure they are rendered correctly in the final
translation.
Fragment matches are parts of previously translated segments that are analyzed and suggested as possible translations in certain parts of the target
text.

Procedure
1. Open the appropriate file in Online Editor.
2. Select a target segment.
If its corresponding source segment contains any tags, placeables, terms, or fragment matches, their corresponding symbols are displayed.
3. Do one of the following:
To insert a tag into the target segment, select Insert Tag , and then select the
appropriate tag or tag pair.

Tip: Tags and tag pairs are displayed in the order of their relevance based on your position within the source segment. For example, if
a term in the target segment is written in bold and you select its correspondent in the source segment, the bold tag pair will be
displayed first. Also, tags and tag pairs which have already been used are displayed last; however, you can select them again if
necessary.
Also, you can move tags around in the target segment by using drag-and-drop.

To insert a placeable into the target segment, select Insert Placeables , and
then select the appropriate placeable.
In the source segment, placeables are underlined in blue.

To insert a term into the target segment, select Terms , and then select the appropriate
term.
In the source segment, terms have a red line above them.
To insert a fragment match into the target segment, select Fragment Matches
, and then select the appropriate match.
You can bring up the smart action menu at any time by selecting Ctrl + Comma.
Parent topic: Working with translation memories and terminology
Enhanced security policies
To enhance security, the default Trados GroupShare configuration no longer allows you to access the Online Editor via a different URL than the
one set up as External Server Address in the GroupShare Console.
You can still configure custom URLs if you want to use them for accessing the Online Editor. However, we recommend using the one set up as
External Server Address for convenience. To see how to configure those URLs, see the Changing the External Server Address topic in the Online
Help.
Parent topic: Changes introduced in Trados GroupShare 2020 SR1 CU6
Step 3a: Completing assignments in Trados Studio
When project managers move project files to a phase in Trados GroupShare, the users who are assigned to that phase receive automatic
notification emails. The notification emails inform users of the tasks they must work on and of the due date. Another possibility is to perform
translation or review work in Online Editor.

Before you begin


After assignments are completed, users must check in their translation or review tasks performed in Trados Studio, and must move them to the
next file phase from the same Trados Studio.
Make sure that the users who check in their assignments have the correct permissions to change the file phases, namely Change Current Phase
and Change Any Phase. Assign users the appropriate roles or adjust the permissions associated to their roles before users reach this project step.

Procedure
1. Click the link in the notification email to open your Trados GroupShare assigned files in Trados Studio.
2. In Trados Studio, in the Files view, select the file you want to check out.
Important: You cannot check out from Online Editor files which are already checked out in Trados Studio. Wait until the file is checked in
from Trados Studio before you check-it out (open) in Online Editor.
3. On the Home tab, select Check out.
4. On the Home tab, select one of the following: Open for Translation, Open for Review, Open for Sign-Off, depending on your assigned
tasks and project phase.
5. Start working on the file.
All the segments which were pre-translated based on similar, previously translated projects (namely, based on the PerfectMatch
functionality), are displayed as locked and signed-off. You can still edit them, if needed.
6. When finished, in the Files view, select the file you want to check in.
7. On the Home tab, select Check in.
8. Expand Change Phase and select the next phase the document should go to.
Note: If there are users already assigned to work on the file in the new phase, Trados GroupShare sends these users a phase change
notification email and updates the information in the Current Phase column of Trados GroupShare.
Parent topic: Workflow for shared projects started in Trados GroupShare
Related concepts
Standard roles and permissions
Dependencies between permissions
Translation statuses
New REST endpoints
Get Server Project Information
The new GetServerProjectInformation REST API retrieves all relevant information about a list of GroupShare projects and uses the following
format: GET server/api/projectserver/v2/projects/publishingInformation?projectIds={projectId,projectId_1,projectId_2}

Publish packages
PublishPackage endpoint uploads GroupShare packages block by block, which improves performance when uploading larger packages. The
PublishPackage, PublishPackageinBlocks, and FileUpload endpoints support CancellationToken.
The new endpoint uses the following format:api/projectserver/v2/projects/{projectId}/publishpackageinblocks/{blockNumber}.

Export Excel reports


ExportExcel creates and exports predefined reports in Excel format. This was created in the Reporting Service, and generates three reports:
Predefined Projects, Predefined Tasks and Predefined TMLeverage.
The new endpoint uses the following format: GET server/api/reports/exportExcel?OrganizationPath={organizationPath}&ShowAll=
{true/false}&publishStart={publishStartDate}&publishEnd={publishEndDate}&dueStart={dueStartDate}&dueEnd=
{dueEndDate}&status={status}

Changes in Verification Service health response structure


The JSON response structure of the Verification Service health endpoint {server}:41262/api/verification/health now extracts the "details" array
of the dependent services as properties.

SPN required for Windows authentication


Setting up SPN (Service Principal Name) on the GroupShare server is now mandatory when using Windows authentication from Trados Studio.
The is a result of the migration from WCF endpoints to REST API.
For information on configuring SPN, see HTTPS://GATEWAY.SDL.html.
Parent topic: API changes for third-party developers
Installing the Trados License Manager
Install Trados License Manager to configure and manage the network licenses for Trados GroupShare. Trados License Manager is based on
third-party licensing technology from SafeNet. It uses the TCP/IP protocol for dispensing licensing seats across the network.

Before you begin


Make sure you complete all prerequisites for installing Trados License Manager.

About this task


Trados License Manager installer adds the following utilities to your computer:
Locking Utility (Wechoid). This SafeNet utility generates locking codes for activating network licenses on the servers with no Internet
connection.
SafeNet License Manager (WlmAdmin). This SafeNet utility monitors all licensing activity and controls the distribution of license seats to
clients.
Trados License Manager. This is the utility used to activate Trados GroupShare online.
The default location for storing the installed Trados License Manager, as well as the imported license files and preferences is:
32-bit computers: C:\Program Files\Common Files\Trados\Thales
64-bit computers: C:\Program Files (x86)\Common Files\Trados\Thales

Procedure
1. Download the Trados License Manager installer from the Downloads section of My Account.
2. Execute the installer on the computer that you want to act as the license server.
3. Follow the installation steps.
4. If you need to change the default port number, open the SafeNet License Manager application (WlmAdmin.exe) and go to Edit >
Preferences > Server Port.
Setting up IPv6 connection for Trados License Manager
Setup the environment to allow for IPv6 connection.
Parent topic: Activating the Trados License Manager (administrators)
Known issues
This page contains a list of known issues related to Trados GroupShare 2020 SR1 CU7.
Online Deactivation may fail for specific licenses with the message "null". If this occurs, perform an offline deactivation for this license and/or
contact licensing support. (LTGS-10477)
GroupShare does not have logic for counting Chinese/Japanese characters. Projects that have Asian source languages will have 0 words in
the Analyze Files Report. We added a workaround in the code in order for mid-project update operations not to fail for such projects, as
the missing Words property was causing problems for Add/Update Project Files. The words count will still be 0 in the Analyze Files Report
after mid-project update operations for projects that had 0 words count from project creation, but the background tasks should be
successful. (LTGS-10581)
'Numbers' verification settings are now respected when verifying a document in Online Editor. However, customized language processing
rules are not taken into account (date, time and measurement format) and some date and measurement formats are not recognized correctly.
(LTGS-6398)
Translate and Analyze batch task ("Prepare with Groupshare") is not working when creating a server-based TM with Trados Studio White
Rabbit 2022 and the project is not published. The issue is fixed in Trados Studio 2022 CU01. (LTGS-10497)
Perfect Match(PM) is not applied when adding a new ZIP archive with PM folder structure. The new files will be added but the PM files
from folder structure will not be applied. (LTGS-10606)

Segment verification in the Online Editor fails on Spanish and German Windows
locales
If you are using the Online Editor with Spanish or German Windows locales, segment verification is not yet working correctly. To correct the issue,
follow these steps:
Workaround A:
1. Install English-US display language in Windows.
2. Set service user UI language, e.g. via PS command Set-WinUILanguageOverride en-US (executed as service user).
3. Log out and in to Windows as service user and restart services.
Workaround B:
1. Stop Verification service (V-S).
2. Go to V-S installation folder.
3. Remove the folder(s) corresponding to the OS' (service user) local (e.g., delete de and de-DE on German machine, it may be possible to
do this more targeted).
4. Start V-S. (LTGS-10513)
Languages no longer supported
The following languages have been removed because they are not and were not supported for TM creation:
az-Cyrl
az-Latn
bs-Cyrl
bs-Latn
chr-Cher
dsb
ff-Latn
ha-Latn
iu-Cans
iu-Latn
jv-Java
jv-Latn
ks-Deva
ku-Arab
pa-Arab
sd-Deva
shi-Tfng
sma
smj
smn
sms
sn-Latn
sr-Cyrl
sr-Cyrl-CS
sr-Latn
sr-Latn-CS
tg-Cyrl
tzm-Arab
tzm-Latn
tzm-Tfng
uz-Arab
uz-Cyrl
uz-Latn
The following languages that are listed in Supported languages are not supported on Windows Server 2012 R2:
1. ce-RU
2. cu-RU
3. en-AT
4. en-BI
5. en-CH
6. en-CY
7. en-DE
8. en-DK
9. en-FI
10. en-IL
11. en-NL
12. en-SE
13. en-SI
14. fo-DK
15. ko-KP
16. ku-Arab-IR
17. la-0001
18. lrc-IQ
19. lrc-IR
20. mzn-IR
21. nus-SS
22. prg-001
Parent topic: Changes introduced in Trados GroupShare 2020 SR1 CU7
Segmentation process overview
Segmentation settings define how a translation memory (TM) or a project divides source text into segments.
Segmentation rules are defined in the Language Resources section of TM settings. You can also define the segmentation rules that Trados
GroupShare uses when there is no applicable TM: these rules are defined in a Language Resources template, whose location is specified under
project settings.

Segmentation rules
Segmentation rules are defined by the regular expressions that specify a segment.
Often a segment is identical to a sentence, in which case the regular expression specifies the text patterns that constitute a sentence.
In any one project, for the same language pair, you can use multiple main TMs with different segmentation rules.

Rules specifying exceptions


List of abbreviations. This contains a list of abbreviations that finish with a period (.), for example, etc. The period at the end of etc. does not
necessarily mark the end of a sentence, though it might do so, by chance.
List of ordinal followers. Like abbreviations, ordinal followers provide cases where a period does not necessarily mark the end of a segment: when
followed by some nouns, a set of digits followed by a period (for example 23.) signifies the ordinal (23rd), not the end of a sentence. For example
23. April, can mean 23rd April. The list of ordinal followers is the list of such nouns.

Example: A simple segmentation rule


\.+[\p{Pe}\p{Pf}\p{Po}"]*

This regular expression specifies a segment in a rather simplistic manner. It matches all characters up to a punctuation mark that closes the segment.
Close, final and other punctuation, are defined Unicode categories for the following codes:
\p{Pe}specifies close punctuation.
\p{Pf}specifies final quote punctuation.
\p{Po} specifies other punctuation.
For more information, see for example, UnicodeCategory Enumeration.
Parent topic: Segmentation rules
QA messages in the Verification panel
This topic lists the verification messages triggered when QA differences are identified after the automatic comparison of source segments and target
segments.

No. QA verification message Description Default error severity


Inconsistencies
1. DuplicatedWord The target segment contains repeated words. Warning
2. UneditedMatch The target segment contains fuzzy matches which have not Warning
been edited.
Length verification
3. LengthLimitationFixed The target segment exceeds the permitted character limit. Error
4. LengthLimitationContextLong The target segment of a given document structure element is Error
above the permitted character limit.
LengthLimitationContextShort The target segment of a given document structure element is Error
below the permitted character limit.
Numbers
5. NumberMissing The target segment does not contain a number which is present Error
in the source segment.
6. TimeMissing The target segment does not contain a time which is present in Error
the source segment.
7. DateMissing The target segment does not contain a date which is present in Error
the source segment.
8. MeasurementMissing The target segment does not contain a measurement which is Error
present in the source segment.
9. NumberExtra The target segment contains a number which is not present in Error
the source segment.
10. TimeExtra The target segment contains a time which is not present in the Error
source segment.
11. DateExtra The target segment contains a date which is not present in the Error
source segment.
12. MeasurementExtra The target segment contains a measurement which is not Error
present in the source segment.
Punctuation
13. PunctuationDifferences The target segment does not end with the same punctuation as Warning
the source segment.
14. SpanishPunctuation The target segment does not observe Spanish punctuation. Warning
15. PunctuationSpace The target segment contains a space before the punctuation Warning
character which ends the sentence.
16. PunctuationSpace_French The target segment does not observe French space Warning
punctuation. In French, there must be a space between the last
word in a sentence and certain punctuation marks such as
exclamation marks or question marks.
17. MultipleSpaces The target segment contains a sequence of spaces (at least Note
two).
18. MultipleDots The target segment contains a sequence of dots (at least two). Note
19. ExtraEndSpace The target segments contains an extra space at the end. Warning
20. InitialCaps The target segment does not contain an initial capital letter but Warning
the source target segment does.
21. GlobalCaps The target segment does not consist of capital letters, but the Warning
source target segment does.
No. QA verification message Description Default error severity
22. OpeningBracketMissing The target segment does not contain an opening bracket, but Warning
the source target segment does.
23. OpeningBracketExtra The target segment contains an extra opening bracket, but the Warning
source target segment does not.
24. ClosingBracketMissing The target segment does not contain a closing bracket, but the Warning
source target segment does.
25. ClosingBracketExtra The target segment contains an extra closing bracket, but the Warning
source target segment does not.
RegEx (Regular Expressions)
26. RegExReport This reports if both source segments and target segments Warning
match the RegEx patterns.
27. RegExReportSourceOnly This reports if the source segment matches the RegEx pattern. Warning
28. RegExReportTargetOnly This reports if the target segment matches the RegEx pattern. Warning
29. RegExDifferentCount This reports if both source and target segments match but with Warning
different count.
Segments to exclude
30. ReportAllNonExcluded These are the target segments which were not included in the Note
QA check because you configured the project settings to skip
one or more of the following: segments with a specific match
type, segments which are already confirmed, segments which
are exact matches, segments which are fuzzy matches,
segments with a specific context (segments from specific file
locations).
Segment verification
31. ReportUntranslatedSegment The target segment is not translated or is empty. Error
32. IdenticalSegment The target segment is identical to the source segment. Warning
33. ForbiddenChar The target segment contains a forbidden character. Error
34. SegmentLonger The target segment is longer than a given percentage. Note
35. SegmentShorter The target segment is shorter than a given percentage. Warning
Trademark check
36. TrademarkMissing The target segment does not contain the same trademark or Error
copyright symbols as the source segment.
37. TrademarkExtra The target segment contains extra trademark or copyright Error
symbols by comparison with the source segment.
Word lists
38. WordListCheck The target segment contains terms which are included in the Warning
incorrect list of terms.
Parent topic: Checking verification results
Revision color markup
When multiple users review files collaboratively, the system automatically assigns a color to individual users, so that they can differentiate their
comments from the ones introduced by other users.
When users open a file, the system randomly assigns colors to individual users. All revisions made by the same user are marked with the same
color.
Parent topic: Reviewing translated content
Workflow for shared projects started in Trados GroupShare
Project managers can manage shared projects and file assignments directly from the Trados GroupShare web interface.
Once a project is created in Trados GroupShare and users are assigned work tasks, you can:
Search for it in the Projects view.
Open the project tab, and consult the project planning board and statistics.
Move the project files on the Kanban-style board to mark their progress.
To complete a shared project started in Trados GroupShare:
1. Make sure that you are a member of the Project Manager role or that you are in a role which includes the permissions required for
managing file assignments.
2. Follow the workflow steps:
a. Step 1 - Choose one of the available methods:
Step 1a: Create projects from scratch
Step 1b: Create projects based on previous projects* (*This feature is available only on the basis of special contractual
agreement, at an extra cost.)
b. Step 2 - Plan work on assignments
c. Step 3 - Choose one of the available methods:
Complete assignments in Trados Studio
Complete assignments in Online Editor
d. Step 4 - Complete projects
Step 1a: Creating projects from scratch
When you create projects from the Trados GroupShare web interface, you create a storage for all the files that need to be translated. At this
stage, you also decide which organization is in charge of your project. You can either create projects from scratch or starting off from
previous projects.
Step 1b: Creating projects based on previous projects
When you create projects from the Trados GroupShare web interface, you create a storage for all the files that need to be translated. At this
stage, you also decide which organization is in charge of your project. This feature is available only on the basis of special contractual
agreement, at an extra cost.
Step 1c: Updating an existing project
Upload new translatable and reference files to existing projects. This is useful for situations when you receive updated project files from your
customer, or additional files that were missed from the initial drop.
Step 2: Planning work on assignments
To make it easy to manage a project during its lifetime, you should assign engineers, translators and reviewers to translation phases for each
project file. Each of the users will be notified when the file reaches the phase they are assigned to by email.
Step 3a: Completing assignments in Trados Studio
When project managers move project files to a phase in Trados GroupShare, the users who are assigned to that phase receive automatic
notification emails. The notification emails inform users of the tasks they must work on and of the due date. Another possibility is to perform
translation or review work in Online Editor.
Step 3b: Completing assignments in the Online Editor
When project managers move project files to a phase in Trados GroupShare, the users who are assigned to that phase receive automatic
notification emails. The notification emails inform users of the tasks they must work on and of the due date. The assigned users can start
working on their translation or review tasks in Online Editor. Another possibility is to work on your translations or reviews in Trados Studio.
Step 4: Completing projects
When users complete all the assignments, you can mark the projects as Complete. At this stage, all the project files are usually in the
Finalisation phase.
Parent topic: Working with projects
Related tasks
Creating projects
File translation and check-in
You can translate the files of an Trados GroupShare project in Trados Studio or Online Editor, depending on your license agreement. The check-
in process is influenced by these choices.
You can check-in files in three ways depending on where you started working on them:
If the shared file is checked out from Trados Studio, you can check it in from Trados Studio.
If the shared file is checked out from Trados GroupShare to Online Editor, you can check it in from Online Editor.
If the shared file is checked out from Trados GroupShare to Online Editor, you can force check in the file from Trados GroupShare only if
you assigned the following roles: Project Manager, Power User or Administrator.
If your files are checked out, you can revert the check out operation if you assigned the following roles: Project Manager, Power User or
Administrator. This option is particularly useful if you experience server or file conversion issues.
Translating and checking in files from Trados Studio
After you finish translating the shared files in Trados Studio, you must check them back in to Trados GroupShare from Trados Studio.
Translating and checking in files from Online Editor
After you finish translating the files in Online Editor or just want to save your changes, check in the files from Online Editor.
Translating and force check-in files from Trados GroupShare
When files are in translation, you can perform a force check-in on them, fromTrados GroupShare, if you are assigned one of the following
roles: Project Manager, Power User and Administrator.
Translating and undoing file check-out from Trados GroupShare
When files are in translation (therefore, checked out), you can revert the check out operation, from Trados GroupShare, if you are assigned
one of the following roles: Project Manager, Power User and Administrator.
Parent topic: Working with projects
Deleting custom fields
You can safely delete any custom field that no longer meets your requirements.

Procedure
1. Go to the Resources view.
2. In the Custom Fields tab, select the checkboxes corresponding to the custom fields you want to delete.
3. Select Delete.
4. In the confirmation message, select Yes.
Parent topic: Custom fields
Assigning roles to users
To give your users permissions and access to your projects and resources, you must assign them roles. Roles are helpful because they are like
labels users carry with them. Therefore, it is easy to group, filter or quickly retrieve all your translators or reviewers, for example.

Procedure
1. Go to the Users view and select the Permissions tab.
2. Select the user's home organization (the organization in which the user was created).
3. In the right-hand side pane, identify the role you want to assign to your user. If necessary, select .
4. Under the role of your choice, select the Grant [role name] permissions to... field.
5. In the list, select the user you want to assign the role to.
Remember: Roles assigned within an organization propagate to its subsidiaries.
Parent topic: User roles
Related concepts
User roles
User permissions
Standard roles
Editing custom fields
You can modify the details of custom fields when they no longer suit your needs.

Procedure
1. Go to the Resources view.
2. In the Custom Fields tab, select the checkboxes corresponding to the custom field you want to modify.
3. Select Edit.
4. In the Edit Custom Field dialog, make the necessary changes.
5. Select Finish.
Parent topic: Custom fields
You cannot access a resource although you have the permissions
Symptom (example)
You have edit permission for a translation memory but cannot edit that memory.
Probable cause
The nominal permission to access a resource is usually not enough: you usually need additional permissions. For example, to edit a resource
you always need the appropriate Read permission in addition to the Edit permission.
Ask your administrator to give you all the appropriate permissions.
Example: generic dependency
To Edit, Manage or Delete a resource you also need View permission.
Example: edit a TM
To edit a translation memory, you need the following permissions:
Edit Translation memory
View Translation memory
View Language resource
View fields

Symptom (example)
You cannot see or write server-based termbase data although your MultiTerm administrator has granted these access rights to your MultiTerm
role.
Probable cause
You are not using, or you do not have access to the required termbase object.
Solution
Make sure that you are using the Full Layout in MultiTerm Desktop or in MultiTerm Online, and that the input model you must use is at the
correct role access level in MultiTerm Administrator.
Parent topic: Problems and solutions
Updated MultiTerm Online classic layouts
This release includes a new version of our web-based terminology client MultiTerm Online. Starting this version, the five classic layouts for
MultiTerm have been re-built and can now also be used to edit in browser applications without support for executing Java applets.
We also fixed a Tomcat security vulnerability (CRQ-32118) and a display issue for True values when adding or editing Boolean values in the new
MultiTerm Online legacy layouts (CRQ-32038).
You can extract the new multiterm.war containing these two additional fixes after downloading and extracting it from the CU8 archive.
Parent topic: Changes introduced in Trados Groupshare 2020 SR1 CU8
Activating a network license with Trados License Manager
online
Using a key provided by the Licensing Team, you can activate the Trados License Manager to serve licenses of your purchased RWS products to
clients.

Procedure
1. Open Trados License Manager from the Windows Start menu.
2. Copy the product key provided to you by the Licensing team. You can find it in the Order Information email or your RWS ID.
3. Paste the key into the Activation Code field.
4. Choose the number of licenses you wish to activate with your product key. You can activate only a part of the licenses available on your
network license. This is useful in case you need to use some or all of the remaining licenses on another licensing server.
5. Select Activate.
If you select the View Details arrow, you will see your activated product in the list with its corresponding product key. The activations are
grouped together by products and editions in drop-down lists. For example, a drop-down list contains all activations for the Studio [year]
Professional Commuter licenses.
The activated licenses list contains details about the date and time of activation, the number of seats you used on a particular activation and
the number of remaining seats on your purchased license at the time of activation. You can also perform the installation on TDS (Terminal
Desktop Services), in which case both the client application and the licensing application will be installed on the same server. As a result,
Trados GroupShare can be activated using only commuter licenses.
Note: Single-user licenses and subscriptions cannot be used to run Trados GroupShare when the Terminal Desktop Services role is installed
on server operating systems.
You can activate remaining seats from the same product key at a later date.
In some cases, if you have activated a 30-day trial commuter license for an RWS product and wish to activate a full license, you must first
deactivate the trial license.

Results
The license server is now good to go - clients can connect to the license server using the server's name. Make sure you have the licensing
computer turned on when users request network license seats. Trados GroupShare 2015 or later commuter licenses can be installed on the same
License Server. Each Trados GroupShare version will check out the necessary license type when connecting to it.
Parent topic: Activating Trados License Manager online
Working with single-user and network licenses

The Activation Server


The Activation Server is the live server hosted by RWS, which manages the products and activation codes for Trados GroupShare.
The License Server
The License server is the computer where your administrator installs Trados License Manager. The computer is hosted on the customer site
and should be located in the same LAN where the client applications are installed.
Parent topic: Licensing
Working with project packages
As a project manager, you can hand off work to team members who do not have access to Trados GroupShare by exporting project files as
.SDLPPX packages.
After creating the package, you can send it by email, upload on an FTP server, or use any other method that you prefer to send it to the team
member who will work on the project files. Packages enable you to send all project information with the project files in a coherent structure.
Sending one package instead of multiple files or multiple emails enables you to keep translation work organized and increase your efficiency.
Your team members can work with Trados GroupShare packages offline, in one of the following workflows:
Upload project packages to Trados Studio, and translate or review files in the Editor view. This workflow is useful for team members who
cannot connect to a Trados GroupShare server from Trados Studio, or who do not have access to the internet.
Upload offline cloud packages to a third-party CAT tool that supports .SDLPPX packages.
You can work with two types of project packages in Trados GroupShare:

Project packages
These are the packages that you export from Trados GroupShare to send to your team members. A Trados GroupShare package is an .SDLPPX
compressed folder that contains:
The project settings.
The selected project files for translation or review. These are bilingual .SDLXLIFF files that contain the source and target segments with any
translation status: Not Translated, Draft or Translated.
Any reference files available for the Trados GroupShare project. Project reference files are included in the package only if you export all the
files in the project instead of selecting the files individually.
Any translation memories (TMs) available for the project. The TMs that go with the package only include the translation units (TUs) coming
from the confirmed segments in the project files. Any other TUs in the project TMs are excluded when Trados GroupShare generates the
package. This ensures that third-party translators and reviewers do not have access to additional TUs in your TMs. If you do want to send
the entire TMs and not only the relevant TUs, export the TMs separately, and email them along with the .SDLPPX package. To export a
TM, go to the Resources view > Translation Memories, select the TM and click Export > Translation Memory > [source - target language].

Return packages
A return package is an .SDLRPX compressed folder that team members create outside Trados GroupShare to send back completed work.
Return packages can only be created for files that were initially in an .SDLPPX project package.
.SDLRPX packages contain the translated or reviewed project files along with the project settings and resource included in the original package.

Exporting project packages


Prerequisites: Before exporting project packages, make sure that:
you are in a role that includes one of the following permissions: Check Out My Project Files or Check Out Any Project Files. To export
files from secure projects, you also need Secure Project File Download permission.
the files you want to include in the package are not checked out or finalized
the files you want to include in the package are in the same project phase
To create a project package for offline translation or review in Trados GroupShare:
1. Go to the Projects view, and click on the project for which you want to create a package.
2. Choose whether you want to include all the project files or only specific files:
To include all the files available in the project, click Available actions for all files > Export Project Package. This option also adds any
reference files available for the project.
To include only specific project files, select the files that you want to add, and click Available actions for all files > Export Project
Package for x project files.
Trados GroupShare notifies of the status package in theTrados GroupShare right-hand side of the screen. When the package is ready, you can
you can access it from your browser's Downloads location. By default this is: \Users\<username>\Downloads.
The language files selected for export are automatically checked out to mark them as exported. The files will be checked back in when you import
the files from the return package.
The TMs that go with the package only include the translation units (TUs) coming from the confirmed segments in the project files.
Package Due Date
When opening the package in Trados Studio, the package shows the earliest due date of any included assignment. If none of the included project
files specify a due date, the project's due date (if any), is displayed instead.
For information on working with packages in Trados Studio, see the following topics in the Trados Studio documentation:
"Opening project packages and return packages" topic
"Creating return packages" topic

Importing return packages


Prerequisite: Make sure that you are in a role that includes one of the following permissions: Check Out My Project Files or Check Out Any
Project Files.
When you receive completed work in an .SDLRPX package, you can import it into Trados GroupShare to update your project with the modified
files.
The project translation memories are not updated with the TUs available in the returned project files. This is because you may want to review the
translations before committing these TUs to your TMs. After reviewing the translations, you can add these TUs to the project TMs when you
finalize the project files.
To import a return package into Trados GroupShare:
1. Go to the Projects view, and open the project into which you want to import the return package.
2. Click Import Package and select your .SDLRPX package. Trados GroupShare notifies you when the project has been updated with the
files available in the return package. When the package is imported, the files contained in the return package are automatically checked in.
3. Open the project files in the Online Editor and check that the project files have been updated with the changes available in the return
package.

Background tasks
Prerequisites:
To view the import/export background tasks, make sure that you are in a role that includes the View Background Tasks permission.
To download the exported package from the background task item, make sure you are logged in as the user who started the package
export.
Trados GroupShare performs all project package exports and imports in the background. These actions are recorded and the export packages
are stored so that you can retrieve the generated packages at any time.
To check details on the import/export background tasks available for your account, go the Background Tasks view and search for the following
tasks:
Project Package Export
Project Package Import
Parent topic: Project management
Working with translation memories and terminology
Keeping previously translated content in translation memories and enforcing terminology are best practices for reusing content and reducing
translation costs.
Performing concordance searches in the translation memory
When you perform a concordance search, you search through a translation memory (TM) for words or fragments within translation units
(TUs).
Viewing differences between translation memory matches
In Online Editor, you can use the Alternative view to see the differences between source segments and their fuzzy matches from the
translation memory. These differences have to do with words or characters that are either included in source segments, but missing from
their matches or vice versa.
Consulting details for translation memory lookups
You can consult the details of a translation memory (TM) lookup in the Lookups panel: the content, the match percentage, the TM it is part
of, the fields, the person who added the translation unit (TU) and the time it was added.
Blurring or hiding unfiltered translations
If you start translating a segment and you want to see whether there are translations in the translation memory that start with the text you
entered, you can do so by blurring or hiding the translations that do not match that text.
Applying translations
You can apply the results retrieved from the TMs (translation memories) included in your project to the target segment. Context matches
and 100% matches are applied automatically to target segments when you select them.
Applying terminology
You can apply the existing terminology to translate segments in the current file consistently.
Using smart actions
Smart actions are actions designed to boost your productivity while updating target segment in Online Editor. These actions include inserting
tags, placeables, terms, or fragment matches.
Interpreting translation unit matches and penalties
When you perform translation memory (TM) lookups, the resulting translation units (TUs) are displayed in the Lookups panel together with
details such as: match percentage, fields, the person who added the TU to the TM, the date when the TU was added. The match
percentage is influenced by the penalty values specified in the main application using Online Editor.
Updating existing translation units
While translating, you may find that some translation units (TUs) in your translation memory (TM) contain mistakes. In such cases, you can
update the existing TUs in the TM.
Adding translation units
If you confirm a segment, you can add it as a new translation unit (TU) in your TM.
Parent topic: Translating content
Custom Properties Service API
The GET /api/properties-service/info API call now returns the ServiceVersion property instead of serviceVersion. This helps prevent some issues
related to word capitalization when using the search function, for example.
Parent topic: Changes introduced in Trados GroupShare 2020 SR1 CU6
Language Pairs
A language pair consists of a source language and a target language. A language pair has direction: English to French is not the same as French to
English.

Specifying language pairs for a translation memory (TM)


A translation memory (TM) can have an indefinite number of language pairs. In Trados GroupShare projects, you specify the language pairs (and
their language resource settings) separately for each TM, under TM settings.

Language pair settings for a project


The language pair settings for each project specify the TMs and the termbases used in a project and are the link between the project and the
project's TMs, termbases, and automated translation settings.
Under language resources, you can also specify the language pair settings that Trados GroupShare projects use where there is no TM.
Parent topic: Translation memories (TMs)
Navigation themes
Navigation themes are a series of accessibility options developed in accordance with the Web Content Accessibility Guidelines (WCAG)
standard. There are three navigation themes available on the Online Editor user interface: Light, Warm, and Dark. You can find them on the View
tab, in the Theme group.
The Light theme is the one displayed by default.

The Warm theme includes warmer colors for the workspace and darker colors for the elements on the ribbon.

The Dark theme includes darker colors for both the workspace and the elements on the ribbon.

Parent topic: Navigating the Online Editor user interface


Activating the Trados License Manager (administrators)
As administrator, you can set up a network license server, activate it either online or offline, and use it to serve requests for Trados GroupShare
licenses from network clients.

Activation types
There are two ways you can set up a licensing network environment:
Online network licensing - The administrator activates the network license server online. The pre-authorized network license server is then
used to validate license requests from clients. The network license server requires an Internet connection during the activation process.
Offline network licensing - The administrator activates the network license server offline with the help of a locking code. The pre-authorized
network license server is then used to validate license request from clients. The network license server does not require Internet access.
Prerequisites for installing the Trados License Manager
Before installing Trados License Manager, make sure that the computer used as the license server fulfills the requirements below.
Installing the Trados License Manager
Install Trados License Manager to configure and manage the network licenses for Trados GroupShare. Trados License Manager is based
on third-party licensing technology from SafeNet. It uses the TCP/IP protocol for dispensing licensing seats across the network.
Activating Trados License Manager online
Find out how to activate and remove a network license on a server with Internet access.
Activating Trados License Manager offline
Find out how to activate a network license server using a locking code and without connecting the server to the Internet.
Monitoring clients and license information
As a network-licensing administrator, you can use the SafeNet License Manager (WlmAdmin.exe) to monitor Trados GroupShare licenses
and the clients who are using the license seats.
Configuring available product editions
As a network-licensing administrator, you can configure what product editions are available to a client user when they try to connect to the
license server. The information in this topic is relevant to you if you have multiple commuter licenses activated on the same license.
Product editions and features
This topic contains the available product editions and product features that a network-licensing administrator can configure for Trados
GroupShare.
Parent topic: Network licenses
Studio GroupShare variable values
These are the variables values for variables used in the legal notice:
2000
2023
Trados GroupShare
Trados GroupShare
Acknowledgments
https://gateway.sdl.com/
Deleting containers
You can delete containers, but this means that you will no longer have access to the TMs they host.

Procedure
1. Go to the System Configuration view.
2. In the Containers tab, select the checkbox corresponding to the container you want to delete.
3. Select Delete.
4. In the confirmation message, select Delete.
Parent topic: Containers
Translating and checking in files from Online Editor
After you finish translating the files in Online Editor or just want to save your changes, check in the files from Online Editor.

Procedure
1. Do one of the following:
Click the file-name link in the notification email to open your Trados GroupShare assigned files in Online Editor.
Log in to Trados GroupShare, go to Dashboard, and, under Your Tasks, select near the assignment you want to work on.
Log in to Trados GroupShare, go to Projects, select the project where the assignment is stored, select the checkbox next to the file
you want to work on, and then select Open in Editor.
Important: You cannot check out from Online Editor files which are already checked out in Trados Studio. Wait until the file is checked in
from Trados Studio before you check-it out (open it) in Online Editor.
The file automatically opens in Online Editor and is ready for editing.
2. Edit the file in Online Editor.
3. When finished, on the right-hand side corner of the toolbar, select Check-in file.
Important: You can use the Force check-in button if you are assigned one of the following roles: Project Manager, Power User or
Administrator. The Force check-in option is available from Trados GroupShare, when you open the project and select the file which is
checked out in Online Editor.
4. In the Check In dialog, do one of the following:
If you are the only or last user to edit the file, enter a comment and, under Change Phase to, select the next phase the file advances
to. If you still have work to do, do not change the file phase. Select Check-in. All your changes are now saved.
If there are still other people working on the same file as you, enter a comment, if necessary. You cannot change the file phase at this
point. The last user who checks in their changes can change the file phase. All your changes are now saved.
Parent topic: File translation and check-in
Auto-propagation in Online Editor
Auto-propagation is the process whereby the confirmed translation of a segment is applied to all the segments having the same source content.
Parent topic: Confirming translated segments
Copying content in target segments
If copying content to and from source segments is disabled, you can still copy external content to target segments.
Parent topic: Translating content
Translating and force check-in files from Trados GroupShare
When files are in translation, you can perform a force check-in on them, fromTrados GroupShare, if you are assigned one of the following roles:
Project Manager, Power User and Administrator.

About this task


The force check-in operation disconnects the persons who are currently translating the files in Online Editor and preserves the latest changes
performed on the file in Online Editor. This option is particularly useful if translators/reviewers finish their work but forget to check-in their changes.

Procedure
1. Translators do one of the following:
Click the file-name link in the notification email to open their Trados GroupShare assigned files in Online Editor.
Log in to Trados GroupShare, go to Dashboard, and, under Your Tasks, select near the assignment translators want to work on.
Log in to Trados GroupShare, go to Projects, select the project where the assignment is stored, select the checkbox next to the file
translators want to work on, and then select Open in Editor.
Important: Translators cannot check out from Online Editor files which are already checked out in Trados Studio. Wait until the file is
checked in from Trados Studio before you check-it out (open it) in Online Editor.
The file automatically opens in Online Editor and is ready for editing.
2. Translators edit the file in Online Editor.
3. Project Managers, Power Users and Administrators can force check in the files which are checked out in Online Editor by translators or
reviewers. In Trados GroupShare, go to the Projects view, open the project where the file is located, select the file you want to force check
in, and then select Force check-in.
Parent topic: File translation and check-in
TM import options
TM import options determine how TUs are imported.
You can access the TM import options Trados GroupShare imports TUs as a background task.
When updating server-based TMs with new TUs via import operations, the new TUs will be available for lookup, but the TU count will be
updated after 60 minutes.

General Options page


Option Description
Import File
Import only *.tmx files.

Language Direction
Choose the language pair for the TUs.

Options Description
Import translation units as plain text
Select this option to remove formatting tags on import. Fields are not affected.

Export invalid translation units


Select this option to write, to a .tmx file, the TUs that are marked not valid. The meaning of
not valid depends on other options that you set, for example:
The TU is written in an excluded language variant.
The TU contains unknown fields.

Recompute Fuzzy Index Statistics


Select this option to remove the 1000 most frequent words from the fuzzy indexes.
Words that occur very frequently TUs are not useful for fuzzy indexes. Typically, these are
words like a, the, to.
Recomputing can make a difference in performance for large TMs. If the TM has less than
50,000 TUs, it will not make a noticeable difference.

If target segments differ Description


Add new translation units
Import the new TUs as an addition to the existing ones.

Overwrite existing translation units


Import the new TUs and overwrite the existing TUs in the TM.

Leave existing translation units unchanged


Keep the existing TUs and do not import the new ones.

Keep most recent translation units


Keep the most recently changed TUs. Trados Studio imports a TU whose source segment is
identical to that of an existing TU only if the imported TU is newer than the existing one. If the
change date of the imported TU is older than the change date of the existing one, Trados
Studio does not replace the existing TU.

Advanced Options page


Option Description
Option Description
Unknown fields
These options determine how Trados GroupShare treats TUs with unknown fields.
Add to translation memory. The field is made available to all TUs in the TM. This
option is not available when you use a field template.
Ignore. The TU is imported, but the field is ignored.
Skip translation unit. The TU is not imported.
Fail translation unit import. The TU is not imported and it is counted as an error.

Only import segments with the following confirmation Filter by segment translation status (confirmation level) which translation units to import
levels into the TM.
Parent topic: Importing TUs to server-based TMs
Assigning user access to resources
Depending on their assigned roles in an organization, users can have permissions over organization resources. To have access to organization
resources, users must be assigned a role that includes access permission to resources. Several options are available.
Parent topic: User permissions

Create a role having user access permissions


You can group user access permissions by creating a new role for this purpose.

Procedure
1. Go to the Users view and select the Permissions tab.
2. Select New Role to display the application-wide Add Roles window.
Tip: Alternatively, go to Edit Roles > Add New.
3. In the Add Role dialog, give the role a name and, in the Resources section, select the checkboxes corresponding to the resources you want
to give users access to.
4. Select Finish.

Add user access permissions to an existing role


You can add user access permissions by editing an existing role.

About this task

This is a drastic measure. Note that all users who are already assigned to this role will be affected by this change.

Procedure

1. Go to the Users view and select the Permissions tab.


2. Select Edit Roles and, from the drop-down menu, select the role you want to edit.
Tip: Alternatively, identify the role in the right-hand side pane and select .
3. In the Resources section, select the checkboxes corresponding to the resources you want to give users access to.
4. Select Finish.
Working with custom batch tasks in Trados GroupShare
During project creation, Trados GroupShare automatically runs the following sequence of default batch tasks to prepare the project files for
translation: Scan file type, Convert to translatable format, Split text into segments, Apply PerfectMatch files (where available), Pre-
translate files, Analyze files.
If you need to run additional batch tasks on your project files, Trados GroupShare 2020 SR1 CU3 and later enables you to install plug-ins for
custom batch tasks. To use an installed plug-in, specify its settings in a Trados GroupShare project template, which you can then apply to new
projects.
Starting with the 2020 SR1 CU3 release, GroupShare offers support for the SDL Batch Anonymizer plug-in. This is a plug-in created by SDL that
you can use to strip translated and pre-translated segments of any identifiable metadata. Future Trados GroupShare releases will enable
developers to install their own plug-ins for any other custom batch tasks.

Installing a plug-in
Install your custom batch task plugin on the server where Trados GroupShare is installed. The plug-in will be available for all the users in your
Trados GroupShare account.
On a Trados GroupShare CU3 server
1. Deploy the plug-in assemblies to the location where Trados GroupShare is installed. The default location is C:\Program Files
(x86)\SDL\SDL Server\Application.
2. Deploy the <PluginName>.plugin.resources and <PluginName>.plugin.xml where the Trados GroupShare plug-ins are installed.
The default location for plug-ins is: C:\Program Files (x86)\SDL\SDL Server\Application\Plugins.
3. Restart the Application Service and the Execution Service. Your custom batch task is now available in Trados GroupShare, and can be
added to project templates.
On a Trados GroupShare CU4 server (and later)
1. Deploy the plugin file to one of the following locations:
Users\[user who installed GroupShare]\AppData\Local\
Users\[user who installed GroupShare]\AppData\Roaming\SDL\SDL Trados GroupShare\Plugins\Packages
2. Restart the Application Service and the Execution Service.
3. Check that your custom batch task shows up under the ...\SDL\SDL Trados GroupShare\Plugins\Packages folder in the Local or
Roaming location where you deployed the plugin file for step 1.

Your custom batch task is now available in Trados GroupShare, and can be added to project templates.

List installed plug-ins


To retrieve the list of tasks available in Trados GroupShare and check that your plug-in has installed correctly, make the following API call:
http://<serv_name>/api/projectserver/v4/batchtasks.

Working with Batch Anonymizer


The Batch Anonymizer is a plug-in created by us that you can directly install on your Trados GroupShare server. This plug-in enables Trados
GroupShare to work with project templates that include settings for the Batch Anonymizer task.
The anonymization task can bulk-remove or replace information on:
users who worked on any already translated segments in the project files
translation resources that have been used for translating and pre-translating the segments in the project files
1. Install the Batch Anonymizer plug-in
Add the Batch Anonymizer to Trados GroupShare so that you can then upload project templates with Batch Anonymizer settings.
On a Trados GroupShare CU3 server
1. Extract the Batch Anonymizer.zip file.
2. Copy the Sdl.Community.SDLBatchAnonymize.dll file, and paste it to the folder where Trados GroupShare is installed. The default
installation path is C:\Program Files (x86)\SDL\SDL Server\Application.
3. Copy the Sdl.Community.SDLBatchAnonymize.plugin.resources file and the
Sdl.Community.SDLBatchAnonymize.plugin.xml file to the folder where the Trados GroupShare plug-ins are installed. The default
installation folder for plug-ins is C:\Program Files (x86)\SDL\SDL Server\Application\Plugins.
4. Restart the Execution Service and Application Service.
On a Trados GroupShare CU4 server (and later)
1. Deploy the Sdl.Community.SDLBatchAnonymize.sdlplugin file to one of the following locations:
Users\[user who installed GroupShare]\AppData\Local\SDL\SDL Trados GroupShare\Plugins\Packages
Users\[user who installed GroupShare]\AppData\Roaming\SDL\SDL Trados GroupShare\Plugins\Packages
2. Restart the Application Service and the Execution Service.
3. Check that the Anonymizer component files show up under ...\SDL\SDL Trados
GroupShare\Plugins\Unpacked\Sdl.Community.SDLBatchAnonymize in the Local or Roaming location where you deployed the
plugin file for step 1.
The Anonymizer batch task is now available in Trados GroupShare, and can be added to project templates.
2. Add the Batch Anonymizer task to a project template
Prerequisites: When creating a project template with Batch Anonymizer settings, make sure that:
You did not exclude the Pre-Translate task from your project template. This is a default batch task that Trados GroupShare requires for
running the Batch Anonymizer task.
The Batch Anonymizer is the last task in the batch sequence. Trados GroupShare runs batch tasks on your project files in the order
specified in the project template.
To create a project template with anonymization settings, use one of the following workflows:
Trados Studio workflow
Use this workflow if you have access to Trados Studio and you want to quickly generate a project template with anonymization settings.
1. Download and install the Batch Anonymizer plug-in for Trados Studio from the RWS AppStore.
2. Create a project in Trados Studio, then go to Project Settings > Language Pairs > All Language Pairs > Batch Processing > SDL Batch
Anonymizer and configure the following anonymization settings for the project:
Username: Created by, Last modified by, Comment author, Tracked changes.
Resource origins: Machine Translation Provider, Translation Memory Provider, Match Score.
3. Select Projects view > Home tab > Create project template to generate a template that includes the settings for the Batch Anonymizer task.
4. Specify a name and download location for the .SDLTPL project template file, then click Save.
Manual workflow
Use this workflow if you have an .SDLTPL project template file that you want to edit outside Trados Studio:
1. Open the .SDLTPL project template file in Notepad++ or other similar text editing tool.
2. Edit the settings in the BatchAnonymizerSettings group and save the .SDLTPL file.

3. Upload the project template to Trados GroupShare


To add a project template that contains the Batch Anonymizer task and settings:
1. Go to Resources > Project Templates > New Project Template.
2. On the General Settings page, click Browse in the From file template field, and upload the .SDLTPL file that includes your Batch
Anonymizer settings.
3. Specify the template settings for the other pages on the wizard, and click Finish. Trados GroupShare automatically checks if all the batch
tasks specified in the template are supported, and notifies you of any missing plug-ins.
4. Apply the project template to new, relevant projects
1. Go to Projects > New Project to create a new project.
2. On the General Settings page, check that you have specified the correct location, then select the template that includes the Batch
Anonymizer task.
3. Fill in the other project details in the New Project wizard, and click Finish.
During project creation, Trados GroupShare anonymizes any pre-translated and translated segments, based on the settings specified in the
template.
Parent topic: Working with projects
Setting up IPv6 connection for Trados License Manager
Setup the environment to allow for IPv6 connection.
Before you begin:
Make sure no license server is set in Trados Studio while setting up the IPv6 connection.
Make sure Trados Studio is not running while setting up the IPv6 connection.
To set up the IPv6 connection:
1. Right-click the Windows icon on the taskbar and select System.
2. In the Settings window, under Related Settings, click Advanced system settings.
3. On the Advanced tab, click Environment Variables.
4. If the LSTCPIPVER variable does not exist click New and in the Name field add "LSTCPIPVER" and set the value to 6. If it does exist
set the value to 6.
Note:
Connecting to a license server with IPv4 or IPv6 is mutually exclusive. While LSTCPIPVER = 6 is set, it is not possible for Studio to
connect to a license server via IPv4 and vice-versa.
To enable IPv4 again, set LSTCPIPVER = 4 or delete the environment variable.
Setting LSTCPIPVER = 6 has a system-wide effect, meaning that if there are other applications that use a Sentinel License Server (RWS
apps or 3rd party) it will force them to use IPv6 as well.
Parent topic: Installing the Trados License Manager
Creating roles
Roles are the sets of permissions users have within an organization. When you create a role, you create a new set of permissions that you can
assign to your users.

Procedure
1. Go to the Users view and select the Permissions tab.
2. Select New Role to display the application-wide Add Roles window.
Tip: Alternatively, go to Edit Roles > Add New.
3. In the Add Role dialog, give the role a name and select the checkboxes corresponding to the permissions you want the role to have.
Some permissions need other permissions to be useful. For example, to be useful, the Edit permission needs the corresponding View
permission. For more information, see Dependencies between permissions.
4. Select Finish.
Parent topic: User roles
Related concepts
Standard roles
Prerequisites for installing the Trados License Manager
Before installing Trados License Manager, make sure that the computer used as the license server fulfills the requirements below.

Requirements for network licensing


Make sure that:
The PC where Trados License Manager is installed is turned on during work hours and that it runs a Server Operating System (Server OS).
You do NOT change the computer name on the license server after installing Trados License Manager. This may prevent users from being
able to connect to the network license server. The client application can be activated via IPv4 or IPV6, hostname or FQDN. If the name of
the computer where the application is installed changes, this will affect only the clients which connected via hostname or FQDN.
Enable communication with the licensing server leaving port UDP 5093 open.
The requirements for the license server are:
Any standard specification Windows 32-bit or 64-bit workstation
Windows Server 2012 SR2 or a higher version of a server operating system (recommended). As a general rule, Trados GroupShare
supports the operating systems also officially supported by Microsoft.
Windows 8.1 or a higher version of a workstation operating system
The Trados License Manager can be run on virtual machines.
If you do not want users to know the real name of your server, you can configure an alias name for it. Clients will still be able to connect to the
server and activate Trados GroupShare using the alias name instead of the real hostname.

Client requirements
The client installation (workstations) that are requesting license seats from the server must be Windows-based.

Installation combinations and restrictions


If required, Trados License Manager can coexist on the same computer with the following products:
Trados GroupShare (TM Server, MultiTerm Server, Project Server)
Microsoft SQL Server
The client application (for example, Trados GroupShare or Passolo ) in this case use localhost as the licensing server name in the client
applications.

Uninstall previous version of Trados License Manager


You must uninstall Trados License Manager v1.0 and Trados License Manager v2.0 before installing Trados License Manager v3.0.
Parent topic: Activating the Trados License Manager (administrators)
Defining ordinal followers
You can define a list of ordinal followers for each source language of your TMs.

About this task


When you define a list of ordinal followers, you edit the language resource template used to create a TM.

Procedure
1. Go to the Resources view.
2. In the Language Resource Templates tab, select the checkbox corresponding to the template of choice.
3. Select Edit.
4. In the [language resource template name > language] dialog, select Ordinal Followers.
5. Type in ordinal followers or edit existing ones.
6. Select Finish.
Parent topic: Ordinal followers
Viewing users
You can consult the list of all the available users in an organization.

Procedure
1. Go to the Users view and select the Users tab.
2. Required: Select an organization. All the available users are displayed in the right-hand side pane.
Note: If you do not have sufficient permissions to see the name of a user, the system displays the user as Anonymous User or as Hidden
User.

Example: Viewing anonymous or hidden users


Let's assume you have Read permissions to an organization, but not Read access to a user who holds a role in that organization. The system
displays the holder of that role as Anonymous User or as Hidden User.
To see the user's name, you need View User permissions in the home organization that stores the user's details.
To see the user's name if they are assigned to work on the same files as you, you need View Other Users permission.
Parent topic: Users
Importing TUs to server-based TMs
You can import TUs into an existing TM in order to update it with relevant content.

About this task


After you start the import, Trados GroupShare performs the task in the background. Monitor the progress in the System Configuration view, in the
Background Tasks tab.
Compatible files
You can import TUs from the following types of files: *.tmx, *.sdltm, *.zip and *.tmx.gz.
When importing *.zip files, make sure that the archive only contains one *.tmx, *.sdltm or *.tmx.gz file. If your *.zip contains multiple TM files,
only the first TM will be uploaded to the server-based TM.

Procedure
1. Go to the Resources view.
2. In the Translation Memories tab, select the checkbox of the translation memory you want to import content into.
3. Select Import Into.
4. In the Import into [TM name] dialog, select General Options, and specify the relevant settings:
a. In the Import File area, select Browse to add the import file.
b. In the Language Direction area, select a language pair combination.
c. Under Options, select a checkbox corresponding to the way you want to import TUs.
d. Under If Target segments differ, choose an option to specify how you want Trados GroupShare to handle TU mismatches.
5. In the Import into [TM name] dialog, select Advanced Options, and specify the relevant settings:
a. Specify how you want Trados GroupShare to handle unknown fields.
b. Specify which TUs are imported depending on their status: Translated, Translation approved, Signed-off, Draft, Translation rejected
or Sign-off rejected.
Important: When updating server-based TMs with new TUs via import operations, the new TUs will be available for lookup, but the
TU count will be updated after 60 minutes.
6. Select Finish.
TM import options
TM import options determine how TUs are imported.
TU import statistics
When you import translation units (TUs) into a translation memory (TM), you can check the import result in the Translation Unit Import
dialog.
Parent topic: Translation memories (TMs)
New and improved Dashboard and reporting interface
This release features a new Dashboard and Reporting interface, which brings the following improvements:
Dashboard reports and charts sections are larger so your project data is displayed more clearly.
Added search capability in the Dashboard reports to filter Projects Due Soon and Tasks Due Soon.
Removed Add Panel and Reset Dashboard options, while keeping the option to change the position of the reports and keeping the custom
view when reopening the page.
Improved performance when loading the Dashboard and the predefined reports.
Improved security on reporting area.
Parent topic: Changes introduced in Trados Groupshare 2020 SR1 CU9
Fixed issues
This page contains an overview of the new features and fixed brought to Trados GroupShare 2020 SR1 with Cumulative Update 7.
Fixed security issue related to cross-site WebSocket hijacking, impacting Trados GroupShare Notification Service.
Cross-site WebSocket hijacking involves a cross-site request forgery (CSRF) vulnerability on a WebSocket handshake. An attacker can
create a malicious web page on their own domain which establishes a cross-site WebSocket connection to the vulnerable application.
To defend against the vulnerability a new setting was added to Notification Service configuration file, under ..\Notification
Service\appsettings.json. The setting under Host.AllowedOrigins is set by default to the external server address. It supports a list of
comma separated values. Requests to Notification Service are validated and if the origin is not in the list of AllowedOrigin the response
will be HTTP 403. (LTGS-9494)
Changes in certificate validation. When connecting to various translation providers Trados GroupShare will no longer accept invalid
certificates that can't be validated against a CA. This means that you won't be able to connect to translation providers that use expired or
invalid certificates. (LTGS-10030)
When adding or updating files for a project that has a missing analysis report (e.g. created from Studio), reports will be generated for the
add/update operation but the "Full report" will not be available. (LTGS-10577)
Fixed an issue where downloading/open files in Trados Studio and Trados GroupShare WebUI under list view would fail with the error
message "The 'UserId' property on 'LanguageFileVersionComplex' could not be set to a 'null' value. You must set this property to a
non-null value of type 'Guid'." This occurred after deleting an user. (CRQ-27459)
Fixed an issue where GroupShare files in the TEMP folder never got removed. The work folder that each batch task creates in TEMP is
now cleaned up and creation of files and folders was made more robust. (CRQ-19617)
Trados GroupShare now supports certificates using SHA-256. (CRQ-19412)
Fixed an issue where email notifications were not sent to the external users when moving from Translation phase to Review phase. (CRQ-
28130)
Notification Service no longer allows HTTP origins for connections if HTTPS has been set up. (CRQ-29128)
Fixed an issue where Target language Processing Rules and Resources could not be customized for server-based TMs. (CRQ-23092)
Fixed an issue where logging in back to MTO took longer comparing to GS 2015 CU4. (CRQ-15079)
Fixed an issue where Trados GroupShare created file-based project TMs and Trados Studio then displayed the error: "The translation
memory 'proj tm.sdltm' could not be found. Click OK to specify its location, or Cancel to disable this translation memory." Project file-
based TMs are no longer created on the GS server in FileStore. (CRQ-26186)
Fixed an issue where populating Project Translation Memories would fail in Trados GroupShare if Custom Segmentation Rules were
applied to TM instead of via Language Processing Rules Templates with the error: "BatchProcessing.Implementation | Error | Message: One
or more errors occurred." The TMs can now be reliably created. (CRQ-26391)
Fixed an issue where TM Custom language processing rules were reset to default when adding a new language pair. (CRQ-25343)
When adding or creating server TMs via Trados GroupShare webUI only supported cultures of Serbian are now displayed. (CRQ-26083)
Fixed an issue where Application Service consumed over 90% CPU and caused the server to become unresponsive. (CRQ-28157)
Fixed an issue where pre-translate would fail for Chinese when creating new projects via GroupShare webUI. (CRQ-29543)
Fixed an issue that corrupted TMs if the Save button was pressed while the Re-Index task was running. If this issue still occurs in your
environment, make sure that you have downloaded the latest 2020 SR1 CU7 build from your OOS account. (CRQ-30854)
Parent topic: Changes introduced in Trados GroupShare 2020 SR1 CU7
Changing the external server address
When users create and edit file assignments in SDL Trados Studio 2015 and later, SDL GroupShare 2015 and later sends out email notifications
to the users assigned to work on the project files. These notifications emails include the project server hyperlink address that enables users to
access the Online Editor and open assignment files directly from the notification email.

Procedure
1. In the Trados GroupShare Console navigation tree, select Trados GroupShare > Settings.
2. In the Settings pane, under Project Server Settings, type in an External Server Address.
3. In the Actions pane, select Apply Changes to save the change.
Parent topic: Trados GroupShare Console settings

Enabling access to the Online Editor via custom URLs


Due to enhanced security policies, the default Trados GroupShare configuration allows you to access the Online Editor only via the link set up as
External Server Address. For convenience, we recommend that you use this URL to access the Online Editor. However, you can enable access to
the Online Editor via custom URLs.

About this task


To configure custom URLs for access to the Online Editor, you need to update the CorsAllowedOrigins configuration in the
Sdl.EditorService.Host.exe.config file , located by default in C:\Program Files\SDL\SDL Server\Editor Service.

Procedure
1. Add a comma separated list of all the origins you use to access the Online Editor or the Trados GroupShare website. An origin is the
scheme (protocol), hostname (domain) and port of the URL(s) that you use to access the Online Editor or the Trados GroupShare
website. You can also optionally add the value that you set up as the External Server Address.
Examples:
<add key="CorsAllowedOrigins" value= "https://origin1.com,https://origin2.com" />
<add key="CorsAllowedOrigins" value= "http://groupshare.company.corp,https://groupshare" />
<add key="CorsAllowedOrigins" value= "http://origin2:81" />
While not recommended due to security considerations, you can also allow all origins by removing <add key="CorsAllowedOrigins"
value= "" /> from the same configuration file.
2. Restart the Editor Service after applying the changes.
Navigating the Online Editor user interface
The Online Editor user interface consists of multiple elements designed to help you focus on your work and make each interaction meaningful.
These elements include tabs, groups, the ribbon, the workspace, and the status bar, as shown in the following image:

The number of words displayed in the status bar is the total number of words in the source text. On the other hand, the number of characters refers
to the total number of characters in the segment that you are currently editing; this can be the source segment or the target segment. If you select
only a part of the source or the target segment, the number of characters in the selected text is displayed.

The Online Editor interface is context-sensitive. Therefore, when you resize the page, its elements are adjusted automatically to the new height and
width. If the buttons on the ribbon do not fit on the entire width of the page, only part of them are displayed and you can access the rest by
selecting .

Modifying the layout of the workspace


The way segments are displayed during translation helps you focus on your task differently. In Online Editor, you can choose between two
layout options: vertical (the source and target segments are displayed in two columns, one next to the other) or horizontal (each target
segment is displayed under its corresponding source segment).
Detaching the side panel
Detaching the side panel in Online Editor means opening it in a different window. This can be particularly useful if you are working with two
monitors, because it makes the translation area larger and it separates the actual translation of content from other operations, such as
working with revisions, lookups, or comments.
Viewing navigation information about a file
Navigation information consists in the name and path of the file, as well as in details about whether the segment you are working on is part of
a header, a footer, or a paragraph, for example.
Viewing information about the structure of a file
This information indicates where each segment is located in the structure of the source file; for example, in a paragraph or in a header or
footer.
Consulting cloud project details
If you have a file open in the browser, you can easily check what project it belongs to and what its location is. This is particularly useful
when you work on multiple files at the same time.
Details about segments and translations
These details consist in: the current status of the translation, information about whether each segment is locked or not, as well as the
percentage of the translation memory match applied to the translation.
Adapting the contrast of colored text
If the file you are working on contains text formatted with very light colors, you can change the way in which it is displayed without affecting
its formatting in the output.
Making text larger or smaller
Adjust the size of the text in the Online Editor workspace by making it larger or smaller. You can do this either temporarily, by zooming in
or out, or permanently, by configuring a minimum and a maximum font size. In either case, the adjustments only have to do with the way the
text is displayed in Online Editor. They do not affect the size of the text in the output.
Navigation themes
Navigation themes are a series of accessibility options developed in accordance with the Web Content Accessibility Guidelines (WCAG)
standard. There are three navigation themes available on the Online Editor user interface: Light, Warm, and Dark. You can find them on the
View tab, in the Theme group.
Navigating between segments
You can navigate between segments either one by one (forwards or backwards) or by going directly to specific segments, according to their
number.
Cutting, copying, and pasting text
You can select fragments of text and copy them somewhere else in the file or move them there altogether.
Support for right-to-left scripts
If you select a display language that uses a right-to-left script (for example, Arabic) before opening a file in Online Editor, the options on the
Online Editor user interface will be displayed in that language from right to left.
Parent topic: Working with Online Editor
Editing field templates
You can modify field templates any time. Any changes you make to your field template impact the way your TM works.

Procedure
1. Go to the Resources view.
2. In the Field Templates tab, select the checkbox corresponding to the field template you want to edit.
3. Select Edit.
4. In the [field template name] dialog, make any necessary change.
5. Select Finish.
Parent topic: Fields
Step 3: Creating server-based TM
You create server-based translation memories (TMs) to ensure translations are performed consistently, sharing the same language resource.
Server-based TMs are repositories which store the translation units (TUs) that your organization's users work on over the course of time.

Procedure
1. Go to the Resources view.
2. In the Translation Memories tab, select New Translation Memory.
3. On the General Settings page:
a. Type the TM details.
b. Choose a location for your TM.
4. Select Next.
5. On the Language Pairs page, select source and target languages for your language pair(s).
6. Select Next.
7. On the Fields page, perform one of the following actions:
Select a field template. The field columns are automatically updated with the template content.
Configure the field columns.
Leave the fields blank.
8. Select Next.
9. On the Language Resources page select a language resource template or configure each language resource.
If you select a field template, the field columns are automatically updated with the template content.
If you select , you can configure the fields accordingly. Select Finish.
10. Select Next.
11. On the Advanced Settings page, do one of the following:
If you selected a language resource template in the previous step, the Advanced Settings page is automatically populated with data
from the template and all checkbox options are disabled. You can consult these settings, but you cannot edit them.
If you did not select a language resource template in the previous step, select the checkboxes corresponding to your TM's recognized
tokens and multiple-part tokens (considered as one element).
12. Select Finish.
Parent topic: Configuring server-based TMs
Related concepts
Translation memory advanced settings
Making text larger or smaller
Adjust the size of the text in the Online Editor workspace by making it larger or smaller. You can do this either temporarily, by zooming in or out,
or permanently, by configuring a minimum and a maximum font size. In either case, the adjustments only have to do with the way the text is
displayed in Online Editor. They do not affect the size of the text in the output.

Procedure
1. Open the appropriate file in Online Editor.
2. On the View tab, do one of the following:
To zoom in or out, select Enable Text Zoom, and then select Smaller or Larger as many times as necessary.
Tip: After zooming in or out, you can go back to default text size by selecting Enable Text Zoom again.
To configure a minimum and a maximum font size for segments, select Options, and then, under Font Adaptation, specify a minimum
and a maximum value. Select the Adapt font sizes checkbox for the settings to be applied immediately after saving, and then select
Save.
Note: When you configure a minimum and a maximum font size, any segment whose font size is smaller than the minimum value or
larger than the maximum value will be adapted to fit the values you configured. Segments whose font size falls in between the
minimum and the maximum values will not be affected.
Once you save your configuration, these values are linked to your account and will be applied every time you open a file in Online
Editor.
Parent topic: Navigating the Online Editor user interface
Increasing user access to resources
Depending on their assigned role in an organization, users can have a range of user access permissions to some or all organization resources.
Several options are available.
Parent topic: User permissions

Create a role with additional user access permissions to resources


If you want your users to have increased user access permissions, but you don't yet have a role that includes the permissions of your choice, create
a new role for this purpose and assign your users to the new role.

Procedure
1. Go to the Users view and select the Permissions tab.
2. Select New Role to display the application-wide Add Roles window.
Tip: Alternatively, go to Edit Roles > Add New.
3. In the Add Role dialog, give the role a name and select the checkboxes corresponding to the permissions of your choice.
Important: If you use Trados GroupShare Cloud, you cannot edit roles and permissions.

Add more user access permissions to an existing role


If your users already have a role which gives them some user access permissions, edit that role to add more permissions.

About this task


This is a drastic measure. Note that all users who are already assigned to this role will be affected by this change.

Procedure
1. Go to the Users view and select the Permissions tab.
2. Select Edit Roles and, from the drop-down menu, select the role you want to edit.
Tip: Alternatively, identify the role in the right-hand side pane and select .
3. In the Resources section, select the checkboxes corresponding to the resources you want to give users access permissions to.
4. Select Finish.

Add user to a more powerful role


If you want users to have increased user access permissions, and a role that fits your requirements already exists, assign your users to this role.

Procedure
1. Go to the Users view and select the Permissions tab.
2. Select the user's home organization (the organization in which the user was created).
3. In the right-hand side pane, identify the role you want to assign to your user. If necessary, select .
4. Under the role of your choice, select the Grant [role name] permissions to ... field.
5. In the list, select the user you want to assign the role to.
Note: Roles assigned within an organization propagate to its subsidiaries.
Conrefs for Licensing links
This topic contains all links in the Licensing help

External links
RWS Licensing Youtube playlist
MultiTerm Online security hotfix
Download this MultiTerm Online hotfix since it upgrades from Apache Log4j 1.2.13 to Apache Log4j 2.17.1. This newer version prevents some
security issues.
You can download the new version here: MultiTerm Online security hotfix.
Parent topic: Changes introduced in Trados GroupShare 2020 SR1 CU6
Customize password complexity rules
As an Trados GroupShare administrator, you can enforce password requirements for the user accounts on your server. This enables you to better
protect your users' accounts and meet your organization's compliance needs. Password requirements are enforced the next time that your existing
users change their passwords or when new accounts are created.

About this task


The default password complexity rule require users to set a password that includes at least one uppercase, one lowercase letter, and one digit.
To customize these password rules for increased security:

Procedure
1. Open the Trados GroupShare Console.
2. In the navigation pane, choose Trados GroupShare > Settings.
3. Scroll down to the Customize Password Complexity Rule section and specify the minimum number of required uppercase and lowercase
letters, digits and special characters, as well as the minimum password length. The minimum password length is determined by the total
number or characters required by all the password criteria set.
4. Click Finish to apply the changes and close the window.

Passwords for Windows accounts


The password complexity rules do not impact the accounts created using Windows credentials.
Parent topic: Trados GroupShare Console settings
Changing the account used by Trados GroupShare services
A Windows account is set up for each Trados GroupShare service during installation. To view or update the account settings after installation, use
the Trados GroupShare Console.

Procedure
1. In the Trados GroupShare Console navigation tree, select Services (Local).
2. Locate the required service in the Name column.
3. Double-click the service name (or right-click and select Properties) to display the dialog where you can view or update the account details.
4. Make the changes and select OK.
Parent topic: Trados GroupShare Console
Network licenses
Network licensing (or commuter licensing) provides the flexibility required in an enterprise environment to distribute a limited number of licenses
among a large number of clients.

How it works
To use a network license for Trados GroupShare, an authorized user contacts a licensing server and requests a license. The licensing server is set
up by an administrator who activates the network licenses here. The network administrator uses the licensing server to specify the number of
concurrent users which are allowed to request licenses.

What is required
Network licenses are available only while the license server is running. This is because the licensing server needs to monitor the number of
concurrent licenses. However, users do not need to remain connected to the licensing server after activating their network license. If they need to
work with Trados GroupShare offline, they can borrow a license from the licensing server. This enables them to use Trados GroupShare while
disconnected from the running licensing server. Borrowing a license removes the license from the license server and places it on the user's
computer.
Anyone on the network can activate Trados GroupShare with a network license. License borrowing is possible for a maximum 30-day interval.
Activating the Trados License Manager (administrators)
As administrator, you can set up a network license server, activate it either online or offline, and use it to serve requests for Trados
GroupShare licenses from network clients.
Connecting to the Trados License Manager (users)
You can activate Trados GroupShare by connecting to a license server they have access to. Users need to know that computer's short
name, the fully qualified address (less than 40 characters) or its IP address.
Parent topic: Licensing
Variables
A variable is a word or phrase that the translation memory (TM) recognizes in the source text. The TM copies the variable to the target text.
Because variables are identical between source and target text, they are useful for special terms such as product names.
If a source segment contains a variable, there are two scenarios:
The TM contains a translation unit (TU) that matches the source (though the variable might differ).
The TM does not contain a translation unit (TU) that matched the source text.

Scenario 1: The TM contains a matching TU


The TM contains a matching TU, but the variables in the text and the TU might differ.
The TM copies the target language text from the TU to the target of the translatable item, and substitutes the variable from the presented text in
place of the variable from the TU.
The match is 100%, minus any penalty for variable substitution as specified in Trados Studio, in the project settings under Penalties, Text
substitution.

Scenario 2: The TM does not contain a matching TU


If there is no match, the TM does not translate the segment. However, the TM recognizes the presence of the variable in the source, and adds an
annotation to the working text file. When you open the text, the editor displays the variable text as a recognized token.
Format of variables
Variables are recognized tokens and also a language resource.
Defining variables
You can define the list of variables translation memories (TMs) take into consideration. Each language pair can have a list of variables.
Enabling variables
You can configure Trados GroupShare to identify variables in the source text, so that they are found in the target text as such.
Parent topic: Recognized Tokens
Exporting abbreviations
You can reuse abbreviation lists across translation memories (TMs) by exporting and importing them in .txt format.

Procedure
1. Go to the Resources view.
2. In the Language Resource Templates tab, select the checkbox corresponding to the template of choice.
3. Select Edit.
4. In the [language resource template name] dialog, select Language Resources.
5. Identify the language for which you want to export existing abbreviations.
6. In the [language resource template name > language] dialog, select Abbreviations.
7. Select Export all.
8. Select Finish.
Parent topic: Abbreviations
Downloading server-based TMs
Once the TUs of a server-based TM are exported, you can download the export file at a later date.

Procedure
1. Go to the System Configuration view.
2. Go to the Background Tasks tab.
3. If necessary, set the filter to display tasks that have the Done status.
4. Select the checkbox corresponding to the export task you want to download.
5. Select View.
6. In the [export task name] dialog, select Download exported TM.
7. Save the exported file.
Parent topic: Translation memories (TMs)
Customer support
To contact Technical Support, connect to the Customer Support Web Portal at https://gateway.sdl.com/ and log a case for your RWS product.
You need an account to log a case. If you do not have an account, contact your company's RWS Support Account Administrator.
Parent topic: Welcome to the Trados GroupShare 2020 SR1 documentation
Filtering and exporting reports
For a more granular view of the translation work progress, you can filter reports by different criteria.

About this task


Procedure
1. In the Reporting tab of the web UI, expand the Filter sidebar.
2. Set the criteria you want to filter by:
Organization
Publishing date
Delivery date
Status
Source language
Target language
Assigned users
3. If you want to, you can export the filtered report as an Excel file by selecting Export as Excel.
An Excel file with the filtered data will be downloaded locally.
Parent topic: Global reports
Main TMs and project TMs
A GroupShare installation can have a number of Main TMs. For example, some installations have a TM for each subject matter area and a TM
for each of their customers.
When you start a project, you can also create a project TM. This includes the TUs from the main TMs that have some match with the source texts.
When the TMs have different fields, the project TM uses only fields that occur in all the main TMs. This always includes the GroupShare-
maintained fields.

View and change which TMs are used by a project


To view or change which TMs are used in your project, edit the project settings. These specify:
Which language resource template, or TM template to use.
The TM sequences to use.
The penalties associated with each of the main TMs.
Which main TMs can be updated with new translations.
What translation statuses are needed to update the project TM.
How TMs are used: the minimum values need for a match.
Parent topic: Translation memories (TMs)
Abbreviations
Abbreviations are standardized short strings that replace full words or expressions. Abbreviations must be marked appropriately in translation
memories (TMs), so that they can be differentiated from fully fledged words or expressions.
Defining abbreviations
You can define an abbreviation list for each source language of your TMs.
Exporting abbreviations
You can reuse abbreviation lists across translation memories (TMs) by exporting and importing them in .txt format.
Importing abbreviations
You can reuse abbreviation lists across translation memories (TMs) by importing and exporting them in .txt format.
Parent topic: TM language processing rules and recognized tokens
Deleting project templates
You can safely delete any project template that no longer meets your requirements.

Procedure
1. Go to the Resources view.
2. In the Project Templates tab, select the checkboxes corresponding to the project templates you want to delete.
3. Select Delete.
4. In the confirmation message, select YES.
Parent topic: Project templates
RWS product names as conrefs (for cross-product content)
RWS Language Cloud
Language Cloud
Trados Enterprise
Trados Studio
Trados GroupShare
Language Weaver Edge
Language Weaver
MultiTerm
MultiTrans
Managed Translation
RWS Translation Connector for Adobe Experience Manager
RWS Translation Connector for AEM
Translation Connectivity
TMS
WorldServer
Tridion Docs
Tridion Sites
Tridion Sites Cloud
DXA
UDP
Unified Delivery Platform
Content Porter
Experience Optimization
Translation Preview
Quality Assistant
Xopus
Knowledge Center
Media Manager
XPP
Passolo
Contenta
Contenta S1000D
LiveContent S1000D
TMS
WorldServer
XPP
Passolo
Contenta
Contenta S1000D
LiveContent S1000D
ETS
SDL Tridion Sites (full name of "Tridion Sites" before SDL was acquired by RWS)
SDL Web (old name keeps "SDL")
SDL Tridion (old Tridion product, keeps "SDL")
SDL Tridion Docs (full name of "Tridion Docs" before SDL was acquired by RWS)
SDL Knowledge Center (short form Knowledge Center)
SDL SmartTarget
MultiTerm Administrator
Activating Trados GroupShare
The Product Activation dialog is where you can perform all license related functions.
Here you can:
Activate and deactivate Trados GroupShare with a single-user or a subscription license.
Request to use a network license
Borrow a network license
View your license status
View your deactivation certificate
Modify the connection settings (specify a proxy server and test Internet connection)
You can also activate Trados GroupShare with a subscription license from the Cloud Sign In window, by clicking the Sign In button in the
upper corner of any view.

Display the Product Activation dialog


On the computer where Trados GroupShare is installed, select GroupShare Product Activation from the Start under the SDL Trados GroupShare
folder.

Activation process

Based on what your path is, follow the instructions in this section to activate your product.
Parent topic: Licensing
Organizations and resources
To ensure work consistency across the organizations and at project level, organizations create or store common resources for their users.
Users have access to the organization's resources depending on the permission associated to their role. Resources include:
Translation memories (TMs)
Termbases
Language resource templates
Field templates
Project templates
Parent topic: Organizations and their components
Upgraded components
Editor Service Rounter and BCM-S now run on .NET 6.
Following the upgrade to .NET 6, the configuration files for the two respective services, Sdl.EditorServiceRouter.Host.exe.config and
Sdl.BcmService.Host.exe.config, have been replaced by appsettings.json.
Parent topic: Changes introduced in Trados GroupShare 2020 SR1 CU7
Checking service status
You can check service status at any time to manage service operations according to your needs.

Procedure
1. In the Trados GroupShare Console navigation tree, select SDL Trados GroupShare > Services.
2. In the Services pane, consult the current status of the available services.
3. In the Actions pane, choose an action:
Select Refresh Service Status to check the current service status.
Select Restart Services to start services which are not currently running.
Select Stop Services to stop the services.
Available Trados GroupShare services
The current section enumerates the available Trados GroupShare services as they are featured in the Services pane of Trados GroupShare
Console.
Parent topic: Trados GroupShare Console settings
Activation certificate
You are prompted to enter an activation certificate when you activate your product and do not have an Internet connection on the computer where
Trados GroupShare is installed. An activation certificate incorporates all of the details which would normally be downloaded from the Activation
Server during an online activation.
Parent topic: Activating single-user licenses offline
Deleting servers
You can safely delete the servers you no longer want to host your server-based TMs.

Procedure
1. Go to the System Configuration view.
2. In the Servers tab, select the checkboxes corresponding to the servers you want to delete.
3. Select Delete.
4. In the confirmation message, select Yes.
Parent topic: Servers
Step 5: Advancing assignments to the next phase
Once the assigned users complete their translation or review work, they must check in the documents to the server and advance them to the next
project phase.

Before you begin


Make sure that the users which check in their assignments have the correct permissions to change file phases, namely Change Current Phase and
Change Any Phase. Assign users the appropriate roles or adjust the permissions associated to their roles before users reach this project step.

Procedure
1. In Trados Studio, go to the Projects view, double-click a project published on Trados GroupShare to open it.
2. In the Files view, select the file you want to check in.
3. On the Home tab, select Check in.
4. Expand Change Phase and select the next phase the document should go to.
Note: If there are users already assigned to work on the file in the new phase, Trados GroupShare sends these users a phase change
notification email and updates the information in the Current Phase column.
Parent topic: Workflow for shared projects started in Trados Studio
Related concepts
Standard roles and permissions
Dependencies between permissions
File assignment notifications
Translation statuses
Creating language resource templates
You can speed up the creation process of TMs that are similar or identical in the language resources they use. Language resource templates enable
you to work consistently across your TMs.

Procedure
1. Go to the Resources view.
2. In the Language Resource Templates tab, select New Language Resource Template.
3. In the Create Language Resource Template dialog, select General Properties.
4. On the General Properties page:
a. Type in a name and, optionally, a description for your language resource template.
b. Choose a location for the resource template in your organization.
5. Select Next.
6. On the Language Resources page:
a. Select a source language and click the page white space.
b. Select .
c. In the Create Language Resource Template > [source language name] dialog, select the Abbreviations page.
d. Type an abbreviation. Click anywhere on the white page and type more abbreviations.
e. Select Next.
f. On the Ordinal Followers page, type an ordinal follower. Click anywhere on the white page and type more ordinal followers.
g. Select Next.
h. On the Segmentation Rules page, choose either Paragraph based segmentation or Sentence based segmentation, and add or edit
segmentation rules.
i. Select Next.
j. On the Variables page, type a variable. Click anywhere on the white space and type more variables.
k. Select Finish.
7. In the Create Language Resource Template dialog, select Finish.
Parent topic: Language resource templates
Installing Trados GroupShare 2020 SR1
This topic contains some important notes on installing Trados GroupShare. Complete instructions for installing Trados GroupShare are available in
the dedicated Trados GroupShare Installation Guide PDF.
Ensure that you have administrator permissions and that no other software is running while you install Trados GroupShare.
You can find a full list of software installed with this application, including any third-party software in the Installation Guide.
Download location
You can download the Trados GroupShare installer from your RWS Account.
Installation instructions
To install Trados GroupShare, follow the instructions in the Installation Guide.
Installation issues
For information on resolving installation issues, see the Gateway Knowledge Center.
Parent topic: Installing Trados GroupShare
TU import statistics
When you import translation units (TUs) into a translation memory (TM), you can check the import result in the Translation Unit Import dialog.
The Translation Unit Import dialog contains information about scheduling and TU statistics:
Total or RawTU - This is the total number of TUs involved in the import.
Added - These TUs are added to the TM when no duplicate or errors are found in the TM.
Merged - TU context or TU fields (from the imported TUs) are added to the TM. This happens if the imported TU is a duplicate of an
existing TU and the imported one contains extra fields/information.
Errors - These TUs were not imported.
Overwritten - TU context or TU fields (from the imported TUs) replace the ones in the TM. This happens if the imported TU is a duplicate
of an existing TU.
Discarded - The imported TU was rejected or skipped (if it was explicitly filtered out). This happens:
If the imported TU contains attributes for fields that are not part of TM and Unknown fields is set to Skip
If the imported TU is a perfect duplicate (source and target) and there is nothing to merge
Bad - These TUs were not imported.
Parent topic: Importing TUs to server-based TMs
Using the Trados GroupShare Console
The instructions for using the Trados GroupShare are available in a separate Help resource.

About this task


To learn about using the Trados GroupShare, browse through the Trados GroupShare Console Help.
Trados GroupShare Console
With Trados GroupShare Console, an administrator can view and manage Trados GroupShare settings and services. It is available on any
Trados GroupShare machine that includes the Application Server role.
Managing termbase data on the host
All termbases, including MTMaster, are stored on the data host. The data host is accessed by MultiTerm Server, and MultiTerm Server in
turn is accessed by the users of the client applications on the network.
Trados GroupShare Console
With Trados GroupShare Console, an administrator can view and manage Trados GroupShare settings and services. It is available on any Trados
GroupShare machine that includes the Application Server role.
Trados GroupShare Console features
Trados GroupShare Console enables administrators to manage the Trados GroupShare settings and services.
Opening Trados GroupShare Console
To manage the Trados GroupShare settings, you must first open Trados GroupShare Console.
Trados GroupShare Console settings
The SDL Trados GroupShare branch of the navigation tree gives you access to the GroupShare settings, databases and services.
Activating licensing
Trados GroupShare is licensed using a single-user license. A single-user license can have several 'seats' that can be used within that one
license.
Services (Local)
Services are all located under the Services (Local) branch.
Changing the account used by Trados GroupShare services
A Windows account is set up for each Trados GroupShare service during installation. To view or update the account settings after
installation, use the Trados GroupShare Console.
Parent topic: Using the Trados GroupShare Console
Deleting resources
You cannot delete resources by removing their links. When you delete resources, their links are also deleted.

Procedure
1. Go to the Resources view.
2. Go to the tab where your resource is located: Translation Memories, Language Resource Templates, Field Templates or Project Templates.
3. Select the checkbox corresponding to the resource you want to delete.
4. Select Delete.
Parent topic: Resource Links
Resource Links
Each resource belongs to just one organization, but you can link the resources in one organization to any number of other organizations. Access to
the resource via the link is determined by the permissions users have.

Example: Permissions to a resource link in the subsidiary


A TM is created in organization 'America'. You create a link to that TM in organization 'Europe'. All permissions that users have in organization
'Europe' apply to that TM.
Adding resource links
Resource links allow users from other organizations to access the resource in your organization. The resources you can link to and from
include: translation memories (TMs), servers and containers.
Removing resource links
When you want to deny users from other organizations access to your resource, you must remove the resource link.
Deleting resources
You cannot delete resources by removing their links. When you delete resources, their links are also deleted.
Parent topic: Working with users, roles and permissions
Trados GroupShare Console features
Trados GroupShare Console enables administrators to manage the Trados GroupShare settings and services.
Through the console, you can:
Access the Product Activation tool for licensing
Specify the language that you want MultiTerm server messages to be written in
Update details of the account used for database authentication
Manage services on the local machine
Specify the amount of threads used by Trados GroupShare background tasks
Specify TM account used for TM interaction in server-based project creation
Enable and disable dynamic resource access and define the default role to be used
Specify archiving location and timing
Rename Trados GroupShare phase names
Specify e-mail notification settings
Customize the password complexity requirements for the accounts on your Trados GroupShare server
The console is installed with Trados GroupShare, on the same computer.

Trados GroupShare Console layout


Trados GroupShare Console includes:
The Navigation pane (on the left), displaying the navigation tree where you can select a branch to display the related settings.
The Settings pane (the middle of the page), displaying the settings appropriate to the branch you selected in the navigation tree. You can edit
the settings here.
The Actions pane (on the right), displaying the actions appropriate to the currently displayed settings. For example, if you edit the settings,
you must select Apply Changes in the Actions pane to save the changes.
Parent topic: Trados GroupShare Console
Mid-project updates
Update current project with new source and reference files without disrupting current work.
Trados GroupShare now allows you to upload new translatable and reference files to existing projects. This is useful for situations when you
receive updated project files from your customer, or additional files that were missed from the initial drop.
Users with the new Update Project Files permission, can import new files using the new Update Project option under Projects view > All projects
tab.
Behind the scenes, Trados GroupShare automatically replaces the outdated versions in the project and applies all currently performed work to the
new project files.
For more information, see Mid-Project Updates topic in the online Help.
New operations for the Analyze Files report
To support the enhancements introduced for Mid-Project updates, the Reports view now includes new options for generating the Analyze files
report. In addition to the Full report which includes all statistics for the current project, you can now also generate a report for Inital project
creation, and individual separate report for each Add project file operation or Update project file operation.
For more information, see Working with reports.
Parent topic: Changes introduced in Trados GroupShare 2020 SR1 CU7
SQL Server Management Studio
If you are using SQL Server as the database server for your MultiTerm installation, you can use Microsoft SQL Server Management Studio to
view the databases that are used by MultiTerm.
In SQL Server, each termbase corresponds to a separate database. A termbase database is named < MTMaster>_<number>, where <
MTMaster> is the name of the MultiTerm master database name entered while installing GroupShare and <number> is a unique number.
For information on using Microsoft SQL Server Management Studio, see the Microsoft SQL Server documentation.
Parent topic: Managing termbase data on the host
Changes in the Online Editor
The Online Editor will be receiving an update with this release. Check the release highlights below.

Secure copy/paste from the Online Editor


Copy/pasting segment text from the Online Editor now only works in secure contexts (HTTPS connections). This feature is available for all
supported browsers.

Ability to paste text inside comments


Comments are no longer dismissed when clicking outside the box. This means that you can now copy/paste text from segments that contain the
currently marked segments.

Restricted editing of segments over 2000 characters


Editing the target segments of source segments that contain more than 2.000 characters is no longer allowed. When opening such files, the Online
Editor now shows a warning message and locks these segments. Previously, source segment were truncated at 2000 characters and content was
lost.
Note: 2000 characters corresponds to over one page of content, which generally makes translation difficult. To avoid working with such long
segments, we recommend that you review your segmentation rules.

Verification errors can now be filtered for a specific segment


The Verification side panel includes a new filter which shows errors specific to the segment you are currently working on.

Additional details displayed in status bar in form of tooltips


Hovering over the Restricted Editing text in the status bar now displays the following tooltip: Editor is in restricted editing mode and copy and
cut functionality is disabled.
Other tooltips providing more details are also available:
Text insert is active
Text overwrite is active
Editor is in limited editing mode and only adding comments is allowed.

Smart Actions improvements


Building on the recently introduced Smart Actions functionality, we have now made a series of enhancements to improve user experience:
Added the ability to hide the Smart Actions menu using the Esc key.
When filtering textual results, AutoSuggest now looks for matches only at beginning or end of a word.
Smart Actions menu is now be displayed when activating a segment, or in other relevant circustances, like when a tag is deleted. The Smart
Actions menu is automatically hidden when you start writing inside the segment.
Autoexpand is now disabled by default and you can manually expand it from the icon.
Fragment matches now feature tooltips.
Footers no longer cuts off the Smart Actions menu.
Placeables directions is now set to Auto, to correctly render text in right-to-left languages.

Other enhancements in Online Editor


Added support for sort order quickinsert.
Added Single quotation and Apostrophe options to the Insert Symbols drop-down menu.
Confirming segments with Batch Tasks > Update Translation Memory set to Approved Translation and Approved Signed-Off now
correctly saves translation units in the TM.
Parent topic: Changes introduced in Trados Groupshare 2020 SR1 CU9
Restricting user access to resources
When you want your users to have fewer user access permissions
Parent topic: User permissions

Remove user access permissions from an existing role


If your users already have a role which gives them several user access permissions, but you want to reduce the number of permissions, edit the
role. Note that all users who are already assigned to this role will be affected by this change.

Procedure
1. Go to the Users view and select the Permissions tab.
2. Expand the Edit Roles list and select the role you want to remove permissions from.
3. In the [role name] dialog, clear the checkboxes corresponding to the permissions you want to remove.
4. Select Finish.

Remove user from current role


If your users are assigned to a role with increased user access permissions, and you want users to have fewer access permissions to resources,
remove users from the current role and assign them a different role.

Procedure
1. Go to the Users view and select the Permissions tab.
2. Select the user's home organization (the organization in which the user was created).
3. Identify the user whose role you want to remove.
4. Select the checkbox corresponding to the user's name.
5. Select Remove Users.
Known issues
Component Description or workaround
GroupShare 2020 Trados GroupShare ignores any specific language pairs settings coming from the project template for files added
using the Update Project Files option. (LTGS-11106)
GroupShare 2020 Organizations cannot be deleted from the GroupShare UI or using the DELETE /api/management/v3 endpoint (which
the UI uses) on environments where TM Server is installed without Project Server. (LTGS-11157)
Workaround: To delete organizations in this scenarios, call the DELETE
/api/management/v2/organizations/{organizationId} endpoint instead.

GroupShare 2020 To avoid vulnerabilities identified in the Reporting component and update its outdated libraries, we plan to retire Logi
Analytics and replace the Reporting implementation with the next Trados GroupShare CU. (CRQ-32113)
Parent topic: Changes introduced in Trados Groupshare 2020 SR1 CU8
Users
Users are the individuals or bodies which collaborate on various tasks within an organization. Users can belong to one or several organizations
where they fulfill roles. Roles enforce the permissions users have over resources.
Creating users
Users are defined by the roles they have within organizations. In addition to the standard users (defined by their standard roles) Trados
GroupShare allows you to create as many users as you need to organize your translation team.
Editing users
When no longer up-to-date, the users' account details or assigned roles can be modified to reflect the permissions they are intended to have
in Trados GroupShare.
Viewing users
You can consult the list of all the available users in an organization.
Deleting users
When users are no longer part of your organization you can delete them.
User roles
Every user who is part of an organization has a role. If users are part of several organizations, they may have different roles across
organizations. In Trados GroupShare you can use its standard, default roles or create new roles. Each role has an associated set of
permissions.
User permissions
User permissions are defined in a system-wide list that is not editable. Permissions are grouped under roles. By assigning roles to users, you
can easily manage the permissions users have to perform tasks in Trados GroupShare.
Parent topic: Working with users, roles and permissions
Error message solutions
Activation Failed - The license is already registered
Activation Failed - Cannot connect to activation server
Network License errors - Retry button
Parent topic: Licensing
Updating TMs after project file download
You can download the translated project files in their native format and update the TMs (translation memories), during any project phase, if you
are not restricted in this regard by a user who has the Secure Project File Download permission.

Before you begin


You can update TMs after project file download only if you have the Write TU permission and if you are not restricted by a user who has the
Secure Project File Download permission.

About this task


To restrict the download of project files to some users, users must be assigned a role which has the Secure Project File Download permission. The
Secure Project File Download permission is assigned to the following roles by default: Administrator, Power User and Project Manager. During
project creation, users in these roles must select the Prevent file downloads for this project checkbox, which means that only users with the Secure
Project File Download permission will be able to download the source project files and the translated project files.

Procedure
1. In the Projects view, select the project whose TM you want to update.
2. In the project tab, do one of the following:
Select Download all files > Download preview for all target files > Include TM Update.
Select the checkboxes corresponding to the files you want to download and select selected files > preview of target version for
selected files > Include TM Update.
The target files are now downloaded as a zip archive which you can save on a location of your choice. The TM is automatically updated
with the newly translated units.
Parent topic: Project management
Parent topic: Translation memories (TMs)
Specifying segmentation rules
You can customize the segmentation rules that parse your translation memory (TM), in order to adapt the TM to your translation goals.

About this task


When you specify segmentation rules, you edit the language resource template used to create a TM.

Procedure
1. Go to the Resources view.
2. In the Language Resource Templates tab, select the checkbox corresponding to the template of choice.
3. Select Edit.
4. In the [language resource template name] dialog, select Language Resources.
5. Identify the language for which you want to modify segmentation rules and select .
6. In the [language resource template name > language] dialog, select Segmentation Rules.
7. Perform any necessary change.
8. Select Finish.
Parent topic: Segmentation rules
Related concepts
Example of a segmentation rule
Viewing project level reports
You can view report details irrespective of the project's file phases.

About this task


Reports are available only for projects created in Trados GroupShare. There are three available reports: Analyze Files, Post-translation Analysis
and Audit Trail report. To access the Audit Trail report, you must either be assigned the Administrator role or the AuditTrail permission.

Procedure
1. Go to the Projects view and select a project to open it.
2. In the [project name] tab, select .
3. Consult the report details.
4. Optionally, go to the table columns and:
Sort the data in ascending or descending order.
Customize the columns that are displayed.
Tip: The filters you apply at column level are kept when printing the report.

Example of Audit Trail report


The Audit Trail report enables you to consult the entire, unique path a document goes through from source to target. You can filter document
actions per timestamp.

Parent topic: Project-level reports and background tasks


Borrowing a network license from Trados License Server
Commuter licensing allows users to borrow a license. Users usually require a commuter license when they want to travel and need to use Trados
GroupShare offline, for a certain period of time.

About this task


The network user borrows a license seat for the duration of the trip (when their computer is not connected to the network) and checks it back in
on returning. Borrowed licenses reduce the available pool of licenses. As long as the license is borrowed, it is not available on the license server.
Borrowed licenses are automatically returned when the borrow period expires. Users can also return a borrowed license early, but they have to be
connected to the network license server when returning it.
Borrowing limit - By default, you can borrow a license for a maximum of 30 days. If you need to borrow a license for more than that, return the
license to the server and borrow again. When the borrowing period expires, Trados GroupShare stops working and the client user is required to
connect to the company's network.
Time zone - To prevent license tampering issues, the client workstation and the network server must be in the same time zone for borrowing
licenses.
Last license seat - You will not be able to borrow the last license seat available on the license server for a product edition. This is because
connecting to the server in order to borrow a license already requires a license seat. Borrowing is not possible without an available license seat.
The seat required for the connection is returned back to the license pool immediately after the server grants the borrowed license.

Procedure
1. Connect to the license server to consume a license seat.
2. Go to Help > Product Activation to display the Product Activation dialog.
3. In the Product Activation dialog, select the Borrow a License link.
4. Specify the number of days you want to borrow the license for.
5. Select Borrow License. This moves the license from the server to your computer. You can now work with Trados GroupShare without
being connected to the license server.
Parent topic: Connecting to the Trados License Manager (users)
Changing Trados License Server details
If you use a network license, you may need to change details for the license server to which you are connecting. This is likely to happen if you want
to use a different license server or if the current license server has changed names.

Before you begin


You must have a new license server.
You must know the new license server name.

Procedure
1. Run the application.
2. Go to Help > Product Activationto display the Product Activation dialog.
3. In the Product Activation dialog, select Change License Server.
4. On the Configure a License Server, enter the short computer name, the fully qualified address (less than 40 characters) or the IP address of
the license server.
5. Select Connect.
The Product Activation page is displayed with details of the active license.
6. Select Continue to open Trados GroupShare.
Parent topic: Connecting to the Trados License Manager (users)
Managing termbase data on the host
All termbases, including MTMaster, are stored on the data host. The data host is accessed by MultiTerm Server, and MultiTerm Server in turn is
accessed by the users of the client applications on the network.
Note: Do not use the host database management software, such as SQL Server Enterprise Manager, to delete or modify the MultiTerm master
database. Make changes to the MultiTerm master databases only from MultiTerm Administrator.
Also, do not modify terminology data directly on the database server. Always use MultiTerm to change terminology data.
SQL Server Management Studio
If you are using SQL Server as the database server for your MultiTerm installation, you can use Microsoft SQL Server Management Studio
to view the databases that are used by MultiTerm.
Log files
Database backup
Back up the master databases and the individual databases and tables regularly.
Parent topic: Using the Trados GroupShare Console
Removing permissions from user roles
Permissions are stored in a system-wide list. Roles are permission sets or bundles whose scope can be narrowed down by removing permissions
from them.

Procedure
1. Go to the Users view and select the Permissions tab.
2. Expand the Edit Roles list and select the role you want to remove permissions from.
3. In the [role name] dialog, clear the checkboxes corresponding to the permissions you want to remove.
4. Select Finish.
Parent topic: User permissions
Related concepts
Dependencies between permissions
Adding containers
Upon Trados GroupShare installation, a default container is set. Depending on your needs and the complexity of your organization, you can add as
many containers as you need. Containers must be added before creating TMs. One container can support several TMs.

Procedure
1. Go to the System Configuration view.
2. In the Containers tab, select New Container.
3. In the Create Container dialog:
a. Choose a location for your container within the organization.
b. Choose a database server.
c. Enter a container name and a database name.
d. Optionally, provide a description for your container.
4. Select Finish.
Parent topic: Containers
Global reports
There is a set of three predefined reports available to view on the Reporting view of the web UI.
There are currently three pre-defined reports in the reporting area:
Projects - this report is a list of all the projects that respect the criteria you filter for in the Reporting view. You can select a project's name
to open it in the Projects view.
Tasks - you get a comprehensive view of the current progress on all the tasks that you've filtered for in the Reporting view. You can select a
task's name to open it in the Projects view.
TM leverage - you can see the performance of the TMs you are using in the projects that you've filtered for in the Reporting view
Filtering and exporting reports
For a more granular view of the translation work progress, you can filter reports by different criteria.
Parent topic: Working with reports
Interpreting translation unit matches and penalties
When you perform translation memory (TM) lookups, the resulting translation units (TUs) are displayed in the Lookups panel together with details
such as: match percentage, fields, the person who added the TU to the TM, the date when the TU was added. The match percentage is influenced
by the penalty values specified in the main application using Online Editor.

About this task


Match percentages reflect the translation origin of the TU. Matches can have one of the following values:
100% Match - This target segment has been changed by applying a TU, with 100% match, from a TM.
Context Match - This target segment has been changed by applying a TU, with context match, from a TM (the preceding source and target
segments are identical).
Fuzzy Match - This target segment was translated by applying a TM match ranging from 1%-99%, and then by editing and confirming the
translation. The match is below 100% because one or more penalties were applied.

Procedure
1. Open the appropriate file in Online Editor.
2. Select the target segment to which you want to apply an existing translation. The available translations are automatically displayed in the
Lookups panel.
3. Check the TU details: fields, the person who added the TU to the TM, the date when the TU was added.
4. Check the TU match percentage and the applied penalties:
Missing formatting
Different formatting
Multiple translations
Auto-localization
Text replacement
Alignment
Character-width difference
Parent topic: Working with translation memories and terminology
Delete organizations
You can delete any organization or sub-organization that you no longer need. Deleting an organization removes all the resources available inside the
organization: users, translation memories, termbases, sub-organizations and libraries.

Before you begin


Make sure your account has the permissions required to delete all types of resources available in the organization. You can only remove the
resources for which your user has Delete permissions.

About this task


You cannot remove the Root Organization. If your installation only includes MT Server, you can only delete empty organizations. This is because
deleting an organization's resources is handled by the Execution Service, which is not deployed on MT Server-only installations.
Organizations are deleted as a background task. The task details shows information on task duration and the IDs of every resource deleted.
To delete an organization:

Procedure
1. Go to the Users view.
2. Under Organizations, select the organization you want to remove.
3. Select .
4. Select Yes in the confirmation message.
If the resources have been created under the organization that you delete, these resources will be removed from Trados GroupShare
altogether.
If the organization that you delete is only referencing resources created under a different organization, these resources will still be available in
the source organization.
Parent topic: Organizations and their components
Working with projects
Trados GroupShare is a repository and server for projects that are published from Trados Studio or which are created directly in Trados
GroupShare.

Working with projects in Trados GroupShare


Once a project is created in Trados GroupShare, you can:
View its status in the Projects view.
Open the project tab, and consult the project planning board and statistics.
Move the project files on the Kanban-style board to mark their workflow progress.
Create file assignments and your users can start working on their assignments in Trados Studio.
Add, remove or replace files to existing projects.
Update the existing files with new files.
Cancel any file or multiple files from a project.
The project planning board can be consulted when opening the project in its tab. The default view of the board is a Kanban-style view with the
project files arranged inside columns representing the translation phases used in the Trados GroupShare workflow. The alternative view of the
board contains a list of all project files, where you can click the plus sign next to a file to check its version and comments. You can switch between
views with the button.
The project statistics can be consulted when opening the project in its tab. The upper-right corner of the project tab provides:
An estimation of the project's status based on the number of translated segment
A chart with the percentage of files in each phase

Working with projects in Trados GroupShare


Once a project is created in Trados Studio, it can be published to Trados GroupShare in order to split the work on the project files among Trados
GroupShare users. All translation and review work is done in Trados Studio.
A Trados Studio project:
Holds information needed to translate files (e.g. translation memories or file type settings).
Has one source language and can have multiple target languages.
Has project-level settings and may have individual-file settings.
A Trados Studio project that is published to Trados GroupShare has a workflow which:
Defines the stages the project goes to until it is completed.
Defined the tasks that need to be done to move the project or project files through workflow stages.
Enables users to work on their assignments in Trados Studio.
Workflow for shared projects started in Trados Studio
Trados Studio and Trados GroupShare synchronize continuously to support your projects and file assignments.
Workflow for shared projects started in Trados GroupShare
Project managers can manage shared projects and file assignments directly from the Trados GroupShare web interface.
File assignment
Trados GroupShare and Trados Studio work together to enable file assignments for projects published to a Trados GroupShare server. The
file assignment process enables users to make files in an Trados GroupShare project available only to members of a specific role and only
for specific stages of the translation process.
File translation and check-in
You can translate the files of an Trados GroupShare project in Trados Studio or Online Editor, depending on your license agreement. The
check-in process is influenced by these choices.
Project management
The Trados GroupShare interface enables you to manage both new and completed projects.
Project archiving
Users with Edit Project permission can archive a project or restore an archived project from the Trados GroupShare web interface. Users
with the Delete Project permission (by default, Administrator, Power User and Project Manager accounts) can detach a project from
Trados GroupShare's database.
Translation statuses
Trados GroupShare shows the translation status for each project uploaded to Trados GroupShare and for each document included in the
project.
About Perfect Match
A Perfect Match is a form of context match that compares updated source files to a corresponding set of existing bilingual files rather than to
a translation memory (TM). Segment matches, known as Perfect Matches, are checked for context, that is, the surrounding entries are
checked to ensure that they are the same.
Supported file types
The current topic provides a table of supported file types, their file name extensions, and a help topic concerning the file type settings.
Working with custom batch tasks in Trados GroupShare
During project creation, Trados GroupShare automatically runs the following sequence of default batch tasks to prepare the project files for
translation: Scan file type, Convert to translatable format, Split text into segments, Apply PerfectMatch files (where available), Pre-
translate files, Analyze files.
Running verification during translation
When you verify your translated segments, the system compares the source and the target to find missing or incorrect tags.

About this task


This feature is available for Online Editor Advanced.

Procedure
1. Open the appropriate file in Online Editor.
2. In the Online Editor, select the segment you want to verify.
3. Go to the Review tab and expand the Verify menu.
To perform verification at segment level, place your cursor in a particular segment, and then select Verify segment.
To perform verification on the entire document, select Verify document.
Check the results in the Verification panel on the right:
Error - For example, this message is displayed when a tag is missing.
Warning - For example, this message is displayed when the order of tags is changed.
Info - For example, this message is displayed when there are additional or missing spaces in tags.
Parent topic: Verifying translated content
Cutting, copying, and pasting text
You can select fragments of text and copy them somewhere else in the file or move them there altogether.

Before you begin


Before you cut text from a source segment or paste text to a source segment, you need to enable source editing (Other Actions > Edit Source).
However, you do not have to do this if you only want to copy text from a segment or to paste text to a target segment.

Procedure
1. Open the appropriate file in Online Editor.
2. Select the text that you want to cut or copy.
3. On the Home tab, in the Clipboard group, select Cut or Copy, depending on what you want to do.
4. Click the exact place where you want to paste the text.
5. Select Ctrl+V.
Tip: You can also select Paste on the Online Editor user interface, but some browsers do not support this action.
Parent topic: Navigating the Online Editor user interface
Upgrading to Trados GroupShare 2020 SR1
Upgrading from SDL Studio GroupShare 2015 to Trados GroupShare 2020 SR1
Upgrading from SDL Trados GroupShare 2017 to Trados GroupShare2020 SR1
Project templates
Project templates are.sdltpl files that are generated in Trados Studio from existing translation projects.
Project templates are useful when you want to start a new Trados Studio project using the settings or configuration of previous projects. In the
context of theTrados GroupShare and Trados Studio integration, shared project need to be compatible across these two application. To ensure
compatibility, all the projects that are created in Trados GroupShare must be based on Trados Studio templates.
Creating project templates
Project templates are used in Trados GroupShare when creating projects from the web interface.
Deleting project templates
You can safely delete any project template that no longer meets your requirements.
Parent topic: Working with resources
Adding translation units
If you confirm a segment, you can add it as a new translation unit (TU) in your TM.

Procedure
1. Open the appropriate file in Online Editor.
2. Select the target segment and edit it.
3. Select Confirm > Add as new Translation Unit or press Ctrl+Shift+U.

Results
The translation unit is updated in the translation memory. These updates are also reflected in the Lookups panel.
Parent topic: Working with translation memories and terminology
Connecting to the Trados License Manager (users)
You can activate Trados GroupShare by connecting to a license server they have access to. Users need to know that computer's short name, the
fully qualified address (less than 40 characters) or its IP address.
You can also work with Trados GroupShare while disconnected from the license server, by borrowing a license from a license server.
Connecting to Trados License Server to consume a network license seat
When connecting to the Trados License Server , you (as the client user) make a request to obtain a valid Trados GroupShare license. A
license consists of a number of product features, all of which are checked out as part of checking out the license.
Disconnecting from Trados License Server to free up a license seat
Disconnecting from the license server returns your license seat to the license pool. The license seat is immediately available for other
network users to activate Trados GroupShare on their computers.
Borrowing a network license from Trados License Server
Commuter licensing allows users to borrow a license. Users usually require a commuter license when they want to travel and need to use
Trados GroupShare offline, for a certain period of time.
Returning a borrowed network license to Trados GroupShare
If you borrow a network license, you can return it before the borrowing period expires or after the expiry date is reached. If you do not
return your license, it will not be available for use by other users, even if the license expired.
Changing Trados License Server details
If you use a network license, you may need to change details for the license server to which you are connecting. This is likely to happen if
you want to use a different license server or if the current license server has changed names.
Parent topic: Network licenses
Application Server - restart options
The Application Server may restart or not depending on the changes you make to the configuration or the licensing options.
Generally, the Apllication Server restarts once the activation screen is closed.
The Application Server restarts automatically if:
a different license is activated
the same license is activated after changes to its configuration
The Application Server does not restart automatically if:
the license is only viewed
the license is deactivated and (and no trial license is active)
Parent topic: Licensing
Confirming translated segments
You should confirm segments when you finish translating them or if you want to approve them during the review process. Confirmed translations
are added to the translation memory automatically.

About this task


Status changes:
The segments you confirm as translator get the Translated status.
The segments you confirm as linguistic reviewers get the Translation Approved status.

Procedure
1. Open the appropriate file in Online Editor.
2. Select the target segment whose translation you want to confirm.
3. On the Home tab, in the Segments group, do one of the following:
To confirm and move to the next unconfirmed segment, select Confirm > Confirm and Move to Next Unconfirmed Segment or press
Ctrl+Enter.
To confirm and move to the next segment, regardless of its status, select Confirm > Confirm and Move to Next Segment or press
Ctrl+Alt+Enter.
To confirm, but stay on the same segment, select Confirm > Confirm, but do not Move to Next Segment or press
Ctrl+Alt+Shift+Enter.
To confirm and add the translated segment as a new translation unit (if the translation memory already contains a translation for the
source segment and you do not want to overwrite it), select Confirm > Add as new Translation Unit or press Ctrl+Shift+U.
Note: If you add translations with missing tag pairs or with extra tag pairs as new translation units, a multiple translations penalty is
applied to them, which means that they are displayed as 99% matches, not as 100% matches.
Important: When you confirm a segment, the same segment cannot be confirmed again till the previous confirmation action, which involves
saving the changes, is fully completed. Otherwise, a warning is shown.
Auto-propagation in Online Editor
Auto-propagation is the process whereby the confirmed translation of a segment is applied to all the segments having the same source
content.
Parent topic: Translating content
Step 2: Assigning files to users
After publishing your project to Trados GroupShare you must delegate the translation work to specific users, so that they can start translating or
reviewing the project files. Remember that you may have already assigned users to files or phases on the Trados GroupShare page of the Create a
New Project wizard.

Before you begin


Make sure that the users you want to assign tasks to are added to the Trados GroupShare server. Add the missing users to the Trados
GroupShare server before you begin the assignment process.
Make sure that your Trados GroupShare users are assigned roles and permissions that allow them to perform actions on the assigned files.
Assign users the appropriate roles or adjust the permissions associated to their roles before you begin the assignment process.

About this task


When the allocated files reach the phase where the users are assigned to work on them, Trados GroupShare automatically sends the assigned
users a phase change notification email. This informs the users that they can start working on the files you assigned to them.

Procedure
1. In Trados Studio, go to the Projects view, double-click a project published on Trados GroupShare to open it.
2. In the Files view, go to the Home tab and select the GroupShare layout.
3. Expand Assign to Users in Phase and select a phase.
4. In the Assign Users to the [phase name] Phase dialog, select Add.
5. In the Select Users dialog, select Show all users from the GroupShare server, and consult the list of users available on the server where the
project is published.
6. Select the user you want to assign work to and select OK.
7. In the Assign Users to the [phase name] Phase dialog, select OK.
8. Repeat steps 3 - 7 to add users to all the phases the document(s) will go through.
Note: If you add or remove assigned users during the current phase, Trados GroupShare sends an assignment change email.
Parent topic: Workflow for shared projects started in Trados Studio
Related concepts
Standard roles and permissions
Dependencies between permissions
File assignment security
Moving single-user license to another computer without
Internet
If you cannot access the Internet from the computer on which the currently activated (licensed) version of Trados GroupShare is installed or if your
firewall prevents you from performing online deactivation, you can either modify your proxy settings or use offline deactivation.

About this task


To deactivate Trados GroupShare when you have no Internet connection, you need to use another computer with Internet access to the RWS
website to return the deactivation certificate.

Procedure
1. Go to Start > GroupShare [year] > GroupShare [year] Product Activation to displat the Product Activation dialog.
2. Generate the deactivation certificate:
a. In the Product Activation dialog, select the Deactivate offline link.
b. On the Offline Deactivation page, select Generate Certificate.
A Deactivation certificate code is displayed.
3. Return the deactivation certificate:
a. Switch to a computer that can access the Internet and log onto My Account.
i. Select the Licenses link.
ii. Follow the prompts for returning your Trados GroupShare deactivation certificate using the copy of the deactivation
certification that you have.
b. Return to the Product Activation dialog and select I have returned the deactivation certificate to RWS.
c. Select Confirm.
4. Activate the certificate on the new computer.
Parent topic: Moving single-user license to another computer
Changing segment statuses
You can change the status of a segment if you want to mark a confirmed segment as Draft or if you want to approve, reject, or sign off translated
segments during the review process.

About this task


This feature is available for Online Editor Advanced.
The available translation statuses are: Not Translated, Draft, Translated, Translation Rejected, Translation Approved, Sign-off Rejected, Signed
Off. The translation status is indicated by the icon displayed in the Segment Status column. When changing the segment status, a new translation
origin is created.

Procedure
1. Open the appropriate file in Online Editor.
2. Select the target segment whose status you want to change.
3. On the Home tab, in the Segments group, select Change Segment Status, and then select a new status for the target segment.
Parent topic: Translating content
Installing Trados GroupShare
This section contains general information about installing Trados GroupShare 2020 SR1 and the technical requirements for the installation.

About this task


For step-by-step instructions in how to install and maintain Trados GroupShare, see the Installation guide.
Supported operating systems
Supported database servers
Supported browsers
GroupShare kit
The kit includes two types of available information: .NET library for Trados GroupShare REST API and TM Search and Terminology
Editing using REST API.
REST API information
REST API information is hosted in Swagger. The information can be used interactively to learn more about the actions that can be
performed on projects, translation memories, termbases and any other resources.
Installing Trados GroupShare 2020 SR1
This topic contains some important notes on installing Trados GroupShare. Complete instructions for installing Trados GroupShare are
available in the dedicated Trados GroupShare Installation Guide PDF.
Checking GroupShare logs
Check the event logs to monitor GroupShare process executions, and trace possible issues.
Securing your Trados GroupShare webserver
You can use HTTP Strict Transport Security (HSTS) policy to protect against man-in-the-middle attacks, such as protocol downgrade
attacks and cookie hijacking.
Changing file storage location
By default, files are saved in %ProgramData%\SDL\SDLServer1\FileStore, on the computer where Trados GroupShare is installed, but this
location can be changed if necessary.

Before you begin


To support projects, termbases (TBs) and translation memories (TMs) published on the GroupShare server, Trados GroupShare stores:
All the project files and packages published from Trados Studio to Trados GroupShare
All the TBs imported or exported from MultiTerm Online
All the TMs imported or exported from TM Server
To import and export TB data to the folder which stores files, make sure to give Read and Write permissions for this folder to:
Users running Tomcat
Users running the Application service
Attention: The files in this folder provide the information that Trados GroupShare and Trados Studio exchange in order to support server projects
and the information that MultiTerm Online requires to open import/export files. Do not delete these files unless you no longer need these projects
and import/export data, and you know that the missing files will not affect any Trados GroupShare functionality.

Procedure
1. In the Trados GroupShare Console navigation tree, select SDL Trados GroupShare > Settings.
2. In the Settings pane, under File Storage, specify a new location for file storage.
3. In the Actions pane, select Apply Changes to save the change.
Parent topic: Trados GroupShare Console settings
Using the Trados GroupShare WebHooks Service
Learn how to configure and use the Trados GroupShare WebHooks Service.
REST API endpoint of WebHooks Service
Interaction with the Trados GroupShare WebHooks Service happens through REST API calls, secured with bearer tokens (that you get using Trados GroupShare Management Rest API login endpoint).
WebHooks Notifications (callbacks)
After a WebHook URI was registered for a certain event you will get callbacks when that event occurs. The callback is a POST request.
Other information related to Trados GroupShare WebHooks
Parent topic: WebHooks Service

Configuring WebHooks Service


To configure the WebHooks service:

Procedure
1. Go to C:\Program Files\SDL\SDL Server\WebHooks Service.
2. Edit Sdl.GroupShare.WebHooksService.exe.config. The relevant settings are shown below:
<appSettings>
<add key="RestHostUrl" value="http://+:41239" />
<add key="MessageQueueHost" value="localhost" />
<add key="MessageQueueUserName" value="gssvc" />
<add key="MessageQueueUserPassword" value="u5F/lWdnD+snwvYcjKv/Fg==" />
<add key="WebHookQueueName" value="GsWebHookQueue" />
<add key="WebHookQueueDeadLetterName" value="GsWebHookQueueDeadLetter" />
<add key="WebHookQueueDLXName" value="GsWebHookDlx" />
<add key="Server" value="gs-test-url.sdltest.com" />
<add key="serilog:write-to:RollingFile.pathFormat" value="C:\ProgramData\SDL\Service\logs\WebHooks.Log" />
</appSettings>
<connectionStrings>
<add name="MS_SqlStoreConnectionString" connectionString="Server=(local)\sqlserver2014;Database=WebHooks;Trusted_Connection=True;" providerName="System.Data.SqlClient" />
</connectionStrings>

Observe the configuration used for the service listening port, the RabbitMQ message queue and the database where the web hook registrations will be stored.
RestHostUrl The host and port setting that the Web Hooks Service will use to listen on.
MessageQueueHost, MessageQueueUserName, MessageQueuePassword are configured by the Trados GroupShare installer and are needed to consume messages from RabbitMQ.
WebHookQueueName, WebHookQueueDeadLetterName, WebHookQueueDLXName are used to specify the queues to consume messages from. It would be possible to create new queues with different routing keys. We
recommend to leave as it is.
Server - the value of the Server setting will be included in the callback request body, to know the web hook sender of the message.

Subscribing to events
You can subscribe to all existing events by using the "*" filter and a single callback handling URL.

About this task


The available filter types are as follows:
Sdl.GroupShare.Events.V2.ProjectCreatedEvent
Sdl.GroupShare.Events.V2.PhaseChangeEvent
Sdl.GroupShare.Events.V2.AssignmentEvent
Sdl.GroupShare.Events.V2.CheckOutEvent
Sdl.GroupShare.Events.V2.CheckInEvent
*

Interacting with the REST API endpoint


Interaction with the Trados GroupShare WebHooks Service happens through REST API calls, secured with bearer tokens (that you get using Trados GroupShare Management Rest API login endpoint).

About this task


See REST API endpoint of WebHooks Service for more details.

Receiving WebHooks notifications (callbacks)


After a WebHook URI was registered for a certain event you will get callbacks when that event occurs. The callback is a POST request.

About this task


See WebHooks Notifications (callbacks) for more details.

Testing REST API endpoints


To test / try Rest API endpoints, use the Postman collection .

About this task


Download and extract the ZIP file for Trados GroupShare WebHooks Postman collection.
The License Server
The License server is the computer where your administrator installs Trados License Manager. The computer is hosted on the customer site and
should be located in the same LAN where the client applications are installed.
Network licenses can be activated using Trados License Manager. Then, any other computer which requires licensing (client) can connect to the
server and request a license when concurrent licensing is used. Trados License Manager can host both Passolo and Trados Studio commuter
licenses.
Important: You must uninstall Trados License Manager and Trados License Manager v2.0 before installing Trados License Manager v3.0.
Parent topic: Working with single-user and network licenses
Step 2: Adding database container
After you install Trados GroupShare, a default container is set. Depending on your needs and the complexity of your organization, you can add as
many containers as you need. One container can support several TMs.

Procedure
1. Go to the System Configuration view.
2. In the Containers tab, select New Container.
3. In the Create Container dialog:
a. Choose a location for your container within the organization.
b. Choose a database server.
c. Enter a container name and a database name.
d. Optionally, provide a description for your container.
4. Select Finish.
Parent topic: Configuring server-based TMs
Editing projects
You can change the planning details of your projects when no longer up-to-date.

Procedure
1. In the Projects view, select the project you want to edit.
2. In the project tab, select Planning for <n> file.
3. In the Planning for [file name] window, perform your changes for any phase details: delivery date or assigned users.
4. Select Save.
Parent topic: Project management
Contents

Index

Search

Trados GroupShare 2020 SR1


Index
Search
Enter search criteria:
Search
No documents found
loading...
Contents
Welcome to the Trados GroupShare 2020 SR1 documentation
Customer support
Support articles
Acknowledgments
Legal notice
Change log
Sending a help topic
REST API information
GroupShare kit
Release notes
What's new in Trados GroupShare
Changes introduced in Trados Groupshare 2020 SR1 CU9
New and improved Dashboard and reporting interface
API changes for third-party developers
Changes to TM Service
New REST endpoints
Share project via direct link
Update existing projects with PerfectMatch archives
Changes in the Online Editor
New .NET runtimes
Retiring legacy Language Weaver URLs
Other enhancements
Fixed issues
Known issues
Components update
Changes introduced in Trados Groupshare 2020 SR1 CU8
Changes introduced in Trados GroupShare SR1 CU8.1
New project settings XML REST API endpoint
API changes for third-party developers
Updated MultiTerm Online classic layouts
Fixed issues
Other changes
Known issues
Changes introduced in Trados GroupShare 2020 SR1 CU7
Mid-project updates
Updated documentation
Upgraded components
Service password encryption changes
Added support for new files types
Fixed issues
Known issues
Changes introduced in Trados GroupShare 2020 SR1 CU6
Third-party authorization
Enhanced security policies
Improved defense against cross-site scripting
Find your project templates easier
Automatic configuration CP-S: Authentication Server Address
Interactive Logon permission is no longer required
Custom Properties Service API
GroupShare REST API improvements
Updated requirements
Fixed issues
Known issues
MultiTerm Online security hotfix
Changes introduced in Trados GroupShare 2020 SR1
Real-time updates and notifications
Post-translation Analysis report
Possibility to delete non-empty organizations
Apply Perfect Match from bilingual files
User profile pictures
Dropped support for SQL Server 2014
Other enhancements
Changes introduced in SDL Trados GroupShare 2020
New solution for reporting and dashboard
Mixed Online Editor licensing options
Verify translations in Online Editor
Installing Trados GroupShare
Supported operating systems
Supported database servers
Supported browsers
GroupShare kit
REST API information
Installing Trados GroupShare 2020 SR1
Checking GroupShare logs
Securing your Trados GroupShare webserver
Server security configuration recommendations
Upgrading to Trados GroupShare 2020 SR1
Upgrading from SDL Studio GroupShare 2015 to Trados GroupShare 2020 SR1
Upgrading from SDL Trados GroupShare 2017 to Trados GroupShare2020 SR1
Projects status overview in the Dashboard
Working with users, roles and permissions
Organizations and their components
Organizations and users
Organizations and libraries compared
Organizations and resources
MultiTerm and Trados GroupShare
Creating organizations
Editing organizations
Delete organizations
Configuring a basic organization
Configuring organizations and users for enterprise
Resource Links
Adding resource links
Removing resource links
Deleting resources
Users
Creating users
Editing users
Viewing users
Deleting users
User roles
Creating roles
Editing roles
Deleting roles
Assigning roles to users
Removing roles from users
Standard roles
User permissions
Adding permissions to user roles
Removing permissions from user roles
Assigning permissions to user groups
Assigning user access to resources
Increasing user access to resources
Removing user access to resources
Restricting user access to resources
Dependencies between permissions
Standard roles and permissions
Working with projects
Workflow for shared projects started in Trados Studio
Step 1: Publishing projects to Trados GroupShare
Step 2: Assigning files to users
Step 3: Updating file phase
Step 4: Completing assignments
Step 5: Advancing assignments to the next phase
Step 6: Completing projects
Workflow for shared projects started in Trados GroupShare
Step 1a: Creating projects from scratch
Step 1b: Creating projects based on previous projects
Step 1c: Updating an existing project
Step 2: Planning work on assignments
Step 3a: Completing assignments in Trados Studio
Step 3b: Completing assignments in the Online Editor
Step 4: Completing projects
File assignment
File assignment security
File assignment notifications
File translation and check-in
Translating and checking in files from Trados Studio
Translating and checking in files from Online Editor
Translating and force check-in files from Trados GroupShare
Translating and undoing file check-out from Trados GroupShare
Project management
Viewing projects
Creating projects
Set up translation providers
Set up Language Weaver from the webUI
Set up translation providers from the Console
Step 1c: Updating an existing project
Restricting the download of project files
Downloading project files in .sdlxliff format
Working with project packages
Downloading translated project files
Updating TMs after project file download
Editing projects
Completing projects
Restoring completed projects
Deleting projects
Project settings
Viewing project settings
Editing project settings
Project details progress bar
Project archiving
Archiving completed projects
Restoring archived projects
Detaching completed projects
Translation statuses
About Perfect Match
Supported file types
Working with custom batch tasks in Trados GroupShare
WebHooks Service
What is Trados GroupShare WebHooks Service
Using the Trados GroupShare WebHooks Service
REST API endpoint of WebHooks Service
WebHooks Notifications (callbacks)
Other information related to Trados GroupShare WebHooks
Working with resources
Translation memories (TMs)
GroupShare TMs and local TMs
Main TMs and project TMs
Language Pairs
Translation statuses
Configuring server-based TMs
Step 1: Adding database server
Step 2: Adding database container
Step 3: Creating server-based TM
Translation memory advanced settings
Modifying server-based TMs
Deleting server-based TMs
Exporting TUs from server-based TMs
TM system fields
Importing TUs to server-based TMs
TM import options
TU import statistics
Downloading server-based TMs
Tuning server-based TM performance
TM performance tuning
Updating TMs after project file download
TM language processing rules and recognized tokens
Item categories: translatable and other items
Language resource templates
Creating language resource templates
Editing language resource templates
Exporting language resources as template
Segmentation rules
Segmentation process overview
Example of a segmentation rule
Specifying segmentation rules
Abbreviations
Defining abbreviations
Exporting abbreviations
Importing abbreviations
Ordinal followers
Defining ordinal followers
Exporting ordinal followers
Importing ordinal followers
Recognized Tokens
Time and measurement tokens
Enabling time and measurement tokens
Acronyms and URLs
Enabling acronyms and URLs
Variables
Format of variables
Defining variables
Enabling variables
Fields
Creating field templates
Editing field templates
Exporting fields as template
Containers
Adding containers
Modifying container details
Deleting containers
Servers
Adding servers
Modifying server details
Deleting servers
Termbases
Project templates
Creating project templates
Deleting project templates
Custom fields
Creating custom fields
Editing custom fields
Deleting custom fields
Working with reports
Global reports
Filtering and exporting reports
Project-level reports and background tasks
Viewing project level reports
Printing project level reports
Saving project level reports
Working with Online Editor
Online Editor editions
Opening files in Online Editor
Checking in files in Online Editor
Downloading files in Online Editor
Shortcuts in Online Editor
Navigating the Online Editor user interface
Modifying the layout of the workspace
Detaching the side panel
Viewing navigation information about a file
Viewing information about the structure of a file
Consulting cloud project details
Details about segments and translations
Adapting the contrast of colored text
Making text larger or smaller
Navigation themes
Navigating between segments
Cutting, copying, and pasting text
Support for right-to-left scripts
Translating content
Copying source content to target segments
Source content copying for segments with revisions
Modifying source segments
Copying content in target segments
Splitting segments
Merging segments
Formatting segments
Viewing white spaces and other non-printing characters
Viewing formatting tags
Options for displaying tags
Copying formatting from the source text to the target text
Copying tag pairs
Clearing segment formatting
Inserting symbols and special characters
Overwriting content in segments
Clearing the content of target segments
Working with translation memories and terminology
Performing concordance searches in the translation memory
Viewing differences between translation memory matches
Consulting details for translation memory lookups
Blurring or hiding unfiltered translations
Applying translations
Applying terminology
Using smart actions
Interpreting translation unit matches and penalties
Updating existing translation units
Adding translation units
Locking and unlocking segments or parts of segments
Confirming translated segments
Auto-propagation in Online Editor
Changing segment statuses
Verifying translated content
Running verification during translation
Checking verification results
QA messages in the Verification panel
Tag messages in the Verification panel
Reviewing translated content
Revision modes
Reviewing content with Track Changes
Moving from one revision to another
Accepting revisions
Modifying revisions
Rejecting revisions
Revision color markup
Working with comments
Viewing comments
Adding comments
Modifying comments
Deleting comments
Filtering segments
Translation statuses
Translation origin
Undoing or redoing actions
Performing batch operations on segments
Finding and replacing text
Timeout interval in Online Editor
Known issues in Online Editor
Using the Trados GroupShare Console
Trados GroupShare Console
Trados GroupShare Console features
Opening Trados GroupShare Console
Trados GroupShare Console settings
Specifying the MultiTerm server message language
Setting up execution server threads
Set up translation providers from the Console
Granting permissions automatically
Changing file storage location
Changing settings for project archiving
Setting up project detaching
Changing the external server address
Renaming default phases
Specifying project server notification settings
Specifying or updating the database login details
Checking service status
Available Trados GroupShare services
Customize password complexity rules
Activating licensing
Services (Local)
Changing the account used by Trados GroupShare services
Managing termbase data on the host
SQL Server Management Studio
Log files
Database backup
Supported languages
Licensing
Licensing videos
Working with single-user and network licenses
The Activation Server
The License Server
Activating Trados GroupShare
Single-user licenses
Activating single-user licenses online (activation code)
Activation codes for single-user licenses
Getting an activation code
Activating your product online with a single-user license
Deactivating your product online for a single-user license
Moving single-user license to another computer
Moving single-user license to another computer via Internet
Moving single-user license to another computer without Internet
Activating single-user licenses offline
Installation IDs
Activation certificate
Activating your product offline with a single-user license
Deactivating your product offline with a single-user license
Viewing your deactivation certificate offline for a single-user license
Network licenses
Activating the Trados License Manager (administrators)
Prerequisites for installing the Trados License Manager
Installing the Trados License Manager
Setting up IPv6 connection for Trados License Manager
Activating Trados License Manager online
Activating a network license with Trados License Manager online
Removing a network license from Trados License Manager Manager online
Activating Trados License Manager offline
Activating a network license with Trados License Manager offline
Removing a network license from Trados License Manager offline
Monitoring clients and license information
Configuring available product editions
Product editions and features
Connecting to the Trados License Manager (users)
Connecting to Trados License Server to consume a network license seat
Disconnecting from Trados License Server to free up a license seat
Borrowing a network license from Trados License Server
Returning a borrowed network license to Trados GroupShare
Changing Trados License Server details
Modifying your proxy settings
Viewing your license status
Error message solutions
Activation Failed - The license is already registered
Activation Failed - Cannot connect to activation server
Network License errors - Retry button
Application Server - restart options
Problems and solutions
You cannot access a resource although you have the permissions
You can access a resource although you do not have the permission
You cannot add database server (authentication issues)
You cannot specify a windows user in add user
Defined field is not in project TM
Main TMs are not updated
Unable to discover an endpoint supporting windows authentication for service identity.svc
Glossary

You might also like