Project

General

Profile

Actions

Feature #4049

closed

Permission management on a per project basis

Added by G N over 14 years ago. Updated about 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Permissions and roles
Target version:
-
Start date:
2009-10-18
Due date:
% Done:

0%

Estimated time:
Resolution:
Duplicate

Description

Currently, it is impossible to set permissions for a role on a per project basis.

For example, assuming that we have two projects, A & B, it is impossible to make the "_documents_" and "_repository_" modules publicly available on project A, while at the same time keeping them private (granting access only to Managers and Developers) on project B.

I think that the ability to (at least) manage the "view_*" or "browse_*" permissions per project would be a natural requirement for a multi-project management software.

Unfortunately, my knowledge of Ruby is zero (at the moment), so I cannot provide any patches. But I think that implementing this feature would not be complex, as all the functionality exists.

As a quick suggestion I would say that a new project-related permission, "Manage Permissions", should be available to enable/disable for the "Manager" role. And then, a "permissions" tab could exist in the project administration area, where the manager would be able to set permissions specifically for the project he manages.

I hope my suggestion is clear enough and I feel sorry for not being able to contribute any code.

Thanks in advance.


Related issues

Related to Redmine - Feature #4015: Make app settings overridable at project levelNew2009-10-10

Actions
Is duplicate of Redmine - Feature #850: Per-project role permissionsNew2008-03-14

Actions
Actions

Also available in: Atom PDF