Ability to disable individual apps (tenancy, secrets, etc.) #326

Closed
opened 2025-12-29 16:20:57 +01:00 by adam · 4 comments
Owner

Originally created by @anthraxau on GitHub (Aug 4, 2016).

Would be nice if we can disable the new tenants part as not all of us work on a customer basis.

Originally created by @anthraxau on GitHub (Aug 4, 2016). Would be nice if we can disable the new tenants part as not all of us work on a customer basis.
adam closed this issue 2025-12-29 16:20:57 +01:00
Author
Owner

@fltchr commented on GitHub (Aug 4, 2016):

It might be nice to be able to disable individual modules as well. For example, we would likely not use the secrets feature and will want to ensure that nothing is entered there. For the majority of our folks, they will likely be setup in a user group which disallows creating secrets, but it would be nice to just administratively disable it.

@fltchr commented on GitHub (Aug 4, 2016): It might be nice to be able to disable individual modules as well. For example, we would likely not use the secrets feature and will want to ensure that nothing is entered there. For the majority of our folks, they will likely be setup in a user group which disallows creating secrets, but it would be nice to just administratively disable it.
Author
Owner

@LukeDRussell commented on GitHub (Aug 7, 2016):

I could see disabling modules being really useful for many people.

@LukeDRussell commented on GitHub (Aug 7, 2016): I could see disabling modules being really useful for many people.
Author
Owner

@dirtycajunrice commented on GitHub (Aug 23, 2017):

+1 for disabling modules. Our company uses netbox for the IPAM greatness only, and would love to disable DCIM/Secrets.

@dirtycajunrice commented on GitHub (Aug 23, 2017): +1 for disabling modules. Our company uses netbox for the IPAM greatness only, and would love to disable DCIM/Secrets.
Author
Owner

@jeremystretch commented on GitHub (Nov 5, 2018):

Given how much NetBox has grown and how intertwined its features are, this would take far too much development effort for the modest benefit. Closing this out.

Edit: I should point out that #323 will likely have the same substantial effect as the change proposed here anyway.

@jeremystretch commented on GitHub (Nov 5, 2018): Given how much NetBox has grown and how intertwined its features are, this would take far too much development effort for the modest benefit. Closing this out. Edit: I should point out that #323 will likely have the same substantial effect as the change proposed here anyway.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#326