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

Limit Access #9519

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

Originally created by @RenatoPereira91 on GitHub (Apr 22, 2024).

NetBox version

v3.7.3

Feature type

New functionality

Proposed functionality

I'm trying to allow control access for other employers, but always have one thing that not show, example the interfaces of devices.

I would like one way that I can easier set (site or tenant) that one user can access and all thing under can access too.

Use case

Ease way to segregate access

Database changes

No response

External dependencies

No response

Originally created by @RenatoPereira91 on GitHub (Apr 22, 2024). ### NetBox version v3.7.3 ### Feature type New functionality ### Proposed functionality I'm trying to allow control access for other employers, but always have one thing that not show, example the interfaces of devices. I would like one way that I can easier set (site or tenant) that one user can access and all thing under can access too. ### Use case Ease way to segregate access ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 20:50:53 +01:00
adam closed this issue 2025-12-29 20:50:53 +01:00
adam commented 2025-12-29 20:50:53 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Apr 23, 2024):

Hello @RenatoPereira91,

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.

@DanSheps commented on GitHub (Apr 23, 2024): Hello @RenatoPereira91, 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:50:54 +01:00
Author
Owner
Copy Link

@jeffgdotorg commented on GitHub (May 17, 2024):

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.

@jeffgdotorg commented on GitHub (May 17, 2024): 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.
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 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#9519
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?