Permissions for topics

You can set a permission for each topic. There are permission levels and permission types.

Permission levels:

A permission item is described by:

• User or user group
• Permission level
• Expiry date (optional)

  The permission level can be:

• Admin
• Update
• Guest

  Admin rights:

• Change all topic fields
• Delete topic
• Add/remove relations
• Add notes
• Add broadcast
• Remove notes (can remove anybody’s)
• View history
• View permissions and grant access

  Update rights:

• Change all topic fields
• Add/remove relations
• Add notes
• Remove her own notes
• View history

  Guest rights:

• View data sheet (The Discussions tab) in read-only mode.

  Note: When you create a topic, the Admin permission for the creator of the topic is added.

A topic has a permission type. Permissions can be granted explicitly and the explicit permissions supplement the permissions obtained from those of the selected permission type.

Permission types:

• Grant only: Only the explicit permissions of the topic apply.
• Inherited: The topic inherits permissions from the primary relation as per the following:
• Translation project:
• Project manager -> Update
• Terminologist ->Update
• Translator -> Update
• Term base:
• Admin -> Admin
• Reviewer -> Update
• Updater -> Update
• Lookup -> Guest
• Public: All memoQWeb (legacy) users have guest permission to the topic.

Who can do what?

Not every topic is visible to all users. Administrators see all topics.

The list of topics visible to a non-admin user can be obtained by the following rules:

• User (or a group containing the user) has permission for (permissions type: grant only, public)
• User (or a group containing the user) has permission for (permission type: inherited) and the primary relation is a term base and the user has permission for the term base.
• User (or a group containing the user) has permission for (permission type: inherited) and the primary relation is a project, with these rules:
• The following user types inherit permissions:
• Users are assigned explicitly to the project.
• Users are assigned to a group-sourced document.
• Users are assigned to Subvendor groups.
• FirstAccept users are ignored.
• Topics where the primary relation is a term base, and the term base is attached to a project the user is member of.

  Caution: This is a special case because neither explicit nor inherited permissions can be applied in this case. The user gets Update permissions for the topic.