Version 4.5.0

Project module availability

Administrators can control global module availability without deleting project selections or stored data.

How it works

  1. Open the plugin's Projects settings tab.
  2. Leave every module enabled for Redmine's default behavior.
  3. Disable modules that must not be available globally.
  4. Re-enable a module later to restore menus and permissions with preserved data.

Apply module availability in the correct order

  1. Open Administration → Plugins → Redmine UX Toolkit → Configure → Projects and decide which toolkit modules may be used anywhere in Redmine.
  2. Apply the global selection. A disabled module is unavailable to every project even if that project selected it previously.
  3. For an available module, open Project settings → Modules and enable it for each intended project.
  4. Grant the related role permissions. Global availability, project enablement, and role permission must all allow the feature.
  5. Test the project menu with a normal project member.

Effect of disabling a module

  • Related project menus are hidden.
  • Related permissions are blocked.
  • Existing selections and data remain stored.
  • Reactivation is reversible.

Re-enable a module

Return to the Projects tab, enable the module, and apply the settings. Previously stored project selections and plugin-owned data become usable again; you do not need to recreate them. Recheck role permissions if the menu remains unavailable.

Availability is not deletion. This setting is designed for reversible global rollout decisions.
Redmine project overview with project module navigation
DesktopProject menus reflect global availability and project-specific enablement.