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

Parent Child Tenant Hierarchy #8120

New Issue
Closed
opened 2025-12-29 20:32:42 +01:00 by adam · 5 comments
adam commented 2025-12-29 20:32:42 +01:00
Owner
Copy Link

Originally created by @wirestar on GitHub (May 26, 2023).

NetBox version

3.4.3

Feature type

New functionality

Proposed functionality

We would like to add the parent field on tenant creation, and be able to select another tenant as the parent.

Other records, like regions, and locations have this similar parent field that "can be nested recursively to construct a hierarchy" functionality.

Use case

A tenant is considered a customer for us. Our accounting and billing systems allow for parent and child relationships for customers.
I am aware of tenant groups, and those have the parent field to select another group, but this is not quite the same. This is a grouping of tenants, but doesn't show the hierarchy or relationship of tenants.

Database changes

Unknown

External dependencies

Unknown

Originally created by @wirestar on GitHub (May 26, 2023). ### NetBox version 3.4.3 ### Feature type New functionality ### Proposed functionality We would like to add the parent field on tenant creation, and be able to select another tenant as the parent. Other records, like regions, and locations have this similar parent field that "can be nested recursively to construct a hierarchy" functionality. ### Use case A tenant is considered a customer for us. Our accounting and billing systems allow for parent and child relationships for customers. I am aware of tenant groups, and those have the parent field to select another group, but this is not quite the same. This is a grouping of tenants, but doesn't show the hierarchy or relationship of tenants. ### Database changes Unknown ### External dependencies Unknown
adam added the type: featurepending closurestatus: revisions needed labels 2025-12-29 20:32:42 +01:00
adam closed this issue 2025-12-29 20:32:42 +01:00
adam commented 2025-12-29 20:32:42 +01:00
Author
Owner
Copy Link

@abhi1693 commented on GitHub (May 26, 2023):

I'm not sure if this will be accepted but this will be blocked until https://github.com/netbox-community/netbox/issues/12552 is resolved.

@abhi1693 commented on GitHub (May 26, 2023): I'm not sure if this will be accepted but this will be blocked until https://github.com/netbox-community/netbox/issues/12552 is resolved.
adam commented 2025-12-29 20:32:43 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 26, 2023):

You haven't explained your use case. NetBox provides for contact assignments where separate points of contact must be tracked within a tenant. Can you provide an example where this would not be sufficient?

@jeremystretch commented on GitHub (May 26, 2023): You haven't explained your use case. NetBox provides for [contact assignments](https://docs.netbox.dev/en/stable/features/contacts/) where separate points of contact must be tracked within a tenant. Can you provide an example where this would not be sufficient?
adam commented 2025-12-29 20:32:43 +01:00
Author
Owner
Copy Link

@wirestar commented on GitHub (May 31, 2023):

@jeremystretch I am not understanding how contact assignments would show the hierarchies and relationships between tenants? Can you explain as I might be overlooking something?

"A contact represent an individual" person whereas "tenants are used to represent individual customers or internal departments within an organization" according to the NetBox documentation.

Most of the large CRMs like Salesforce or ERPs have the concept of a tenant being a customer, and an employee working at the customer being a contact linked to that customer or vendor.

Our use case would be to have our existing CRMs and ERPs integrated to NetBox. So when a parent customer is created in the CRM or ERP, it syncs to NetBox using the API. If a child record is created, it pushes that as well also showing the parent as it does in the CRM or ERP.

Some areas of NetBox support this concept today such as regions and locations, but then other sections don't but allow a parent to be define but instead have groups (tenants and sites for example). Why is there a difference between these object types?

@wirestar commented on GitHub (May 31, 2023): @jeremystretch I am not understanding how contact assignments would show the hierarchies and relationships between tenants? Can you explain as I might be overlooking something? "A contact represent an individual" person whereas "tenants are used to represent individual customers or internal departments within an organization" according to the NetBox documentation. Most of the large CRMs like Salesforce or ERPs have the concept of a tenant being a customer, and an employee working at the customer being a contact linked to that customer or vendor. Our use case would be to have our existing CRMs and ERPs integrated to NetBox. So when a parent customer is created in the CRM or ERP, it syncs to NetBox using the API. If a child record is created, it pushes that as well also showing the parent as it does in the CRM or ERP. Some areas of NetBox support this concept today such as regions and locations, but then other sections don't but allow a parent to be define but instead have groups (tenants and sites for example). Why is there a difference between these object types?
adam commented 2025-12-29 20:32:43 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 30, 2023):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Aug 30, 2023): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:32:43 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 29, 2023):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Sep 29, 2023): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure status: revisions needed 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#8120
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?