Overriding permissions
When assigning permissions to user types, you should take into account the fact that certain permissions might override others.
For example, a project group contains five projects (corresponding to five different locales) and Translators A and B only have permissions on two of those locales. Depending on the permissions you assign to the user type to which Translators A and B belong, they will be able to see either all the projects for the project group in question, or only the project corresponding to the locales on which they have permissions, as in the following table:
| Outcome | Permissions | Explanation |
|---|---|---|
| Translators A and B can see only the projects and tasks corresponding to the locales they know. | Any or all of the following:
| These permissions are related directly to user locales. If you wan the users of a certain type to see only the projects and tasks corresponding to their specific locales, do not select any other check boxes under |
| Translators A and B can see al the projects and tasks in the project group. | Any or all of the permissions listed earlier, plus a permission that implies viewing all projects, regardless of their locale, such as Can view all active projects. | In this case, the Can view all active projects permission allows the users of that type to view active projects and tasks, regardless of their locale. Such a permission overrides locale-related permissions and allows users to see all the projects and tasks in a project group. |