Add Specific Permissions for Managing 3rd Party Updates
I would like to see specific permissions for adding/managing a 3rd party software update custom catalog as well as a specific permission to "Publish third-party software update content".
In our multi-tenancy ConfigMgr environment we have lots of different organizations using the same instance and being able to limit this functionality to just the top-level administrators will prevent hundreds if not thousands of unnecessary updates from being published.
This is not functionality we plan to add in the future.
Michael Schultz commented
I need to free up some votes for this as well. I have the same issue. We have a separate patching team and I need to give them rights to manage third party patches without giving the keys to the city.