I can't edit this post anymore but I would like to add to this:

Please give a quick overview of your product feature request or feedback and note who in your org is affected by this issue [ex. agents, admins, customers, etc.]. (2-3 sentences)

I would like all admin dedicated permissions to be broken up into subpermissions as there are teams dedicated to managing certain features but can only do so if they are admins.

What problem do you see this solving? (1-2 sentences)

This would reduce the amount of admins we have, the amount of issues we see when admins untrained in an area change a feature they are not trained for as well as reduce the need to check the audit log regularly of admin changes

When was the last time you were affected by this lack of functionality, or specific tool? What happened? How often does this problem occur and how does this impact your business? (3-4 sentences)

We have a team dedicated to onboardings but they require to be an admin (I know subpermission is coming) but they also need to be able to edit apps (permission is not coming). This is something we encounter multiple times a day. As admins have all access, we see teams performing onboardings when they shouldn't, adjusting triggers when they aren't trained, updating apps when they shouldn't, changing role permissions etc just because they need access to an admin only feature

Are you currently using a workaround to solve this problem? (If yes, please explain) (1-2 sentences)

Right now, we are diligently checking the audit log to see if any admin feature is touched. However, a lot is missed because there is so much not in the audit log as well as it is unclear who is touching something because they are trained vrs not. Instead, we have to only look at what we KNOW should not be edited (like role permissions).

What would be your ideal solution to this problem? How would it work or function? (1-2 sentences)

We need to have each system setting that can be changed broken up into a subpermission. I did some digging and found some common features that only admins can edit at this time:

Read only of business rules/system settings - this would be good for QA so they can see what is setup but not change it
Junior admins - admins dedicated to only being able to update SOME triggers/automations, system settings etc. Reason being is that there are some complex triggers that should never be updated while others that can be regularly updated. As well as restricting what they can set in a trigger. They shouldn't ever be actioning certain conditions (never set tags). Or a "clone only" of a trigger template we setup that they can adjust certain conditions
Install/edit apps - we have developers dedicated to managing their apps but no other system settings. But we would also want to limit who can edit which app to reduce the chance someone else can't edit the app. Select an Address app is one of these apps
Audit log
Bulk import orgs or users
Delete call recordings from tickets
Edit subscriptions (including trials)
Generate and manage API tokens - Also something our dev's need access to setup integrations
Accessing Team members in Admin Centre
Ticket access - we have teams that need to access their tickets for their team but shouldn't be able to be assigned tickets
Pro-active notifications from Zendesk Premier to only Admins
SSO editing/creation
Offboarding admins - the only ones that can edit an admin is another admin or account owner (even with the new team members subpermission)