...
LSP (Language Service Provider) is just another name for a subcontractor → a third-party company who has their own XTM Cloud instance which is connected to the Contractor’s Contractor's account and from whom receives translation projects.
At this point, there is an important remark to be made with regard to the two meanings of the term “Subcontractor”"Subcontractor".
The first one refers to a separate type of subscription in XTM that is simply called “Subcontractor”“Subcontractor". Clients with the aforementioned this subscription cannot create projects on their account by themselves or store their own TM/terminology resources - they . They can only work on projects received from the Contractor and with the use of Contractor’s use the Contractor's resources.
This article, however, aims at describing describes the possibilities and constraints put onto affecting a “standard” "standard” client who receives a translation project from the Contractor, thus acting as a subcontracting party - a second meaning of the term in questionfor that particular term.
...
LSP project restrictions resulting from Contractor settings
Generally speaking, the LSP can do as much as their Contractor will let them do in a subcontracted project, as it is all set up in the Contractor settings in the main XTM Cloud instance and, in most cases, those settings are nowhere to be changed on the LSP side.
...
The most important settings for the LSP are located in an LSP profile on the Contractor instance (Users → LSPs → LSP editor → Access rights).
Here the Contractor can define such items as, for example, specify:
customers to which whose projects the LSP can be assigned;,
accessibility LSP level of access to LQA results and reports for the LSP (click here for more information);
customers whose terminology resources the Contractor can allow permit the LSP to use (if selected at the project creation stage);,
extent of terminology management - : what the LSP can actually do with Contractor terminology;,
customers whose translation memory (TM) resources the Contractor can allow permit the LSP to use (if selected at the project creation stage);,
extent of translation memory (TM) management - : what the LSP can actually do with Contractor TM.
...
Workflow and access
The second place wherein in which the LSP rights are defined are is the Contractor global settings (Configuration → Settings → Translation → Workflow and access).
The naming convention of for some of the sections contained therein it contains might seem to be confusing unclear (for example, Linguist general options) but they do apply to for LSPs as well. In other words, all the settings displayed there also take effect to LSPs since apply for LSPs as, in the context of assigning actors to a workflow, the term “linguist” "linguist" also refers to subcontractors. The Linguist metadata access section is the only section in which a distinction is made between “Linguists” "Linguists" (internal linguists) and LSPs (subcontractors).
Other than that, the The only other option that was has been designed specifically for LSPs is Show Customer name on LSP account in the Linguist general options section.
...
| Note |
|---|
IMPORTANT! The Allow linguists to download → |
Project settings
What
...
can the LSP not do?
Last but not least, the The vast majority of the options pertaining relating to a given specific project that are configured during its creation are valid to apply for the LSP (project creation stage) - : the sections such as:
General information (i.e. customer, project template);,
Translation (i.e. source language and target languages, filter template, QA profile, joining files, segment filter profile, pre-processing, subject matter, source files, additional files (reference material, segment ID images));,
Settings (i.e. customer TM and terminology resources, anonymization, disabling term decoration, using not approved memory, marking certain segments as “locked”, monitoring target length);
Machine translation (all settings);,
Tag settings (all settings).
The settings contained in the above-mentioned sections can only be regulated set or adjusted by the Contractor, and the LSP cannot change it them in any way.
There are some options in the Project Editor → General info section of a subcontracted project on the LSP side (if enabled in the global settings by the LSP) which seem to be available for selection, but their potential change will not bring about any any changes to them will have no effect:
Translation memory settings:
Use not approved memory,Hide repeated segments,Mark segments as locked when:,Disable term decoration,Allow editing of ICE segments;Machine translation settings.
...
There are some options in the Project Editor → General info section of a subcontracted project on the LSP side (if enabled in the global settings by the LSP) which that are available for selection/editing. However, but they serve more as are primarily internal information/guidelines and have no direct effect on the project as a whole (the Contractor settings take priority):
Project name;,
Description;,
Reference ID;,
Payment status;,
Proposal approval status;,
Project Manager;,
Custom fields;,
Due dates (i.e. workflow start date, workflow due date, delivery due date);
As for due dates, the system will make sure to inform the LSP in Workflow editor about any discrepancies in due dates applied to workflow steps between the Contractor and the LSP:  |
...
LSP project restrictions independent of Contractor settings
Irrespective of the settings imposed No matter what settings have been specified by the Contractor, the LSP also faces other restrictions that are set by default and expected in the case of subcontracted projects.
The LSP does not have access to the Project editor → Estimates section.
The LSP cannot re-analyze reanalyze projects.
The LSP cannot archive projects.
The LSP has the option to delete the project on their side but cannot delete TM that they created within the framework of this project.
The LSP cannot force projects to be finished/re-opened.
The LSP cannot approve ICE and Leveraged matches.
The LSP cannot download a project (general) LQA report (click here for more information).
The LSP does not have access to one of the Workbench segment filters: Modification: Any updates to target, status or comments (click here for more information).