Feature #41143
closed
Project Menu Module Access Configuration
0%
Description
Dear Redmine Team,
I would like to propose an enhancement that would allow administrators to define which project menu modules are accessible to end users. Currently, modules such as "Time Tracking," "Gantt," and "Calendar" are enabled by default, which can overwhelm the user experience, especially in scenarios where end users only need access to request submission and tracking modules.
Implementing this feature would improve usability and streamline the workspace for users who require limited access, avoiding unnecessary distractions and simplifying their interaction with the platform.
Thank you for considering this request. I am available to discuss further details if needed.
Sincerely,
Related issues
Updated by Holger Just 3 months ago
- Is duplicate of Feature #10091: Allow administrator to permanently disable modules added
Updated by Holger Just 3 months ago
- Status changed from New to Closed
- Resolution set to Duplicate
You can already configure which modules should be enabled by default in new projects. You can set this at Administration -> Settings -> Projects.
The actual feature to fully disable certain modules is a duplicate of #10091. As such, I'm closing this issue as a duplicate.
Updated by Andres Eduardo Garcia Marquez 3 months ago
Described the problem:
Realmento, Redmine allows you to configure the modules that are activated by default in new projects through the "Administration -> Configuration -> Projects" option. However, not the ability to hide or disable modules for specific users within the same project. This can lead to an overwhelming, specially user store if some users only need to access certain modules, those of application and monitoring, and not a "Gantt" "Gantt", "or" Traceando ".
IMPROVEMENT PROPOSAL:
I liked to propose an improvement that would allow administrators to define that Prooyecto Modules Son accessible to specific users. This would provide a more granular management form the visibility of the modules, improving the usability and simplifying the interaction with the platform. For example, it would be useful if the administrators of the administration of the "Gantt" module to be, for all users, except for one a special one who does not need it.
No additional:
The real application is considered a duplication of the #10091 ticket, which deals with the possibility of permanently deactivating modules.
My proposal focuses on the management capacity of the visibility of the modules, a user individual, not just a project level.
Updated by Andres Eduardo Garcia Marquez 3 months ago
And how can I modify the code to send the application to integrate the improvements you make
Updated by Holger Just 3 months ago
If you want to enable a module in a project but want to restrict its visibility to some users (but want to allow others to use the module in the project), you can define a restricted role which does not grant users the permissions to use the module. If you want to deny some users access to the Time tracking module for example, you can create a new roles which does not have any permissions for time tracking and assign this role to the user in the project.
Note that users can have multiple roles in a single project. The effective permissions for the user are the sum of all its roles. Thus, if a single roles of the user grant a permissions (but others do not), the permission is ultimately granted to the user in the project.