Trados Business Manager
Speech to Text
Managed Translation - Enterprise
Translation Management Connectors
Language Weaver Connectors
Language Weaver Edge
Tridion Docs Developers
RWS User Experience
Internal Trados Ideas Community
RWS Community Internal Group
RWS Access Customer Portal
RWS Professional Services
RWS Training & Certification
RWS Enterprise Technology Partners
Trados Academic Partners
Trados Approved Trainers
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic Tridion Docs User Group
Tridion Docs Europe & APAC User Group
Tridion UK Meetup
Tridion User Group Benelux
Tridion User Group New England
Tridion User Group Ohio Valley
Tridion West Coast User Group
WorldServer User Group
Trados GroupShare Ideas
Trados Studio Ideas
Language Weaver Ideas
Language Weaver Edge Ideas
RWS Language Cloud TMS Ideas
RWS Language Cloud Terminology Ideas
RWS Language Cloud Online Editor Ideas
Managed Translation - Enterprise Ideas
Tridion Docs Ideas
Tridion Sites Ideas
LiveContent S1000D Ideas
Events & Webinars
To RWS Documentation
To RWS Support
Detecting language please wait for.......
In addition to Admin and User default roles, SDL Trados Business Manager has a predefined role called Vendor.
This role should be assigned to all user accounts created for vendors who will be able to access their area on the web-portal. In addition to a role, Associated vendor field must be filled for such users. By default, Vendor role allows vendors to:
Translators cannot edit assignments. They only can change status of assignments by clicking Delivery or Register invoice buttons. After registering an invoice delivery buttons and invoice creation buttons become disabled.
You are fully free to change default permissions defined in the Vendor role. However, if you unintentionally remove permissions which are mandatory for correct working of a vendor's portal, then application will automatically return these permissions after clicking Save button in the role editing window.
Below you will find explanation of every permission setting in the Vendor role.
While navigation permissions control contents of the navigation tree and do not control access right to actual data, type permissions serve exactly for this - to define a data allowed/denied to be read, written, created or deleted by users with this role. By default access to all data is denied in Vendor role:
This means that even if navigation permission allows to open translation assignments list, attempt to do this will lead to fully empty list of assignments, because it is not allowed to read (nor write, create and delete) and data. So, the task of Type permissions table is to define what is allowed to read/write/create/delete. In this list you can see what is allowed by default in the Vendor role:
Change password on first logon
Criteria: [Oid] =
Needed to allow user to change own password
Read permission for all users is needed to determine users for sending notifications
[Title] = 'Vendor performance'
Allows to view only one QuickReport named 'Vendor performance'
[Assignment] Is Not Null And [Assignment.Vendor.Id] = CurrentUserVendorOrClientId()
Allow read and write
To deliver files and invoices
Linked with File attachment table
Fuzzy scheme item
Invoice incoming item
Model difference aspect
Used to store individual user settings (column in tables, etc.)
Needed to send notifications to users
[Vendor] Is Not Null And [Vendor.Id] = CurrentUserVendorOrClientId()
Needed for viewing reports
Read application settings
1. Criteria: [Vendor.Id] =
2. [Vendor] Is Null And [Vendor pickup][[Vendor] Is Not Null And [Vendor.Id] = CurrentUserVendorOrClientId()]
Criteria sets rights on reading and writing only those assignments which are created for logged in vendor, as well as assignments offered to a vendor
[Vendor.Id] = CurrentUserVendorOrClientId()
Explicitly deny access to Translators pickup tab in assignments, but allows to accept and decline assignments
Translation job task
Needed to allow to view fuzzy type, unit and work type in assignments, because tasks in assignments are based on job tasks
Criteria: [Id] =
Allows to read and write only logged in vendor
As you see, two functions were used in the Object permissions column: CurrentUserVendorOrClientId() and CurrentUserId().
CurrentUserVendorOrClientId() function returns Id of a vendor or customer which is linked with a logged in user. This vendor or customer is specified in the Associated vendor or Associated customer in the Users table.
CurrentUserId() function returns Id of the logged in User.
Let's check criteria used to access translation assignments:
Criteria: [Vendor.Id] = CurrentUserVendorOrClientId()
Read, Write, Create and Delete properties are not set. This means that it is denied to access translation assignments table. But in the Object permissions table a row is created which allows to read and write assignments which meet provided criteria. And this criteria sets that Id of a Vendor selected in assignment must equal to Id of a currently logged in vendor.
Visual designer can help you to build this criteria, but you have to manually type name of a function after equity symbol: CurrentUserVendorOrClientId().
By modifying Vendor role you can provide more rights to your vendors or for individual vendors (in this case, Criteria property will look like [Vendor.FullName] = 'Peter Blake').