...
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 inform the LSP in Workflow editor about any discrepancies in due dates applied to workflow steps between the Contractor and the LSP:  |
Other than that, the LSP can also add their own workflow steps to a project workflow.
...
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 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 XTM Workbench segment filters: Modification: Any updates to target, status or comments (click here 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 entire workflow in the Workflow editor. They can only add new workflow steps, and change blocking mechanism criteria between existing steps.
...