• Replies 3 replies
  • Subscribers 47 subscribers
  • Views 1925 views
  • Users 0 members are here
Options
Related

Multiterm administrator 2015 - user lists in roles

Bruno Ciola

Hi all,

I know SDL will suggest an upgrade to GS 2017, but if you ever should consider a Multiterm Administrator 2015 update, please:

- list users in each role alphabetically (not chronologically): when you are looking for a user, you have to read the whole list;

- enlarge the windows used for assigning users to a role: only 10 users are visible, if you have lots of users you must scroll up and down many times.

Regards,

Bruno
Rate translation
×
Suggest better translation
×
Parents
  • Hi Bruno,

    Thank you for your feedback. Unfortunately we have no plans to change functionality in MT Admin 2015.

    One of the key goals of GS 2017 was to make User Management easier by moving most of it into the GroupShare WebUI, which shows you much more users, lists alphabetically etc.

    Thanks,
    Luis

    Best regards,
    Luis Lopes | Principal Product Manager | RWS | (twitter) @Luis___Lopes |

  • in reply to Luis Lopes
    Hi
    Could you please explain the function of GroupShare Roles in Multiterm Administrator?
    My logic tells me, that if some users of GroupShare are part of certain role (like Internal Translator), if I add this role in Restrictions -> Expert Users, instead of the name of the user, all users that have this role in GroupShare would be added as Expert Users. But it does not work. Therefore I am asking myself which is the purpose of GroupShare roles in Multierm Administartor.

    Thank you for your help,
    Angelo
  • in reply to Angelo Caltagirone
    Hi all,

    Since GroupShare 2017 access to termbases is completely managed from GroupShare using Organizations and Roles in GroupShare, exactly as it works for TMs. MT Administrators does not decide anymore if a user can see a termbase or not.

    Restrictions in MultiTerm Administrator, now only manage:
    - Further granular permissions on language or entry class level
    - Access to specific custom objects (Filters, Layouts, Input models)

    It does not guide anymore if a user can see a termbase or not.
    Adding a GS role to a restriction makes it easier to assign the above Restrictions to a GS role rather than have to add individual users.
    You also don't have to add users to restrictions in MT Administrator to provide access, it's all guided by GS Roles and Organizations, to make user management easier.

    Thanks,
    Luis

    Best regards,
    Luis Lopes | Principal Product Manager | RWS | (twitter) @Luis___Lopes |

Reply
  • in reply to Angelo Caltagirone
    Hi all,

    Since GroupShare 2017 access to termbases is completely managed from GroupShare using Organizations and Roles in GroupShare, exactly as it works for TMs. MT Administrators does not decide anymore if a user can see a termbase or not.

    Restrictions in MultiTerm Administrator, now only manage:
    - Further granular permissions on language or entry class level
    - Access to specific custom objects (Filters, Layouts, Input models)

    It does not guide anymore if a user can see a termbase or not.
    Adding a GS role to a restriction makes it easier to assign the above Restrictions to a GS role rather than have to add individual users.
    You also don't have to add users to restrictions in MT Administrator to provide access, it's all guided by GS Roles and Organizations, to make user management easier.

    Thanks,
    Luis

    Best regards,
    Luis Lopes | Principal Product Manager | RWS | (twitter) @Luis___Lopes |

Children
No Data