Ability to hide core functionality menu items #3636

New Issue

adam · 2025-12-29T18:30:17+01:00

adam commented

2025-12-29 18:30:17 +01:00

Originally created by @kamfaima on GitHub (May 5, 2020).

Environment

Python version: NA
NetBox version: NA

Proposed Functionality

Ability to hide or display certain core functionality menu items. This could possibly be extended to hiding sub-menus in each of those core areas.

Use Case

There will undoubtedly be times where certain tools contain functionality that overlap with others. For instance, we don't plan on storing secrets in Netbox as we already have a 3rd-party tool to do this. To enforce this, I propose simply hiding the Secrets menu from the core functionality menu so users won't be physically able to use Secrets. This will eliminate duplicate information being stored in two different tools.

It has been proposed in the Netbox user group that we can simply not grant the permissions to those menus. While this works, the menu item still appears but none of its elements are selectable. This can raise more questions like why is it there but not selectable. I would think it's better to simply not display the menu item altogether to remove this confusion.

Database Changes

None that I know of.

External Dependencies

None that I know of.

Originally created by @kamfaima on GitHub (May 5, 2020).  ### Environment * Python version: NA * NetBox version: NA  ### Proposed Functionality Ability to hide or display certain core functionality menu items. This could possibly be extended to hiding sub-menus in each of those core areas.  ### Use Case There will undoubtedly be times where certain tools contain functionality that overlap with others. For instance, we don't plan on storing secrets in Netbox as we already have a 3rd-party tool to do this. To enforce this, I propose simply hiding the Secrets menu from the core functionality menu so users won't be physically able to use Secrets. This will eliminate duplicate information being stored in two different tools. It has been proposed in the Netbox user group that we can simply not grant the permissions to those menus. While this works, the menu item still appears but none of its elements are selectable. This can raise more questions like why is it there but not selectable. I would think it's better to simply not display the menu item altogether to remove this confusion.  ### Database Changes None that I know of.  ### External Dependencies None that I know of.

adam added the status: duplicate label 2025-12-29 18:30:17 +01:00

adam closed this issue

2025-12-29 18:30:17 +01:00

adam commented

2025-12-29 18:30:18 +01:00

@jeremystretch commented on GitHub (May 5, 2020):

Duplicate of #426

@jeremystretch commented on GitHub (May 5, 2020): Duplicate of #426

adam commented

2025-12-29 18:30:18 +01:00

@createchange commented on GitHub (Aug 21, 2020):

I want to propose a solution to the problem that involves no code changes by the developer. I think you could take this to great lengths with advanced filtering and validation.

You can use uBlock (and other similar extensions) to filter out elements.

As an example implementation, you would construct a query that finds an element with "Secrets", traverse back up X elements until you got to the navbar button, and wipe the things from existence. This would also be supremely easy to do on the dashboard.

The CSS is responsive, so hideous gaps are not left in their wake.

Once you have figured it out on your machine, you would share the config with your users. It's as simple as copying and pasting - screenshots are wonderful.

@createchange commented on GitHub (Aug 21, 2020): I want to propose a solution to the problem that involves no code changes by the developer. I think you could take this to great lengths with advanced filtering and validation. You can use uBlock (and other similar extensions) to filter out elements. As an example implementation, you would construct a query that finds an element with "Secrets", traverse back up X elements until you got to the navbar button, and wipe the things from existence. This would also be supremely easy to do on the dashboard. The CSS is responsive, so hideous gaps are not left in their wake. Once you have figured it out on your machine, you would share the config with your users. It's as simple as copying and pasting - screenshots are wonderful.

Sign in to join this conversation.

Branches Tags

main

update-changelog-comments-docs

feature-removal-issue-type

20911-dropdown

20239-plugin-menu-classes-mutable-state

21097-graphql-id-lookups

feature

fix_module_substitution

20923-dcim-templates

20044-elevation-stuck-lightmode

feature-ip-prefix-link

v4.5-beta1-release

20068-import-moduletype-attrs

20766-fix-german-translation-code-literals

20378-del-script

7604-filter-modifiers-v3

circuit-swap

12318-case-insensitive-uniqueness

20637-improve-device-q-filter

20660-script-load

19724-graphql

20614-update-ruff

14884-script

02496-max-page

19720-macaddress-interface-generic-relation

19408-circuit-terminations-export-templates

20203-openapi-check

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/netbox#3636