- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2023 10:54 PM
Hi.
I want to customize the application menu on my instance, so it will contain only my work/tasks, and the applications that i need..
How do I do it?...
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2023 11:12 PM
Hi @Yuval Lanton ,
The best practice is to grant access to modules/menus by role. This is much more efficient as roles are cached during the user's session - that's why you need to logout/login when given new roles. Using a script means you are imposing a load on the system where caching is not involved and could cause performance issues. What's more, later administrators may find your script difficult to find and/or maintain.
- Navigate to All > System Definition > Application Menus.
- If you are enabling an application menu, click All in the breadcrumbs to display both active and inactive application menus (remove the default filter condition).
- Click the desired title. The application menu record opens and the Modules related list shows the modules that appear in the application navigator.
- 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. - Click Update.
When you change application menus or modules, the application navigator automatically refreshes to display the changes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2023 11:12 PM
Hi @Yuval Lanton ,
The best practice is to grant access to modules/menus by role. This is much more efficient as roles are cached during the user's session - that's why you need to logout/login when given new roles. Using a script means you are imposing a load on the system where caching is not involved and could cause performance issues. What's more, later administrators may find your script difficult to find and/or maintain.
- Navigate to All > System Definition > Application Menus.
- If you are enabling an application menu, click All in the breadcrumbs to display both active and inactive application menus (remove the default filter condition).
- Click the desired title. The application menu record opens and the Modules related list shows the modules that appear in the application navigator.
- 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. - Click Update.
When you change application menus or modules, the application navigator automatically refreshes to display the changes.