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

UI Invisible Custom Field #5037

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

Originally created by @proudbro on GitHub (Jun 29, 2021).

NetBox version

v.2.11.7

Feature type

New functionality

Proposed functionality

Since there is no way to restrict employees' access to editing specific fields I propose to add the ability to create web interface invisible custom fields.
It will be only possible to receive and send data via API. Thus, we will warn against accidental changes to sensitive data for third-party integrations.

Use case

Example:

  • We have integration between Zabbix and Netbox
  • Each Rack in Netbox has Custom Field value with Zabbix host ID related to this rack. Zabbix receives additional data about rack from Netbox (it can be alarms, power limits or so)
  • If someone enters via Web UI incorrect data there it will break the integration

Database changes

External dependencies

Originally created by @proudbro on GitHub (Jun 29, 2021). ### NetBox version v.2.11.7 ### Feature type New functionality ### Proposed functionality Since there is no way to restrict employees' access to editing specific fields I propose to add the ability to create web interface invisible custom fields. It will be only possible to receive and send data via API. Thus, we will warn against accidental changes to sensitive data for third-party integrations. ### Use case Example: - We have integration between Zabbix and Netbox - Each Rack in Netbox has Custom Field value with Zabbix host ID related to this rack. Zabbix receives additional data about rack from Netbox (it can be alarms, power limits or so) - If someone enters via Web UI incorrect data there it will break the integration ### Database changes + ### External dependencies -
adam added the type: featurepending closure labels 2025-12-29 19:23:23 +01:00
adam closed this issue 2025-12-29 19:23:23 +01:00
adam commented 2025-12-29 19:23:24 +01:00
Author
Owner
Copy Link

@AnythingOverIP commented on GitHub (Jul 15, 2021):

I would love if this could be happening. I would not limit this to custom properties, but also to "normal" fields. That would be great if we could simplify and make the UI lighter when fields are not to be used (ie: in site page). Perhaps something feasible in 3.0 with the upcoming UI overhaul? See https://github.com/netbox-community/netbox/issues/5777

@AnythingOverIP commented on GitHub (Jul 15, 2021): I would love if this could be happening. I would not limit this to custom properties, but also to "normal" fields. That would be great if we could simplify and make the UI lighter when fields are not to be used (ie: in site page). Perhaps something feasible in 3.0 with the upcoming UI overhaul? See https://github.com/netbox-community/netbox/issues/5777
adam commented 2025-12-29 19:23:24 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Jul 30, 2021):

I think what you want would be more suitable to moving to a config context and restrict editing of contexts to more "trustworthy" people.

@DanSheps commented on GitHub (Jul 30, 2021): I think what you want would be more suitable to moving to a config context and restrict editing of contexts to more "trustworthy" people.
adam commented 2025-12-29 19:23:24 +01:00
Author
Owner
Copy Link

@proudbro commented on GitHub (Aug 9, 2021):

@DanSheps , Rack model doesn't have config context. This is the whole problem

@proudbro commented on GitHub (Aug 9, 2021): @DanSheps , Rack model doesn't have config context. This is the whole problem
adam commented 2025-12-29 19:23:25 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Oct 9, 2021):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Oct 9, 2021): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:23:25 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Nov 8, 2021):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Nov 8, 2021): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure 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#5037
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?