Hi,
They(Admin role) would still need to understand how to use Update Sets properly though. I've seen some clients grant catalog_admin without training those individuals and their instances get messy. When done correctly, these "sub" admin roles work great!
I have seen a few gaps and "missing" capabilities for those admins that one might expect to exist, so be prepared to modify your Access Controls a bit as you start to use these sub-admin admin roles.
In terms of segregating by application, some of the more recent apps like PPM and Release include an "admin" role, but they do not segregate "full" admin type of privileges to those apps. They basically add full-time write and delete to tasks in those spaces. You'll need to build some pretty extensive Access Controls to segregate "full" customization/configuration type of admin role by application as you have described.
It may make sense in development environments to grant the admin role extensively. But in production, a better approach is to grant administrative users one or more special administrative roles that are specific to the functions they perform. For example, the catalog_admin role grants privileges needed to manage the Service Catalog application, the report_admin role allows users to manage reports, and so forth.
If my answer helps you please mark as correct/helpful.
Regards,
Monali Patil
Developer
