TermPortal app have a number of roles, that affect both client app and server app capabilities. Currently TermPortal have 6 roles, but basically they can be divided into 3 types.
eyJleHRTcnZJbnRlZ1R5cGUiOiIiLCJnQ2xpZW50SWQiOiIiLCJjcmVhdG9yTmFtZSI6IlBhdmVsIFBlcm1pbm92Iiwib3V0cHV0VHlwZSI6ImJsb2NrIiwibGFzdE1vZGlmaWVyTmFtZSI6IlBhdmVsIFBlcm1pbm92IiwibGFuZ3VhZ2UiOiJlbiIsInVpQ29uZmlnIjoie30iLCJkaWFncmFtRGlzcGxheU5hbWUiOiIiLCJzRmlsZUlkIjoiIiwiYXR0SWQiOiIzNTE4MzAwMjgiLCJkaWFncmFtTmFtZSI6IlJvbGVzIiwiYXNwZWN0IjoiIiwibGlua3MiOiJhdXRvIiwiY2VvTmFtZSI6IlRlcm1Qb3J0YWw6IFVzZXIgcm9sZXMiLCJ0YnN0eWxlIjoidG9wIiwiY2FuQ29tbWVudCI6ZmFsc2UsImRpYWdyYW1VcmwiOiIiLCJjc3ZGaWxlVXJsIjoiIiwiYm9yZGVyIjp0cnVlLCJtYXhTY2FsZSI6IjEiLCJvd25pbmdQYWdlSWQiOjM1MTgzMDAyMywiZWRpdGFibGUiOmZhbHNlLCJjZW9JZCI6MzUxODMwMDIzLCJwYWdlSWQiOiIiLCJsYm94Ijp0cnVlLCJzZXJ2ZXJDb25maWciOnsiZW1haWxwcmV2aWV3IjoiMSJ9LCJvZHJpdmVJZCI6IiIsInJldmlzaW9uIjozLCJtYWNyb0lkIjoiN2ZjYWIwNWEtYTdjMS00YWJlLTg5MDEtMDQ0NzQ0ODFjYThmIiwicHJldmlld05hbWUiOiJSb2xlcy5wbmciLCJsaWNlbnNlU3RhdHVzIjoiT0siLCJzZXJ2aWNlIjoiIiwiaXNUZW1wbGF0ZSI6IiIsIndpZHRoIjoiMzYxIiwic2ltcGxlVmlld2VyIjpmYWxzZSwibGFzdE1vZGlmaWVkIjoxNjUyNzY1MjM5MDAwLCJleGNlZWRQYWdlV2lkdGgiOmZhbHNlLCJvQ2xpZW50SWQiOiIifQ==
|
Roles
| Write rights on |
|---|
| Term | Attribute |
| create | update | delete | create | update | delete |
| Type 1 | termCustomerSearch | No | No | No | No | No | No |
Type 2 | termProposer | Yes | Yes if 1.a | Yes | Yes if 1.b |
| termReviewer | No | Yes if 2.a | No | No | Yes if 2.b |
| termFinalizer | No | Yes if 3.a | No | No | Yes if 3.b |
| Type 3 | termPM | Yes | Yes | Yes | Yes | Yes | Yes |
| termPM_allClients4 | Yes | Yes | Yes | Yes | Yes | Yes |
Note that processStatus attribute has a special meaning and behaviour implemented, so that it is completely impossible to delete it for user having any role, but it is partially/fully possible to update it. See point 5 below for details. |
- TermProposer-user
- can update/delete some term only if that term was created by that 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 1.b 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 2.b 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
|