Team, Ultimate and Enterprise editions
Get in touch with Sales for licensing questions.
Sharing allows the sharing of resources between different organizations as defined in Memsource. One organization creates a project and then shares that project or selected jobs with another organization. Shared resources can be searched by clicking Search shared space on the page.
Sharing is a connection between two cooperating organizations: a Buyer and a Vendor. These roles are not fixed to an organization but describe the relationship between them for a specific resource. In some projects, an organization can act as a Buyer, while for others it can act as a Vendor.
A Buyer is an organization with an account in Memsource that can assign projects to other organizations (vendors) in Memsource. To act as a Buyer, the Team (or higher) edition is required.
A Vendor is an organization that can be assigned projects or jobs by other organizations (Buyers). All paid editions of Memsource can function as a vendor. It is possible to act as a Vendor starting with the Team Start (or any higher) edition.
Vendors have their own accounts in which they can create and edit projects, translation memories and term bases.
Vendors can accept shared projects or jobs from translation buyers. They can attach their own translation memories and term bases and use these resources in addition to the resources attached by the project owner.
Vendors can split files, run their own analyses, assign files within their teams, or even further sub-contract work to other partners.
A Buyer needs to establish the Vendor connection before sharing projects or jobs with them. The Vendor organization needs to provide its Vendor Token to the Buyer in order to set it up.
To set up a Vendor Connection, follow these steps:
From the Vendor organization, go to the Setup page, scroll down to the section and copy the .
From the Buyer organization, From the Setup page, scroll down to the section and click on Vendors.
Apply, and Relevancy information if applicable.
Projects can now be shared between the Vendor and the Buyer and jobs can be shared with one or multiple Vendors.
A shared project enables separate organizations to collaborate using their own Memsource resources such as translation memories, term bases, and users.
A corporate Memsource customer sharing a project with a translation company.
A Multi-Language Vendor sharing projects with Single-Language Vendors.
A translation company sharing projects with Memsource users who have a Team Start account, instead of only being able to assign them to Linguist users.
To share a project:
From a Share and select or .page, click
On the .page, the shared project is indicated with
To stop sharing a project with a Vendor, follow these steps:
When a Buyer organization creates a new Vendor, a Buyers list is displayed for the vendor organization under its Setup. The connected Buyer organizations are listed and the Vendor can select a default project owner for each Buyer.
Shared projects always have two project owners:
Buyer project owner
Vendor project owner
Project ownership can be transferred from Vendor to Buyer if the Vendor creates a project and then shares it ex-post with a Buyer.
A fairly open framework for collaboration that is based on mutual trust between the Buyer and the Vendor is provided.
Few actions are locked in the relationship and unwanted or mistaken actions can be reverted.
The Buyer has a full right to the project and all Buyer's resources (TM/TB, MT engine, etc.)
The Buyer may not Edit, Export, or Unselect Vendor's TMs/TBs.
The Buyer is not able to see the names of Vendor Linguists but can see the job status set by the Vendor's Linguist.
The Buyer can see and download Vendor's Analyses, but is not able to edit them or use them to create Quotes.
The Vendor may not:
Delete a shared project.
Modify project machine translation settings.
Edit, Export, or Unselect a Buyer's TMs/TBs.
See the names of Buyer's Linguists.
Edit Buyer's Analysis or use it to create a Quote
The Vendor may:
Create/edit/delete jobs, analyses, and reference files.
Add subsequent Workflow Steps (Vendor Workflow Steps need to have higher hierarchical order).
Assign Vendor Linguists to jobs.
Add Vendor TMs/TBs.
Share jobs with other Vendors.
See and download Buyer's Analysis.
When a Vendor deletes an item in a shared project, both the Buyer and Vendor will be able to undelete it from the Recycle Bin.
When a Buyer deletes an item in a shared project, only the Buyer will be able to undelete it.
In shared projects, generated email communication is only sent between the two directly connected parties.
The Buyer shares the project.
Vendor1 gets a Shared Project email.
Vendor1 accepts the project.
The Buyer will then get a Project status changed email.
Vendor1 assigns/emails a job to Vendor2.
Vendor2 will get a New Work email.
Vendor2 accepts the job.
Vendor1 then gets a Job accepted email.
Vendor2 sets the job to Completed.
Vendor1 will get a Job completed email.
Vendor1 sets the project to Completed.
The Buyer gets a Project status changed email.
A Buyer and a Vendor collaboration typically involves a Buyer initiating a project and then sharing it with the Vendor. There are instances when it is the Vendor who initiates the project and then needs to turn it into a shared project ex-post.
An existing project created by a Vendor can be turned into a shared project owned by the Buyer and shared with the Vendor. The Buyer will be notified of the new shared project when it is transferred.
To transfer a project from a Vendor to a Buyer, follow this step:
When multiple Vendors need to be used for a project, the jobs within that project can be shared.
To assign jobs to Vendors, the Use Vendors for projects option must be enabled on the project level under Access and Security.
Inactive linguists do not appear as available in shared jobs.
A corporate Memsource customer (Buyer) shares jobs within a project with multiple Vendors where different Vendors are responsible for different target languages.
A Buyer picks a lead Vendor and shares the project with them. The lead Vendor can then work with multiple sub-Vendors. This would be a combination of a shared project and shared jobs within the same project.
An MLV (Multi-Language Vendor) assigns jobs to SLVs (Single-Language Vendors). This is typically based on target language specialization.
A project is shared with one Vendor and jobs in the same project are shared with another Vendor. Sharing the project and its jobs with the same Vendor would not be possible.
A vendor connection must be established before being able to share a job.
To share a job and assign it to a Vendor, follow these steps:
Shared jobs are more Buyer-driven. Vendor rights in a shared job are limited in comparison to shared projects.
The Buyer has full Project Management rights in a shared project.
The Buyer is not able to see the names of the Vendor's Linguists but can see the job's status set by the Vendor's Linguist.
The Buyer can neither see nor access the Vendor's TM and TB (if the Vendor added any to the job), nor see the matches coming from these in the Editors.
The Buyer is not able to edit the Vendor's Analysis or use it to create a Quote.
The Vendor may:
See only the jobs assigned to the Vendor by the Buyer.
See analyses assigned to the Vendor by the Buyer (that the Buyer created).
See Buyer's Domain and Subdomain (but not buyer's Client, Cost Center and Business Unit)
Add their own TM.
Add their own TB.
Split and join jobs.
Assign shared jobs to the Vendor's Linguists.
Only active linguists appear when adding Provider to a job.
The Vendor may not:
See jobs that are not directly assigned to them.
See Buyer's analyses that are not assigned to them.
Change the settings of the Buyer's translation memory or term base within the project.
Edit or export Buyer's TMs/TBs.
In shared jobs, all parties will get a notification about every Accepted or Completed job changes.
The Buyer shares a job with Vendor1, and Vendor1 then shares that job with Vendor2.
The job has to be not only Assigned, it must also be emailed.
The Buyer shares a job with Vendor1.
Vendor1 gets a New work email from the Buyer.
If Vendor1 accepts the job.
The Buyer gets a Job Accepted email from Vendor1.
Vendor1 then shares the job with Vendor2.
Vendor2 gets a New Work email from Vendor1.
Vendor2 Accepts the job.
Vendor1 gets a Job Accepted email from Vendor2 and the Buyer gets a Job Accepted email from Vendor1.
Vendor2 Completes the job.
Vendor1 gets a Job Completed email from Vendor2 and the Buyer gets a Job Completed email from Vendor1.
Step 2 can be skipped: Vendor1 can share the job with Vendor2 without accepting it first. If this happens, the Buyer would receive only 1 Job Accepted email after Vendor2 accepted it.