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

Implement simple pre-configured user permissions for general use cases #6610

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

Originally created by @artiomello on GitHub (Jun 30, 2022).

NetBox version

v3.2.3

Feature type

New functionality

Proposed functionality

Currently there's no easy way of creating a simple (e.g. view-only) permission to a specific parent object (e.g. Region) that would encompass all its related child objects without spending a substantial amount of time on creating some overly complicated filter that is next to impossible to plan out in advance due to every component having a distinct set of properties to filter for.

Sure, the level of granularity that this filtering approach provides is a godsend to any infrastructure control freak, but there are many cases where you would simply want to grant view-only to all object in a specific region/location/site that would display all related linked (circuits, devices, connections, etc) and their respective child objects without spending days on figuring out the filtering schema.

Use case

Right now if I select DCIM>region I would expect to set a filter to a specific region and see everything, but I end up seeing only that specific region info page void of any other child object information. Adding Circuits with the same region filter breaks everything because there's no such property on these object.

There should be a way of granting general use case type of permissions quickly and easily out of the box without spending crazy hours on configuring custom complicated filters.

Our specific use case is as follows. We have multiple regions with one to several geographical locations within them, each having one or two data DCs with racks, equipment, connections and whatnot. We need to be able to provide typical (e.g. read-only) permissions to local IT personnel within that region/site/location that would grant them the ability to e.g. view ALL their assets without having admins to spend days on figuring out how to do it using convoluted permission/object/filter combination to do so.

That is, I cannot select all object types (or some subset of them), tick the "can view" action and type in "Region=Texas" in the filter as it immediately starts spewing out errors because such and such object collection doesn't have the property region defined. Instead I have to configure the "Texas Region view-only" permissions as if I'm trying to add custom permissions to modify some specific vlan with IDs ranging from 123 to 234 in one specific location that is active and is not reserved and has a tag called purple attached to it with a tenant name that doesn't start from the letter A.

I hope you get the idea - the most obvious general permission use cases, besides "admin" that is, require complex filtering, tagging and a combination of both.

Database changes

No response

External dependencies

No response

Originally created by @artiomello on GitHub (Jun 30, 2022). ### NetBox version v3.2.3 ### Feature type New functionality ### Proposed functionality Currently there's no easy way of creating a simple (e.g. view-only) permission to a specific parent object (e.g. Region) that would encompass all its related child objects without spending a substantial amount of time on creating some overly complicated filter that is next to impossible to plan out in advance due to every component having a distinct set of properties to filter for. Sure, the level of granularity that this filtering approach provides is a godsend to any infrastructure control freak, but there are many cases where you would simply want to grant view-only to all object in a specific region/location/site that would display all related linked (circuits, devices, connections, etc) and their respective child objects without spending days on figuring out the filtering schema. ### Use case Right now if I select DCIM>region I would expect to set a filter to a specific region and see everything, but I end up seeing only that specific region info page void of any other child object information. Adding Circuits with the same region filter breaks everything because there's no such property on these object. There should be a way of granting general use case type of permissions quickly and easily out of the box without spending crazy hours on configuring custom complicated filters. Our specific use case is as follows. We have multiple regions with one to several geographical locations within them, each having one or two data DCs with racks, equipment, connections and whatnot. We need to be able to provide typical (e.g. read-only) permissions to local IT personnel within that region/site/location that would grant them the ability to e.g. view ALL their assets without having admins to spend days on figuring out how to do it using convoluted permission/object/filter combination to do so. That is, I cannot select all object types (or some subset of them), tick the "can view" action and type in "Region=Texas" in the filter as it immediately starts spewing out errors because such and such object collection doesn't have the property region defined. Instead I have to configure the "Texas Region view-only" permissions as if I'm trying to add custom permissions to modify some specific vlan with IDs ranging from 123 to 234 in one specific location that is active and is not reserved and has a tag called purple attached to it with a tenant name that doesn't start from the letter A. I hope you get the idea - the most obvious general permission use cases, besides "admin" that is, require complex filtering, tagging and a combination of both. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurepending closurestatus: under review labels 2025-12-29 19:43:06 +01:00
adam closed this issue 2025-12-29 19:43:06 +01:00
adam commented 2025-12-29 19:43:07 +01:00
Author
Owner
Copy Link

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

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 (Jun 30, 2022): 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 19:43:07 +01:00
Author
Owner
Copy Link

@artiomello commented on GitHub (Jun 30, 2022):

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.

Hi. I've updated the Use Case in the main post above. I'm not a developer therefore I don't understand how deeply you want me to convey the idea. Same goes for DB changes and APIs - how am I supposed to know what you guys need to change in order for this to work smoothly out-of-the-box. I think it's pretty straight-forward though. Either that or I'm blindly missing some configuration tick or trick to achieve the result. Anyway, hope that helps. Thank you.

@artiomello commented on GitHub (Jun 30, 2022): > 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. Hi. I've updated the Use Case in the main post above. I'm not a developer therefore I don't understand how deeply you want me to convey the idea. Same goes for DB changes and APIs - how am I supposed to know what you guys need to change in order for this to work smoothly out-of-the-box. I think it's pretty straight-forward though. Either that or I'm blindly missing some configuration tick or trick to achieve the result. Anyway, hope that helps. Thank you.
adam commented 2025-12-29 19:43:07 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 14, 2022):

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. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Sep 14, 2022): 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. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:43:07 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Oct 14, 2022):

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 (Oct 14, 2022): 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 status: under review 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#6610
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?