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

Customise 'Tenants' name #664

New Issue
Closed
opened 2025-12-29 16:24:34 +01:00 by adam · 1 comment
adam commented 2025-12-29 16:24:34 +01:00
Owner
Copy Link

Originally created by @InsaneSplash on GitHub (Jan 26, 2017).

I'd like to be able to dynamically change the name 'Tenants' to something more relevant to our organisations infrastructure deployment. An example would be 'Customers'.

We use Netbox to manage all our remote CPE and Switching infrastructure at our customers sites rather than hosting centers.

Would something like this be considered in the future?

Originally created by @InsaneSplash on GitHub (Jan 26, 2017). I'd like to be able to dynamically change the name 'Tenants' to something more relevant to our organisations infrastructure deployment. An example would be 'Customers'. We use Netbox to manage all our remote CPE and Switching infrastructure at our customers sites rather than hosting centers. Would something like this be considered in the future?
adam closed this issue 2025-12-29 16:24:34 +01:00
adam commented 2025-12-29 16:24:34 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 26, 2017):

The term tenancy was chosen for its ambiguity, to ensure that it would apply to most use cases. "Customers" might make more sense for your case, but it would make less sense for a NetBox installation tracking subsidiary companies, internal departments, schools, etc. A customer is still a tenant of your network even if you don't physically house any of their resources.

Edit: You can group tenants by role, also.

@jeremystretch commented on GitHub (Jan 26, 2017): The term _tenancy_ was chosen for its ambiguity, to ensure that it would apply to most use cases. "Customers" might make more sense for your case, but it would make less sense for a NetBox installation tracking subsidiary companies, internal departments, schools, etc. A customer is still a tenant of your network even if you don't physically house any of their resources. Edit: You can group tenants by role, also.
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
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#664
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?