Title: Controlling Access
Last modified: August 30, 2016

---

# Controlling Access

 *  [Cars10](https://wordpress.org/support/users/shonu/)
 * (@shonu)
 * [10 years, 11 months ago](https://wordpress.org/support/topic/controlling-access-1/)
 * We use Press Permit as the core Permission system and it has proven really good
   for all sites, so far.
    Looking at Wiki, we seem to not be able to control edits
   nor reads properly A) Read denied –>Error page where the editor is still open
   despite the message “Wiki page you are looking for does not exist. Feel free 
   to create it yourself.”
 * B) Restrict write
    –> The edit tab still visible and people can edit
 * As Wikis are just another post typoe, I would really recommend to implement them
   as such, so that standard hooks for other security plugins still work.
    Referring
   to the membership plugin as the only supporting control plugin is not really 
   user friendly, as we have already purchased a [allegedly] better one (see the
   rating comments). This might become a killer criteria of using this plugin (and
   the pro)
 * thx
 * [https://wordpress.org/plugins/wordpress-wiki-plugin/](https://wordpress.org/plugins/wordpress-wiki-plugin/)

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

 *  [Bojan Radonic – WPMU DEV Support](https://wordpress.org/support/users/wpmudev-support4/)
 * (@wpmudev-support4)
 * [10 years, 11 months ago](https://wordpress.org/support/topic/controlling-access-1/#post-6240148)
 * Hey there Shonu,
 * Thanks for the suggestion, free version of the wikis is just to display how the
   plugin works in general, in premium version of the plugin there is an option 
   that allows you to select “Who can edit wiki privileges?” based on user roles.
 * The option can be found in Wiki -> Wiki Settings in premium version.
 * Best regards,
    Bojan
 *  Thread Starter [Cars10](https://wordpress.org/support/users/shonu/)
 * (@shonu)
 * [10 years, 11 months ago](https://wordpress.org/support/topic/controlling-access-1/#post-6240151)
 * Based on role, but not by supplemental roles or even individuals as possible 
   with PP Core already (rad access control, free).
 * My point is, the granularity, that we loose for Wiki. In case we needed membership
   plugin, we would run two access control plugins, which will be surely not accepted.
 * Let’s see.
 *  [Bojan Radonic – WPMU DEV Support](https://wordpress.org/support/users/wpmudev-support4/)
 * (@wpmudev-support4)
 * [10 years, 10 months ago](https://wordpress.org/support/topic/controlling-access-1/#post-6240251)
 * Hey again Shonu,
 * I completely agree on that one, adding different levels of accessibility can 
   be very usefull and I’ll definitely suggest that to our plugin developers so 
   it will be considered to be added into future versions of the plugin.
 * Thank you for your feedback 🙂
 * Best regards,
    Bojan

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

The topic ‘Controlling Access’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/wordpress-wiki-plugin_a1b1b7.svg)
 * [Wiki](https://wordpress.org/plugins/wordpress-wiki-plugin/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordpress-wiki-plugin/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordpress-wiki-plugin/)
 * [Active Topics](https://wordpress.org/support/plugin/wordpress-wiki-plugin/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordpress-wiki-plugin/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordpress-wiki-plugin/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [Bojan Radonic – WPMU DEV Support](https://wordpress.org/support/users/wpmudev-support4/)
 * Last activity: [10 years, 10 months ago](https://wordpress.org/support/topic/controlling-access-1/#post-6240251)
 * Status: not resolved