starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-12 05:20:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Toggle the visibility of navigation menu items #6317

New Issue
Closed
opened 2025-12-29 19:39:17 +01:00 by adam · 6 comments
adam commented 2025-12-29 19:39:17 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Apr 7, 2022).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.2.0

Feature type

New functionality

Proposed functionality

Enable NetBox administrators to disable certain navigation menu headings (e.g. Wireless or Circuits). This would most likely be implemented as a dynamic configuration option.

Use case

This has come up a few times in various forums. I think the main theme is wanting to "hide" areas of NetBox that are unused. With the change to programmatically-rendered menu items in v3.0, I think this is more feasible than it has been in the past.

Database changes

No response

External dependencies

No response

Originally created by @jeremystretch on GitHub (Apr 7, 2022). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.2.0 ### Feature type New functionality ### Proposed functionality Enable NetBox administrators to disable certain navigation menu headings (e.g. Wireless or Circuits). This would most likely be implemented as a dynamic configuration option. ### Use case This has come up a few times in various forums. I think the main theme is wanting to "hide" areas of NetBox that are unused. With the change to programmatically-rendered menu items in v3.0, I think this is more feasible than it has been in the past. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 19:39:17 +01:00
adam closed this issue 2025-12-29 19:39:18 +01:00
adam commented 2025-12-29 19:39:18 +01:00
Author
Owner
Copy Link

@stephanblanke commented on GitHub (Apr 8, 2022):

I would propose to tie the visibility of menu items to the users permissions, instead of a separate option in the admin panel. Usually we want to hide an object type for the user in the web interface and the API.

@stephanblanke commented on GitHub (Apr 8, 2022): I would propose to tie the visibility of menu items to the users permissions, instead of a separate option in the admin panel. Usually we want to hide an object type for the user in the web interface and the API.
adam commented 2025-12-29 19:39:18 +01:00
Author
Owner
Copy Link

@emersonfelipesp commented on GitHub (Apr 11, 2022):

I would propose to tie the visibility of menu items to the users permissions, instead of a separate option in the admin panel. Usually we want to hide an object type for the user in the web interface and the API.

I agree with @stephanblanke, having a global way of manage which navigation buttons must appear is cool. But for me, the real solution is to have this related to the permission group.

I work at an ISP and there are Netbox users which only uses the "Devices (DCIM)" section while others uses only the logical ones, like "Virtualization" and "IPAM".

But again, having a global visibility configuration is fine too, as none of the users of Netbox at the ISP uses the "Wireless" section.

@emersonfelipesp commented on GitHub (Apr 11, 2022): > I would propose to tie the visibility of menu items to the users permissions, instead of a separate option in the admin panel. Usually we want to hide an object type for the user in the web interface and the API. I agree with @stephanblanke, having a global way of manage which navigation buttons must appear is cool. But for me, the real solution is to have this related to the permission group. I work at an ISP and there are Netbox users which only uses the "Devices (DCIM)" section while others uses only the logical ones, like "Virtualization" and "IPAM". But again, having a global visibility configuration is fine too, as none of the users of Netbox at the ISP uses the "Wireless" section.
adam commented 2025-12-29 19:39:19 +01:00
Author
Owner
Copy Link

@joaolucasmacedo commented on GitHub (Apr 11, 2022):

That is pretty nice, but I would go further and consider some configuration to hide certain fields from objects, because there is so much information but mos people don't use all of them. So, if I'm proposing something feasible, it would be nice to have a way to hide some fields making navigation and object manipulation much cleaner and quicker.

@joaolucasmacedo commented on GitHub (Apr 11, 2022): That is pretty nice, but I would go further and consider some configuration to hide certain fields from objects, because there is so much information but mos people don't use all of them. So, if I'm proposing something feasible, it would be nice to have a way to hide some fields making navigation and object manipulation much cleaner and quicker.
adam commented 2025-12-29 19:39:19 +01:00
Author
Owner
Copy Link

@emersonfelipesp commented on GitHub (Apr 12, 2022):

That is pretty nice, but I would go further and consider some configuration to hide certain fields from objects, because there is so much information but mos people don't use all of them. So, if I'm proposing something feasible, it would be nice to have a way to hide some fields making navigation and object manipulation much cleaner and quicker.

Maybe instead of "simply" manage the Model permissions as Netbox currently do, it would be necessary to create some mechanism to manage the field permissions of the Model.

@emersonfelipesp commented on GitHub (Apr 12, 2022): > That is pretty nice, but I would go further and consider some configuration to hide certain fields from objects, because there is so much information but mos people don't use all of them. So, if I'm proposing something feasible, it would be nice to have a way to hide some fields making navigation and object manipulation much cleaner and quicker. Maybe instead of "simply" manage the Model permissions as Netbox currently do, it would be necessary to create some mechanism to manage the field permissions of the Model.
adam commented 2025-12-29 19:39:19 +01:00
Author
Owner
Copy Link

@lknflexfone commented on GitHub (May 20, 2022):

we can defently concour on this feature, would be nice if the view was bound the permissions model so you only presented what your permissions gave you access to.

@lknflexfone commented on GitHub (May 20, 2022): we can defently concour on this feature, would be nice if the view was bound the permissions model so you only presented what your permissions gave you access to.
adam commented 2025-12-29 19:39:19 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 29, 2022):

I'm going to tag this for v3.3 with the modification that permissions will be used to control the display of menu items. A user will be able to see only the navigation menu items for which he or she has permission to view the relevant objects (instead of the menu items being grayed out).

That is pretty nice, but I would go further and consider some configuration to hide certain fields from objects, because there is so much information but mos people don't use all of them.

Any discussion along this vein would be wholly out of scope for this FR I'm afraid.

@jeremystretch commented on GitHub (Jun 29, 2022): I'm going to tag this for v3.3 with the modification that permissions will be used to control the display of menu items. A user will be able to see only the navigation menu items for which he or she has permission to view the relevant objects (instead of the menu items being grayed out). > That is pretty nice, but I would go further and consider some configuration to hide certain fields from objects, because there is so much information but mos people don't use all of them. Any discussion along this vein would be wholly out of scope for this FR I'm afraid.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: accepted type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#6317
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?