|Define special role "Superuser" or "Root"|
|Having a large project repository and hundreds of users, it is good practice to have more than one admin for daily jobs like adding users to project, changing roles or creating new projects, but on the other side having many administrators causes some chaos in definition of the roles, categories and phases.|
It would be great to have a superuser with rights to define the "critical" data types like categories, phases, roles or maybe even project templates (when this is available some day) etc.
The "normal" admins should then only have limited rights for daily jobs as mentioned above.
|Back to Search Results|