Trados Live Essential/Live Team/Enterprise
Trados Business Manager
Language Weaver Connectors
Language Weaver Edge
Tridion Docs Developers
RWS User Experience
Internal Trados Ideas Community
RWS Community Internal Group
RWS Professional Services
RWS Training & Certification
RWS Enterprise Technology Partners
Trados Approved Trainers
ETUG (European Trados User Group) Public Information
Nordic Tridion Docs User Group
Tridion UK Meetup
Tridion West Coast User Group
Trados Studio Ideas
Trados GroupShare Ideas
Trados Live Team Ideas
Trados Live Essential Ideas
Trados Live Terminology Ideas
Trados Enterprise Ideas
Trados Online Editor Ideas
Trados Business Manager Ideas
RWS Appstore Ideas
Tridion Docs Ideas
Tridion Sites Ideas
Language Weaver Ideas
Language Weaver Edge Ideas
Managed Translation - Enterprise Ideas
LiveContent S1000D Ideas
Events & Webinars
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 Customer.
This role should be assigned to all user accounts created for customer who will be able to access portal for customers. In addition to a role, Associated customer field must be filled for such users. By default, Customer role allows customers to:
You are fully free to change default permissions defined in the Customer role. However, if you unintentionally remove permissions which are mandatory for correct working of a customer'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 Customer 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 the Customer role.
This means that even if navigation permission allows to open translation project list, attempt to do this will lead to fully empty list of projects, because it is not allowed to read (nor write, create and delete) 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 Customer 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
[Id] = CurrentUserVendorOrClientId()
Allow Read and Write
Access to own customer profile
[Title] = 'Vendor performance'
Allows to view only one QuickReport named 'Vendor performance'
To deliver files and invoices
Linked with File attachment table
Fuzzy scheme detail
[Customer.Id] = CurrentUserVendorOrClientId()
[Invoice.Customer.Id] = CurrentUserVendorOrClientId()
Model difference aspect
Used to store individual user settings (column in tables, etc.)
Needed to send notifications to users
[Payment.Customer.Id] = CurrentUserVendorOrClientId()
Allows to read own price-list. Write permission allows to make changes in background, editing in UI is prohibited.
[Quote.Customer.Id] = CurrentUserVendorOrClientId()
Access to own quotes
Needed for viewing reports
Allows to create entries in the calendar in background when new jobs are created
Read application settings
Translation job task
Translation job receivable
[Translation job.Customer.Id] = CurrentUserVendorOrClientId()
Allow read and write
Allows to view translation jobs which belong to a customer
Allows to view and create translation projects which belong to a customer
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
As you see, two functions were used in the Object permissions column: CurrentUserVendorOrClientId() and CurrentUserId(). Description of these functions can be found in the Default Vendor role article.