Nested tenant groups #3170

Closed
opened 2025-12-29 18:26:18 +01:00 by adam · 5 comments
Owner

Originally created by @ebusto on GitHub (Jan 16, 2020).

Originally assigned to: @jeremystretch on GitHub.

Environment

  • Python version: 3.6
  • NetBox version: 2.6.12

Proposed Functionality

Similar to regions, tenant groups should be nestable, in order to represent organizations with more than two levels.

For example: IT -> Infrastructure -> Network Support

Use Case

This allows companies of any appreciable size to share one NetBox instance, while tracking organizational and team level ownership accurately, without having to resort to ugly hacks or naming conventions.

Database Changes

Add a parent attribute to the TenantGroup model.

External Dependencies

None.

Originally created by @ebusto on GitHub (Jan 16, 2020). Originally assigned to: @jeremystretch on GitHub. ### Environment * Python version: 3.6 * NetBox version: 2.6.12 ### Proposed Functionality Similar to regions, tenant groups should be nestable, in order to represent organizations with more than two levels. For example: IT -> Infrastructure -> Network Support ### Use Case This allows companies of any appreciable size to share one NetBox instance, while tracking organizational and team level ownership accurately, without having to resort to ugly hacks or naming conventions. ### Database Changes Add a `parent` attribute to the `TenantGroup` model. ### External Dependencies None.
adam added the status: acceptedtype: feature labels 2025-12-29 18:26:18 +01:00
adam closed this issue 2025-12-29 18:26:18 +01:00
Author
Owner

@tb-killa commented on GitHub (Jan 18, 2020):

https://github.com/netbox-community/netbox/issues/2815

@tb-killa commented on GitHub (Jan 18, 2020): https://github.com/netbox-community/netbox/issues/2815
Author
Owner

@jeremystretch commented on GitHub (Jan 21, 2020):

This differs from #2815, which was to allow the assignment of a Tenant to multiple TenantGroups. Here, Tenants are still limited to a single TenantGroup association, but TenantGroups themselves can belong to other TenantGroups (similar to how Regions can be nested).

@jeremystretch commented on GitHub (Jan 21, 2020): This differs from #2815, which was to allow the assignment of a Tenant to multiple TenantGroups. Here, Tenants are still limited to a single TenantGroup association, but TenantGroups themselves can belong to other TenantGroups (similar to how Regions can be nested).
Author
Owner

@jeremystretch commented on GitHub (Jan 21, 2020):

Cross-referencing with #1754 (RackGroup nesting)

@jeremystretch commented on GitHub (Jan 21, 2020): Cross-referencing with #1754 (RackGroup nesting)
Author
Owner

@itmicus commented on GitHub (Jan 22, 2020):

May be it is part of it #554

@itmicus commented on GitHub (Jan 22, 2020): May be it is part of it #554
Author
Owner

@ebusto commented on GitHub (Jan 23, 2020):

I don't think it should be coupled to #554.

I've implemented a simple and opinionated RBAC module for NetBox, and as it is a non-trivial task, it would unnecessarily delay this simple change.

@ebusto commented on GitHub (Jan 23, 2020): I don't think it should be coupled to #554. I've implemented a simple and opinionated [RBAC module for NetBox](https://pypi.org/project/netbox-rbac/), and as it is a non-trivial task, it would unnecessarily delay this simple change.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#3170