| Table of Contents |
|---|
| Page Properties | ||
|---|---|---|
| ||
Introduction
LSP (Language Service Provider) is just another name for a subcontractor→ : a third-party company who that has their its own XTM Cloud instance which is connected to the Contractor's account and from whom which it receives translation projects.
At this point, there is an important remark to be made with regard to Important point about the two meanings of the term "Subcontractor".
The first one meaning refers to a separate type of subscription in XTM Cloud that is simply called “Subcontractor". Clients with this subscription cannot create projects on their account or store their own TM/terminology resources. They can only work on projects received from the Contractor and use the Contractor's resources.
This article, however, describes the possibilities and constraints affecting a "standard” client who that receives a translation project from the Contractor, acting as a subcontracting party – a : the second meaning for that particular term“Subcontractor".
...
LSP project restrictions resulting from Contractor settings
Generally speakingIn principle, the an LSP can do as much as their Contractor will let permits them to do in a subcontracted project, as it is all set up specified in the Contractor settings in the main Contractor’s XTM Cloud instance and, in . In most cases, those these settings are nowhere to cannot be changed on anywhere in the LSP side’s XTM Cloud instance.
LSP access rights
The most important settings for the an LSP are located in an Administrator-managed LSP profile on in the Contractor Contractor’s XTM Cloud instance (Users → LSPs → LSP editor → Access rights).
Here In the LSP editor, the Contractor can, for example, specify:
the customers to whose projects the LSP can be assigned,.
LSP level of access to LQA results and reports (see Types of LQA report – description and use case for more information);.
the customers whose terminology resources the Contractor can permit the LSP is permitted to use (if selected by the Contractor’s Project Manager at the project creation stage),.
extent of terminology management: what the extent to which the LSP can actually do with Contractor terminology,manage the Contractor’s terminology.
the customers whose translation memory (TM) resources the Contractor can permit the LSP is permitted to use (if selected by the Contractor’s Project Manager at the project creation stage),.
extent of the extent to which the LSP can manage the Contractor’s translation memory (TM) management: what the LSP can actually do with Contractor TM.
...
Workflow and access
The second place in which the LSP rights are defined is the Contractor global settings (Configuration → Settings → Translation → Workflow and access).
The naming convention for Although the names of some of the sections it contains might seem unclear (for example, Linguist general options) but they might suggest otherwise, the settings in them do apply for LSPs as well . In other words, all the settings displayed there also apply for LSPs as, in the context of assigning actors to a workflow, the term "linguist" also refers to subcontractors. The Linguist metadata access section is the only section in which a distinction is made between "Linguists" (internal linguists) and LSPs (subcontractors).
The only other option that has been designed is 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
...
Which settings can
...
an LSP not
...
configure or modify?
The vast majority of the options the settings contained in the sections listed below, relating to a specific project that , are configured during its creation apply for the LSP (project creation stage): the sections such as:when it is created and apply for an LSP. The settings in these sections can only be set or adjusted by the Contractor and the LSP cannot change them in any way:
General information (i.e. customer, project template),.
Translation (i.e. source language and target languages, filter template, QA profile, file-joining files, segment filter profile, pre-processingpreprocessing, subject matter, source files, additional files (reference material, segment ID, images)),.
Settings (i.e. customer TM and terminology resources, anonymization, disabling of term decoration, using use of not approved memory, marking of certain segments as “locked”, monitoring of target length);.
Machine translation (all settings),.
Tag settings (all settings).
The settings contained in the above-mentioned sections can only be set or adjusted by the Contractor, and the LSP cannot change them in any way.
There are some options in 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 , there are some options that seem to be available for selection, but 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.
What can the LSP do?
...
LSP-configurable project settings
In the Project Editor → > General info section of a subcontracted project, on the LSP side (if enabled in the global settings by the LSP), there are some options that are available for selection/editing. However, they 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, in the Workflow editor, a system message will inform the LSP in Workflow editor about any discrepancies in due dates applied to workflow steps between the Contractor and about if the due date set for a workflow step by the Contractor does not match the due date set for it by the LSP:  |
Other than that, the LSP can also add their own workflow steps to a project workflow.
...
LSP project restrictions independent of Contractor settings
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 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 have created within the framework of this that project.
The LSP cannot force projects to be finished/re-opened.
The LSP cannot approve ICE and or Leveraged matches.
The LSP cannot download a project (general) LQA report (see Types of LQA report – description and use case for more information).
The LSP does not have access to one of the XTM Workbench segment filters: Modification: Any updates to target, status or comments (see Changing the filter view – modification: Any updates to target, status or comments for more information).
...
Restriction for Contractors
The only restriction that appears on the Contractor side is that, once they assign an LSP to a particular workflow step, they can neither remove nor modify that the entire workflow in which it occurs, in the Workflow editor. They can only add new workflow steps, and change blocking mechanism criteria between existing steps.
...