Hi Luis

Sorry to come back on this subject, but we are facing a major issue with these predefined roles.

These predefined roles all give write access to TUs. There are no differences at all between the access rights of the role "Translator" and the role "External Translator" regarding TMs and TUs.

It is standard practice that external translators are granted only read access when the review of translated documents is done internally.

As there is no single predefined role that has only read access and given that we cannot modify roles or create new roles, I would like to know how we should address this problem.

Walter

Hi Luis

Working only with Project TMs is one possible approach, but it strongly limits the possibilities of the external translator to carry out concordance searches because of the limited content of the Project TM.

This is why many companies give their external translators read access to the full TM, so that they can run useful concordance searches.

I don't understand why the rights of these roles have been changed in GS Cloud compared to the standard GS server, where the role "External translator" only gives read access to TUs. 

Why should this be configured differently in GS Cloud than in standard GS?

Even if it was different, we could live with it, but the main problem is that all roles have write access to TUs. What should we do if we don't want external translators to modify the TM? Unless I overlooked something, there is currently no way to prevent this and I think this should definitely be changed.

Walter

Hi Luis

Working only with Project TMs is one possible approach, but it strongly limits the possibilities of the external translator to carry out concordance searches because of the limited content of the Project TM.

This is why many companies give their external translators read access to the full TM, so that they can run useful concordance searches.

I don't understand why the rights of these roles have been changed in GS Cloud compared to the standard GS server, where the role "External translator" only gives read access to TUs. 

Why should this be configured differently in GS Cloud than in standard GS?

Even if it was different, we could live with it, but the main problem is that all roles have write access to TUs. What should we do if we don't want external translators to modify the TM? Unless I overlooked something, there is currently no way to prevent this and I think this should definitely be changed.

Walter