Title: Multisite compatibility
Last modified: June 6, 2023

---

# Multisite compatibility

 *  Resolved [Opeyemi Timothy](https://wordpress.org/support/users/sirotwo/)
 * (@sirotwo)
 * [3 years ago](https://wordpress.org/support/topic/multisite-compatibility-126/)
 * Is this awesome plugin compatible with wordpress multisite??

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

 *  Plugin Author [Daniel Iser](https://wordpress.org/support/users/danieliser/)
 * (@danieliser)
 * [3 years ago](https://wordpress.org/support/topic/multisite-compatibility-126/#post-16799178)
 * [@sirotwo](https://wordpress.org/support/users/sirotwo/) – In what way? The plugin
   will work fine for all of the sites if network activated, but currently no network
   wide restriction capabilities. It would still be per site, but I can add that
   to the list for possible future features.
 *  Thread Starter [Opeyemi Timothy](https://wordpress.org/support/users/sirotwo/)
 * (@sirotwo)
 * [3 years ago](https://wordpress.org/support/topic/multisite-compatibility-126/#post-16799299)
 * Okay,
 * Thanks.

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

The topic ‘Multisite compatibility’ is closed to new replies.

 * ![](https://ps.w.org/content-control/assets/icon-256x256.gif?rev=2968535)
 * [Content Control - The Ultimate Content Restriction Plugin! Restrict Content, Create Conditional Blocks & More](https://wordpress.org/plugins/content-control/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/content-control/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/content-control/)
 * [Active Topics](https://wordpress.org/support/plugin/content-control/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/content-control/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/content-control/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [Opeyemi Timothy](https://wordpress.org/support/users/sirotwo/)
 * Last activity: [3 years ago](https://wordpress.org/support/topic/multisite-compatibility-126/#post-16799299)
 * Status: resolved