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

View permissions should be reflected on Navbar and initial page #3866

New Issue
Closed
opened 2025-12-29 18:31:40 +01:00 by adam · 4 comments
adam commented 2025-12-29 18:31:40 +01:00
Owner
Copy Link

Originally created by @esoubihe on GitHub (Jul 17, 2020).

Environment

  • Python version: 2.8.5
  • NetBox version: 2.7.17

Proposed Functionality

From a UX perspective, the navbar and initial page should respect view permissions in the sense that they should be hidden if the user doesn't have access to them, both for secondary and primary navigation items.

I understand the implications of permissions and the concerns raised on #323 and other similar issues. The proposal here is merely an aesthetic change to avoid confusion and miss clicks.

Use Case

Company Story: As a bare metal shop, Virtualization is irrelevant to my team.
User Story: As a Support Manager, I want to simplify the interface so support analysts can find information faster.

Database Changes

None

External Dependencies

None

Originally created by @esoubihe on GitHub (Jul 17, 2020). ### Environment * Python version: 2.8.5 * NetBox version: 2.7.17 ### Proposed Functionality From a UX perspective, the navbar and initial page should respect view permissions in the sense that they should be hidden if the user doesn't have access to them, both for secondary and primary navigation items. I understand the implications of permissions and the concerns raised on #323 and other similar issues. The proposal here is merely an aesthetic change to avoid confusion and miss clicks. ### Use Case Company Story: As a bare metal shop, Virtualization is irrelevant to my team. User Story: As a Support Manager, I want to simplify the interface so support analysts can find information faster. ### Database Changes None ### External Dependencies None
adam closed this issue 2025-12-29 18:31:40 +01:00
adam commented 2025-12-29 18:31:40 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 17, 2020):

Navigation menu items for which the user does not have access to view are disabled. We don't remove them from the menu entirely completely because can very easily lead to user confusion in cases where permissions are missing.

@jeremystretch commented on GitHub (Jul 17, 2020): Navigation menu items for which the user does not have access to view are disabled. We don't remove them from the menu entirely completely because can very easily lead to user confusion in cases where permissions are missing.
adam commented 2025-12-29 18:31:40 +01:00
Author
Owner
Copy Link

@esoubihe commented on GitHub (Jul 17, 2020):

That's the exact reason why you have super admin users. Applying a CSS cursor style to the anchor and not even rejecting navigation is what causes confusion.

The current implementation is incorrect from a UI and UX perspective and confusion doesn't justify the decision.

@esoubihe commented on GitHub (Jul 17, 2020): That's the exact reason why you have super admin users. Applying a CSS cursor style to the anchor and not even rejecting navigation is what causes confusion. The current implementation is incorrect from a UI and UX perspective and confusion doesn't justify the decision.
adam commented 2025-12-29 18:31:40 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 17, 2020):

Applying a CSS cursor style to the anchor and not even rejecting navigation is what causes confusion.

A bug report to fix this would be valid, so long as there is an understanding that we won't fully remove the navigation items from view.

confusion doesn't justify the decision.

That's very easy to assert when you're not obligated to answer support requests. I am, so I have a very different opinion. I've also been the victim of "surprising" navigation menus in other applications more than once, and don't wish to subject anyone else to that frustration.

@jeremystretch commented on GitHub (Jul 17, 2020): > Applying a CSS cursor style to the anchor and not even rejecting navigation is what causes confusion. A bug report to fix this would be valid, so long as there is an understanding that we won't fully remove the navigation items from view. > confusion doesn't justify the decision. That's very easy to assert when you're not obligated to answer support requests. I am, so I have a very different opinion. I've also been the victim of "surprising" navigation menus in other applications more than once, and don't wish to subject anyone else to that frustration.
adam commented 2025-12-29 18:31:40 +01:00
Author
Owner
Copy Link

@esoubihe commented on GitHub (Jul 17, 2020):

Shouldn't we at least gather feedback from the community and weigh the pros and cons?

Seems like the only con in your argument is that you have to respond to support tickets. I think there are ways around that that could be explored. Also, what do you mean by surprising navigation menus?

@esoubihe commented on GitHub (Jul 17, 2020): Shouldn't we at least gather feedback from the community and weigh the pros and cons? Seems like the only con in your argument is that you have to respond to support tickets. I think there are ways around that that could be explored. Also, what do you mean by surprising navigation menus?
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
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#3866
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?