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

Limiting access to "Other" objects (Tags, Config Contexts) #7615

New Issue
Closed
opened 2025-12-29 20:26:05 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:26:05 +01:00
Owner
Copy Link

Originally created by @stavr666 on GitHub (Feb 8, 2023).

NetBox version

v3.4.3

Feature type

New functionality

Proposed functionality

Add ability to assign limited access to Tags and Config Contexts.

Assigning Tenant and use it as access role filter is fine, but as it's actually can cause recursive references, new field possible needed.

Use case

While adopting config contexts (bound to tags) to store device and VM options for external orchestrators and monitoring, we encountered and issue, when we can either add user ability to change any CC/tags, or block all changes.

We need mechanics, working similar to other objects in Netbox: limiting access to several CC and/or tags. This way, changing network configs (bound to network devices, already limited in DCIM) will be possible by person with access to network devices, and changing VM CC's will be possible only by virtualization team.

Database changes

No response

External dependencies

No response

Originally created by @stavr666 on GitHub (Feb 8, 2023). ### NetBox version v3.4.3 ### Feature type New functionality ### Proposed functionality Add ability to assign limited access to Tags and Config Contexts. Assigning Tenant and use it as access role filter is fine, but as it's actually can cause recursive references, new field possible needed. ### Use case While adopting config contexts (bound to tags) to store device and VM options for external orchestrators and monitoring, we encountered and issue, when we can either add user ability to change any CC/tags, or block all changes. We need mechanics, working similar to other objects in Netbox: limiting access to several CC and/or tags. This way, changing network configs (bound to network devices, already limited in DCIM) will be possible by person with access to network devices, and changing VM CC's will be possible only by virtualization team. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: revisions needed labels 2025-12-29 20:26:05 +01:00
adam closed this issue 2025-12-29 20:26:05 +01:00
adam commented 2025-12-29 20:26:05 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 16, 2023):

Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.

@jeremystretch commented on GitHub (Mar 16, 2023): Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md), a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.
adam commented 2025-12-29 20:26:06 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 4, 2023):

Closing this as there's been no further response from OP.

@jeremystretch commented on GitHub (Apr 4, 2023): Closing this as there's been no further response from OP.
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: revisions needed 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#7615
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?