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

Hide fields for specific user groups #10341

New Issue
Closed
opened 2025-12-29 21:30:15 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:30:15 +01:00
Owner
Copy Link

Originally created by @powerscooter on GitHub (Oct 9, 2024).

NetBox version

v4.0.7

Feature type

New functionality

Triage priority

N/A

Proposed functionality

This will probably be a big feature request now. We have been using Netbox for several years and it has become one of the most important tools for us.
Netbox is getting more and more functions, which means more and more fields in all screens. For example, if we want to create a device, we only have to fill in 8 fields. All the others are not necessary in our case.
For even better user-friendliness, it would therefore be nice to be able to hide fields that are not required.

Use case

We often discover that some users are overwhelmed because they don't know whether a field has to be filled in or not. If you can set the fields that are displayed for users or perhaps based on user groups, the user-friendliness would be improved once again. The error rate when creating different data would also be minimized. As no unnecessary information would be entered.

Database changes

No response

External dependencies

No response

Originally created by @powerscooter on GitHub (Oct 9, 2024). ### NetBox version v4.0.7 ### Feature type New functionality ### Triage priority N/A ### Proposed functionality This will probably be a big feature request now. We have been using Netbox for several years and it has become one of the most important tools for us. Netbox is getting more and more functions, which means more and more fields in all screens. For example, if we want to create a device, we only have to fill in 8 fields. All the others are not necessary in our case. For even better user-friendliness, it would therefore be nice to be able to hide fields that are not required. ### Use case We often discover that some users are overwhelmed because they don't know whether a field has to be filled in or not. If you can set the fields that are displayed for users or perhaps based on user groups, the user-friendliness would be improved once again. The error rate when creating different data would also be minimized. As no unnecessary information would be entered. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: duplicate labels 2025-12-29 21:30:15 +01:00
adam closed this issue 2025-12-29 21:30:15 +01:00
adam commented 2025-12-29 21:30:16 +01:00
Author
Owner
Copy Link

@alehaa commented on GitHub (Oct 9, 2024):

I fear this has been discussed before, at least in #16882 and #14481.

@alehaa commented on GitHub (Oct 9, 2024): I fear this has been discussed before, at least in #16882 and #14481.
adam commented 2025-12-29 21:30:16 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 10, 2024):

Thank you for submitting this issue, however it appears that this topic has already been raised. Please see issue #14481 for further discussion.

@jeremystretch commented on GitHub (Oct 10, 2024): Thank you for submitting this issue, however it appears that this topic has already been raised. Please see issue #14481 for further discussion.
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: duplicate 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#10341
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?