SDL Trados Studio
SDL Trados GroupShare
SDL Trados Business Manager
SDL Trados Live
SDL Speech to Text
SDL Managed Translation - Enterprise
Translation Management Connectors
SDL LiveContent S1000D
SDL Contenta S1000D
SDL Tridion Docs
SDL Tridion Sites
SDL Content Assistant
SDL Machine Translation Cloud
SDL Machine Translation Connectors
SDL Machine Translation Edge
Tridion Docs Developers
SDL User Experience
Language Products - GCS Internal Community
SDL Community Internal Group
SDL Access Customer Portal
SDL Professional Services
SDL Training & Certification
Language Technology Partner Group
SDL Academic Partners
SDL Enterprise Technology Partners
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic SDL Tridion Docs User Group
SDL Tridion UK Meetup
SDL Tridion User Group New England
SDL Tridion West Coast User Group
SDL WorldServer User Group
Tridion Docs Europe & APAC User Group
Tridion User Group Benelux
Tridion User Group Ohio Valley
SDL MultiTerm Ideas
SDL Passolo Ideas
SDL Trados GroupShare Ideas
SDL Trados Studio Ideas
SDL Machine Translation Cloud Ideas
SDL Machine Translation Edge Ideas
SDL Language Cloud TMS Ideas
SDL Language Cloud Terminology Ideas
SDL Language Cloud Online Editor Ideas
SDL Managed Translation - Enterprise Ideas
SDL TMS Ideas
SDL WorldServer Ideas
SDL Tridion Docs Ideas
SDL Tridion Sites Ideas
SDL LiveContent S1000D Ideas
SDL Contenta S1000D
SDL XPP Ideas
Events & Webinars
To SDL Documentation
To SDL Support
What's New in SDL
Detecting language please wait for.......
In SDL TMS, a Vendor is a localization service provider to an organization. In most cases, the vendor will be providing translation and/or linguistic review services to the organization. If the Vendor is not marked as private, they can also provide these services to child organizations. When creating a Vendor in SDL TMS, the following information is required:
To use Vendors in an Organization, you must define a Workflow that has Vendor-enabled steps. Any Workflow Step that is not performed by the system can be Vendor-enabled, except for Authorization and Recovery. When authorizing a Job, the Project Manager can assign Tasks from the same Job to different Vendors. However, it is not possible to assign one Task to multiple Vendors.
For more information on setting up Vendors and configuring Workflows, please refer to chapter 10 in the SDL TMS Administrator Guide which is available online by visiting https://docs.sdl.com/.
With the release of SDL TMS 12.4, the functionality for Vendors has been revisited to provide a more flexible solution. In previous versions of SDL TMS, specific checks were made to restrict the information and functionality that a Vendor User could access. In SDL TMS 12.4, these specific checks have been replaced with permission checks so that Vendor Users can be granted permissions based on the Vendor Groups that they belong to.
A Vendor is assigned to a Task if one of the following conditions are met:
A Vendor is assigned to a Job if there is at least one Task in the Job that is assigned to the Vendor.
A Vendor User can see a Project if:
Vendors can see Organizations where they have (or have previous had) access to a non-archived Job. Vendors can also see Organizations that are between their parent Organization and any Organization with a relevant Job.
A Vendor User who has permission to create Jobs will:
When a Job is assigned only to a single Vendor, a Vendor User can see all the costs associated with the Job. In addition, when a Vendor User views the details of the Job, the word count pie chart will only show information relating to the relevant Tasks and Languages for that Vendor.
A Vendor with suitable permissions can edit their own Vendor and modify User/Group assignment and supported Language Pairs. Vendor Users will not be able to change the Users or Cost Models assigned to their Vendor. Vendor Users with enough permissions can create additional Users and these new Users will be automatically added to their Vendor.
Regardless of the permissions granted to a Vendor user, they will never have visibility of other Vendors on the system.
Vendors can only see and edit Configurations where they are the only Vendor.
A Vendor User with permission to run standard SDL TMS reports will not see any information relating to other Vendors.
The logic that determines whether a Cost Models, Group, User, Language Pair or Language Group is in use now additionally considers whether the object is in use by a vendor.