Introduction

The purpose of this article is to answer common questions about the Subcontracting module (LSPs) in XTM Cloud. and to help resolve issues you might experience with it.

...

Once both sides have specified all the information correctly, and clicked the Save button, a green message should be displayed, confirming that a two-way connection has been established.

...

If the connection details are missing or incorrect, and a user clicks the Save button, a yellow message should be displayed, informing them:

...

Why is it not possible to start the project on the LSP side when the LSP has been assigned to the first step in the project’s workflow?

If a yellow border is displayed in the project’s workflow on the LSP (contractor) side, when the LSP has been assigned to the first workflow step, this indicates that the project has simply not been started on the contractor’s side.

...

However, after the project is created in XTM Cloud, the change of this setting is not passed automatically on to the LSP side. If the contractor enables it after the project is created, the LSP also needs to enable it on their side to be able to unlock the ICE-matched segments.

Some of the Subcontractor’s linguists cannot log into the XTM platform. What might be the reason for this?

In the case of subcontracted-only accounts, the root cause of this issue might be that the Contractor has reserved most of his licenses for internal use, which leaves less available licenses for LSPs. In other words, Licenses shared amongst LSPs might have simply run out, causing problems on your side.

To prevent this for happening in the future, your Contractor would have to access Configuration → Settings → System → Licenses → Licenses, and change the value of the licenses allocated to internal users to a smaller number than there is currently.

...