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

Add authorized persons and contacts to tenants #390

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

Originally created by @nev275 on GitHub (Aug 24, 2016).

Good evening,

I would like to request an additional Tenant information fields as authorized persons who should be able to visit the tenant equipment in the data center and authorized mail and phone contacts from which the tenant will be able to ask for equipment restart, re-configuration and so on. It will be really useful for us and i hope for others.

Thank you!

Originally created by @nev275 on GitHub (Aug 24, 2016). Good evening, I would like to request an additional Tenant information fields as authorized persons who should be able to visit the tenant equipment in the data center and authorized mail and phone contacts from which the tenant will be able to ask for equipment restart, re-configuration and so on. It will be really useful for us and i hope for others. Thank you!
adam closed this issue 2025-12-29 16:21:36 +01:00
adam commented 2025-12-29 16:21:36 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 22, 2016):

This seems like the sort of thing where everyone is going to want something slightly different, and trying to force information into a particular format is going to do more harm than good. We also don't want to creep outside NetBox's focus on infrastructure management. I think it's sufficient to store such information in the comments field of the Tenant object.

@jeremystretch commented on GitHub (Nov 22, 2016): This seems like the sort of thing where everyone is going to want something slightly different, and trying to force information into a particular format is going to do more harm than good. We also don't want to creep outside NetBox's focus on infrastructure management. I think it's sufficient to store such information in the comments field of the Tenant object.
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#390
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?