starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 13:53:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Multi-tenant UI improvements #344

New Issue
Closed
opened 2025-12-29 16:21:05 +01:00 by adam · 3 comments
adam commented 2025-12-29 16:21:05 +01:00
Owner
Copy Link

Originally created by @bzoel on GitHub (Aug 9, 2016).

While testing out the multi-tenant support, I found myself having to constantly select the tenant I am working in each time I added a device or viewed a page. I would suggest that there be a way to select the tenant you're working in, for example:

When I want to work on something for "Company A", I could go to a 'Select Tenant' box at the top of the page and select Company A. While this selection is in place, additions and views could be generated as though I was using NetBox for only Company A (without multi-tenant support). I could then change this global selection to "Company B", and the process would be similar.

I'm not sure if this is totally clear, but if you have used Cisco Prime, it functions similarly when you use mutli-tenant support. Let me know if I need to clarify further, or if others feel this wouldn't make sense in their case.

Originally created by @bzoel on GitHub (Aug 9, 2016). While testing out the multi-tenant support, I found myself having to constantly select the tenant I am working in each time I added a device or viewed a page. I would suggest that there be a way to select the tenant you're working in, for example: When I want to work on something for "Company A", I could go to a 'Select Tenant' box at the top of the page and select Company A. While this selection is in place, additions and views could be generated as though I was using NetBox for only Company A (without multi-tenant support). I could then change this global selection to "Company B", and the process would be similar. I'm not sure if this is totally clear, but if you have used Cisco Prime, it functions similarly when you use mutli-tenant support. Let me know if I need to clarify further, or if others feel this wouldn't make sense in their case.
adam added the type: feature label 2025-12-29 16:21:05 +01:00
adam closed this issue 2025-12-29 16:21:05 +01:00
adam commented 2025-12-29 16:21:06 +01:00
Author
Owner
Copy Link

@bzoel commented on GitHub (Aug 9, 2016):

Maybe this could also be extended to allow specific users access to only specific tenants... although that is probably a bit more involved.

@bzoel commented on GitHub (Aug 9, 2016): Maybe this could also be extended to allow specific users access to only specific tenants... although that is probably a bit more involved.
adam commented 2025-12-29 16:21:06 +01:00
Author
Owner
Copy Link

@traveler3468 commented on GitHub (Jun 21, 2017):

In total agreement that this would be a necessary feature! My org needs NetBox and will most likely still use it (still in POC phase preping for presentation). Having access restricted to specific tenants or sites would be massively awesome!

@jeremystretch btw: Fantastic work on putting this together! I know how much work goes into something like this and you've done a fantastic job!

@traveler3468 commented on GitHub (Jun 21, 2017): In total agreement that this would be a necessary feature! My org needs NetBox and will most likely still use it (still in POC phase preping for presentation). Having access restricted to specific tenants or sites would be massively awesome! @jeremystretch btw: Fantastic work on putting this together! I know how much work goes into something like this and you've done a fantastic job!
adam commented 2025-12-29 16:21:07 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 20, 2017):

Seems like this is probably better covered by #554. Closing this out.

@jeremystretch commented on GitHub (Oct 20, 2017): Seems like this is probably better covered by #554. Closing this out.
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#344
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?