Versionen im Vergleich

Alte Version 3

changes.mady.by.user Diana Schoppe

Gespeichert am

verglichen mit

Neue Version Aktuell

changes.mady.by.user Diana Schoppe

Gespeichert am

Schlüssel

  • Diese Zeile wurde hinzugefügt.
  • Diese Zeile wurde entfernt.
  • Formatierung wurde geändert.

Assign views before you start working with TermTiger. If you are using several TermBases, the views must be defined individually for each TermBase.

Preparation

  • Get an overview of the existing groups. If necessary, create additional groups in Congree Control Center - User.

  • Determine the requirements:
    - Do certain groups want to see less or more details?
    - Are you obliged by existing rules to hide some things for certain groups?

Assign views initially

  1. Select the TermBase and the type of view (Edit, Manage, Search).

  2. Then specify the group and whether the TermBase as a whole should be visible for this group.

  3. When a view is defined for the first time, all fields are activated. Deactivate these if required.

  4. The configuration is automatically saved in the state in which it is displayed. There is no separate Save button.

Hinweis

If you open a view (e.g. Manage/Anonymous) and close it again without editing it, it is saved with all rights. Only open views that you want to edit. Open views must be configured to ensure that no unwanted rights are granted to this group. Pay particular attention to this note in relation to the Anonymous group, as this is used for all non-configured users in case of doubt.

Updating views

If you assign fields to an existing TermBase, these are initially deactivated for the views. To add new fields to views, open the relevant view and activate the new field (usually at the bottom of the list).

...


Tips

Tipp


The views of the Anonymous group are automatically used for all users for whose groups no other views are defined. This view should therefore include the minimum area that all employees are allowed to see.

Tipp

Congree users can also be assigned to several groups. You can therefore completely ignore the existing groups and create new groups for the views. Create views exclusively for these groups and leave the others untouched.

Tipp

The Search view refers exclusively to the TermTiger Anonymous Search. The display of the term search in the client is still defined via the Display Configuration in Congree Control Center - Settings - Global.

Suggestions for configuration

The views allow a detailed distribution of access rights down to field, value and language level. We have put together a few typical situations that can make your initial configuration easier.

situation

configuration

All persons with Congree user access work in the terminology. They are members of one group with the name "Users". All others only use the search.

Which fields should be displayed in the search? Activate these for the Search/Anonymous combination. Deactivate all other fields in this view. Do not configure any Edit or Manage views for Anonymous, or deactivate all fields in these views.
The "Users" group receives all rights in all views.

All employees use the TermTiger Anonymous Search. All persons with Congree user access also work on the terminology. But only a few people decide on the usage status. These people are members of the Senior Terminologists group.

As above, but your standard group "Users" has no authorization for the Usage field in the Edit view. The "Senior Terminologists" group has all rights everywhere.

All employees use the TermTiger Anonymous Search, but only a few specialists actively work in Congree TermTiger. The other members of the technical editorial team are also not expected to carry out any terminology work.

Define the Search view for Anonymous. The group(s) of experts receive all rights in Manage and Edit. You may need to create a new group for this. No views are defined for all other groups.
image-20240501-192809.pngImage Added As the Anonymous group is a fallback for all non-configured groups, you can ignore the views for most groups.

It should be possible to adapt fields depending on the native language.
image-20240501-192605.pngImage Added An example: Definition may be inserted by all. People from the respective native language decide on the usage status.

For fields that are specified as translatable, you can assign the rights depending on the language. You assign the rights for the non-translatable fields as in the other scenarios. You may need to create separate groups for each language.

Only explicitly permitted access is desired. There must be no access that has not been permitted by a specific, precisely defined group.

Do not define any views for the Anonymous group or deactivate all fields in all views for the Anonymous group. Anyone who is not logged in or does not belong to a group for which views have been defined cannot access TermTiger anywhere.

The authorized groups receive the views you have defined.