NeoAnd/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2025-12-18 11:22:25 -06:00
Code Issues Actions 10 Packages Projects Releases Wiki Activity

Closes #412: Tenant group assignment is no longer mandatory

Browse Source
This commit is contained in:
Jeremy Stretch
2016-08-02 16:04:25 -04:00
parent d677f13eb0
commit 8c3b7c9d7c
5 changed files with 54 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
docs/data-model/tenancy.md
View File

@@ -4,6 +4,19 @@ NetBox supports the concept of individual tenants within its parent organization
A tenant represents a discrete organization. Certain resources within NetBox can be assigned to a tenant. This makes it very convenient to track which resources are assigned to which customers, for instance.
The following objects can be assigned to tenants:
* Sites
* Racks
* Devices
* VRFs
* Prefixes
* IP addresses
* VLANs
* Circuits
If a prefix or IP address is not assigned to a tenant, it will appear to inherit the tenant to which its parent VRF is assigned, if any.
### Tenant Groups
Tenants are grouped by type. For instance, you might create one group called "Customers" and one called "Acquisitions."
Tenants can be grouped by type. For instance, you might create one group called "Customers" and one called "Acquisitions." The assignment of tenants to groups is optional.