Title: Allow controlled admins to edit plugins?
Last modified: May 29, 2020

---

# Allow controlled admins to edit plugins?

 *  [slapbox](https://wordpress.org/support/users/slapbox/)
 * (@slapbox)
 * [6 years, 2 months ago](https://wordpress.org/support/topic/allow-controlled-admins-to-edit-plugins/)
 * Obviously this creates a major loophole in the security functionality, but it
   would be a really helpful feature to have.
 * **Reason for needing this:** I’d like to give vendor support staff access to 
   the plugin editor without giving them effortless access to other areas of the
   site that they would traditionally be able to access like user accounts and the
   like. I trust the people, so it’s not so much a security concern as a user privacy
   one.
 * Of course, if you can prevent them from editing only Controlled Admin Access 
   then the security loophole is more or less avoided, though there’s plenty of 
   other ways to do damage.
 * Thoughts? Thanks for the great plugin!

Viewing 5 replies - 1 through 5 (of 5 total)

 *  Thread Starter [slapbox](https://wordpress.org/support/users/slapbox/)
 * (@slapbox)
 * [6 years, 2 months ago](https://wordpress.org/support/topic/allow-controlled-admins-to-edit-plugins/#post-12912323)
 * Specifically, to clarify, I’m referring to the Plugin Editor feature built into
   WordPress.
 *  Thread Starter [slapbox](https://wordpress.org/support/users/slapbox/)
 * (@slapbox)
 * [6 years, 2 months ago](https://wordpress.org/support/topic/allow-controlled-admins-to-edit-plugins/#post-12912368)
 * Doh… I didn’t realize you could drop these things down for more options. This
   plugin is even greater than I had thought.
 * Unfortunately still can’t check that. Again, totally understand why, but it would
   be a great option to add with a disclaimer about the danger.
    -  This reply was modified 6 years, 2 months ago by [slapbox](https://wordpress.org/support/users/slapbox/).
 *  Thread Starter [slapbox](https://wordpress.org/support/users/slapbox/)
 * (@slapbox)
 * [6 years, 2 months ago](https://wordpress.org/support/topic/allow-controlled-admins-to-edit-plugins/#post-12945506)
 * [@waseem_senjer](https://wordpress.org/support/users/waseem_senjer/) any comment?
   I understand it’s sort of an edge case but I’d love to see it implemented with
   a warning rather than completely blocked off.
 *  Plugin Author [Waseem Senjer](https://wordpress.org/support/users/waseem_senjer/)
 * (@waseem_senjer)
 * [6 years, 2 months ago](https://wordpress.org/support/topic/allow-controlled-admins-to-edit-plugins/#post-12945677)
 * Hi [@slapbox](https://wordpress.org/support/users/slapbox/)
    I like the idea 
   of enabling all of the checkboxes to be enabled. And a warning message can be
   useful to warn admins about enabling these options.
 * I will add this in the next release of the plugin. Hopefully, next week.
 * Thanks for sharing this with me.
    Waseem
 *  Thread Starter [slapbox](https://wordpress.org/support/users/slapbox/)
 * (@slapbox)
 * [6 years, 2 months ago](https://wordpress.org/support/topic/allow-controlled-admins-to-edit-plugins/#post-12948708)
 * That’s awesome to hear! Thanks a ton for everything!

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Allow controlled admins to edit plugins?’ is closed to new replies.

 * ![](https://ps.w.org/controlled-admin-access/assets/icon-128x128.gif?rev=2773094)
 * [Controlled Admin Access](https://wordpress.org/plugins/controlled-admin-access/)
 * [Support Threads](https://wordpress.org/support/plugin/controlled-admin-access/)
 * [Active Topics](https://wordpress.org/support/plugin/controlled-admin-access/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/controlled-admin-access/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/controlled-admin-access/reviews/)

 * 5 replies
 * 2 participants
 * Last reply from: [slapbox](https://wordpress.org/support/users/slapbox/)
 * Last activity: [6 years, 2 months ago](https://wordpress.org/support/topic/allow-controlled-admins-to-edit-plugins/#post-12948708)
 * Status: not resolved