Documentation Center

Managing MultiTerm restrictions

Administrators can restrict the actions Trados GroupShare users can perform over a server-based termbase

MultiTerm has two predefined roles - Expert User and Public - which consist of a set of predefined permissions. The two roles are inherited by Trados GroupShare. You can further restrict the two MultiTerm permission set, from the Restrictions section of each server-based termbase in MultiTerm.

Here is how the Expert User and Public roles fit in the Trados GroupShare - MultiTerm integration:
  1. Trados GroupShare inherits theExpert User and Public roles from MultiTerm.
  2. Trados GroupShare offers administrators the possibility to check the permissions associated to the MultiTerm roles.
  3. Administrators set up users in Trados GroupShare and assign them an MultiTerm role (usually, the MultiTerm Guest role).
  4. (Optional) Administrators log in to MultiTerm and add the Trados GroupShare users to the MultiTerm user list. In MultiTerm, administrators can further restrict users' access to MultiTerm objects: layouts, import/export definitions, filters and input models. Whenever you add a user to a termbase in MultiTerm, they are automatically added to the predefined Public restriction.

If a user is not in a restriction

Whenever you add a user to the Users list, they are automatically added to the predefined Public restriction. If a user is not in a restriction, no termbases are available when logging in from a MultiTerm component.

Expert user restriction

An Expert User restriction is automatically created for a termbase when the termbase is created and you cannot delete it.

The Expert User restriction has read, write and delete access to all entries in the termbase, and to all fields in the entries. The Expert User can also import and export termbase data.

The termbase creator is a default member of the Expert User restriction as well as the Super user. You can remove all users except the Super user from this restriction.

Public restriction

A Public restriction is created in a termbase when the termbase is created, and you cannot delete it.

The Public restriction has read access to all entries in the termbase, and to all fields in the entries.

When you add a user to a termbase, the user is automatically made a member of the Public restriction.

The Guest user is always a member of the Public restriction. You can remove all users from this restriction except the Guest user.