Disable/Hide the "Application Vulnerability Response" module in the navigator?

[Matt Moerloos1]

I have done many Vulnerability Response implementations for clients and majority of them do not use the Application Vulnerability Response module. I have attempted to "hide" this module within the Application Navigator by setting the Application Menu object to inactive, which works initially, but somehow always is automatically set back to Active. This is becoming a point of frustration for our clients as they have found themselves searching for modules within the core Vulnerability Response module and accidentally selecting the modules within Application Vulnerability Response (like Assignment Rules, Calculators, etc). 

I have encouraged my clients to add the Vulnerability Response module as a favorite and navigate to the Application Modules through their favorites menu, but people like to work in different ways and this is not a solution to the issue.

I am not sure if my approach to hide this module is incorrect, or if there is a better way to do this. Wanted to get the community's thoughts.

Thank you!

[Community Alums]

Hi @Matt Moerloos1 ,

Here are few options :

Enable or disable the application menu and modules as desired.

Option	Description
Enable or disable a specific module in the application	Double-click the Active field beside the module name in the Modules related list. Set Active to true (show) or false (hide).
Enable or disable multiple modules at the same time	Select the check boxes next to the module names. Select Change active state from the Actions choice list.
Enable or disable the entire application menu (for example, Incident or Service Catalog)	Select or clear the Active check box.
Restrict the application menu to specific roles	Use the Roles field.

[Matt Moerloos1]

Hi Sandeep,

Thank you for your quick response. I think the option to restrict the application menu to a new custom role may be the only option. I will test this out.

The other options to set the modules to inactive does not work in the long run. It does work initially, but for some reason after a few days they are automatically set back to active and visible again in the navigator. I suspect the system may be doing it, or possibly is it changed when updates are applied.

[Community Alums]

Surely test it out  @Matt Moerloos1 

[Matt Moerloos1]

Although creating or limiting the visibility of this Application by role certainly works. I have found that modifying the Application order as another user suggested was a simpler approach. Thank you for your suggestions!