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 #6612

New Issue
Closed
opened 2025-12-29 19:43:06 +01:00 by adam · 1 comment
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

Python version

3.10

Steps to Reproduce

Try to configure view-only permissions to any logical subset in less than a day.

Expected Behavior

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.

Observed Behavior

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.

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.

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.

Originally created by @artiomello on GitHub (Jun 30, 2022). ### NetBox version v3.2.3 ### Python version 3.10 ### Steps to Reproduce Try to configure view-only permissions to any logical subset in less than a day. ### Expected Behavior 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. ### Observed Behavior 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. 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. 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.
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):

This is obviously not a bug. You're welcome to open a feature request if you'd like to propose a specific improvement.

@jeremystretch commented on GitHub (Jun 30, 2022): This is obviously not a bug. You're welcome to open a [feature request](https://github.com/netbox-community/netbox/issues/new?assignees=&labels=type%3A+feature&template=feature_request.yaml) if you'd like to propose a specific improvement.
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#6612
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?