Netbox: Ability to disable individual apps (tenancy, secrets, etc.)
Would be nice if we can disable the new tenants part as not all of us work on a customer basis.
anthraxau
All 4 comments
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
on 4 Aug 2016
I could see disabling modules being really useful for many people.
LukeDRussell
on 7 Aug 2016
+1 for disabling modules. Our company uses netbox for the IPAM greatness only, and would love to disable DCIM/Secrets.
DirtyCajunRice
on 23 Aug 2017
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
on 5 Nov 2018
Related issues
tyler-8
路
3Comments
soer7022
路
3Comments
aarjbdea
路
3Comments
Grokzen
路
3Comments
Ali-Yazdani
路
3Comments
Most helpful comment
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.