ChiliProject is not maintained anymore. Please be advised that there will be no more updates.
We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.
Granular admin rights (Feature #121)
Right now the administrator role is all or nothing. On the other hand, project owners have no special system-wide power.Ideally, we should move away from the monolithic "administrator" concept and have separate rights for:
- managing users (including creating new users, assigning rights and projects)
- managing projects (including creating new projects and assigning an owner that is not the user herself)
- changing settings such as email server config
This would make it possible to e.g. let an IT support person handle user management, without giving them wide open access to all.
Note that I mostly care about preventing "casual" unauthorized access: of course a determined person with user-mgmt rights could give themselves the right to access more projects (but that would be easy to detect from log files).
|duplicated by Feature #204: ReThink the Create Project permission||Duplicate||2011-02-18|
I proposed something like that some time ago on Redmine's issue tracker. Unfortunately, to make it right, it means rewriting most of the permission system, as ChiliProject currently doesn't really support the concept of global rights. Such a rewrite is something which is planned nevertheless (see New Permissions), but it will take some time to be completed.
Although we have a plugin adding this developed at finnlabs, we don't think this is generic enough to be part of the core.
- (deleted custom field) set to http://www.redmine.org/issues/4427