- TermProposer-user
- can update/delete some term only if that term was created by that
userTermReviewer-- user
can update some term only if that term is Unprocessed TermFinalizer-user - can update
some term only if that term is ProvisionallyProcessedTermProposer-user can update- /delete some attribute only if that attribute was created by that user and all term(s) on that attribute's level are Unprocessed, so:
- If it's a term-level attribute - that term should be Unprocessed
- If it's a language-level attribute - all terms for that language should be Unprocessed
- If it's a termEntry-level attribute - all terms for that termEntry should be Unprocessed
- TermReviewer-user
- can update some term only if that term is Unprocessed
- can update/delete some attribute only if all term(s) on that attribute's level are Unprocessed, so it's same as in point 4 but with no 'was created by that user'-requirement
- TermFinalizer-user
- can update some term only if that term is ProvisionallyProcessed
- can update/delete some attribute only if all term(s) on that attribute's level are ProvisionallyProcessed, so it's same as in point 5 but just other status used
- As long as TermPortal is working with terms, which are contained in TermCollections, users of all roles except termPM_(allClients)-role can only access the TermCollections of those clients, that they are associated with in the user management in the main translate5 app.
- The ability to update processStatus attribute is:
- Not available for roles of Type 1
- Partially available for roles of Type 2
- TermProposer-user - not available
- TermReviewer-user - available, but only from Unprocessed to only ProvisionallyProcessed or Rejected
- TermFinalizer-user - available, but only from ProvisionallyProcessed to only Finalized or Rejected
- Fully available for roles of Type 3
|