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

User to access only specific site/region related data #8528

New Issue
Closed
opened 2025-12-29 20:37:48 +01:00 by adam · 3 comments
adam commented 2025-12-29 20:37:48 +01:00
Owner
Copy Link

Originally created by @trs91km on GitHub (Aug 29, 2023).

NetBox version

v3.5.4

Feature type

New functionality

Proposed functionality

Our netbox is accessed by many team in different region, I want to restrict users from US region only to access data for US alone

Use case

This will help us to restrict users to access/modify data only belongs to them

Database changes

No response

External dependencies

No response

Originally created by @trs91km on GitHub (Aug 29, 2023). ### NetBox version v3.5.4 ### Feature type New functionality ### Proposed functionality Our netbox is accessed by many team in different region, I want to restrict users from US region only to access data for US alone ### Use case This will help us to restrict users to access/modify data only belongs to them ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 20:37:48 +01:00
adam closed this issue 2025-12-29 20:37:48 +01:00
adam commented 2025-12-29 20:37:49 +01:00
Author
Owner
Copy Link

@abhi1693 commented on GitHub (Aug 29, 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.

@abhi1693 commented on GitHub (Aug 29, 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:37:49 +01:00
Author
Owner
Copy Link

@Mailstorm-ctrl commented on GitHub (Aug 30, 2023):

I'm not sure if it's available in your version, but you can already do this permission constraints
https://demo.netbox.dev/static/docs/administration/permissions/

@Mailstorm-ctrl commented on GitHub (Aug 30, 2023): I'm not sure if it's available in your version, but you can already do this permission constraints https://demo.netbox.dev/static/docs/administration/permissions/
adam commented 2025-12-29 20:37:49 +01:00
Author
Owner
Copy Link

@trs91km commented on GitHub (Aug 30, 2023):

@Mailstorm-ctrl excellent, this is exactly what I need, thanks

@abhi1693 I will close this, thanks much

@trs91km commented on GitHub (Aug 30, 2023): @Mailstorm-ctrl excellent, this is exactly what I need, thanks @abhi1693 I will close this, thanks much
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#8528
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?