Title: Multisite, proper workflow
Last modified: May 13, 2026

---

# Multisite, proper workflow

 *  Resolved [neuromatto2012](https://wordpress.org/support/users/neuromatto2012/)
 * (@neuromatto2012)
 * [2 weeks, 1 day ago](https://wordpress.org/support/topic/multisite-proper-workflow/)
 * Hi Team,
 * I’ve read in the FAQ that this plugin is fully compatible with multisite installations,
   which is my use case. Great.
   Before installing and testing it, I would like to
   understand a little more about the setup. Specifically, what is the suggested
   way to activate it:1. network activate (with it populating tables and meta for
   each site2. single site activation.I believe the general preferred way from admins
   is the second one, but thought worth checking.
 * Thank you

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

 *  Plugin Support [Amrit Kumar Shrestha](https://wordpress.org/support/users/shresthauzwal/)
 * (@shresthauzwal)
 * [2 weeks ago](https://wordpress.org/support/topic/multisite-proper-workflow/#post-18906713)
 * Hi [@neuromatto2012](https://wordpress.org/support/users/neuromatto2012/),
 * Based on WordPress Multisite best practices and how LMS plugins work, here is
   what you should know:
 * Option 1 — Network Activation
 * When a plugin is network-activated, it becomes active on every site in the network
   and individual site admins cannot deactivate it. However, there is an important
   risk to be aware of: when you perform a network activation, the plugin’s installation
   procedure, which creates database tables and runs setup scripts, is only triggered
   for the main site and not for all subsites in the network. This means Masteriyo’s
   database tables may not be created correctly for each subsite, which can lead
   to errors or missing functionality.
 * Option 2 — Per-Site Activation [ Recommended ]
 * It is always best to test a plugin on a single site first before network-activating
   it, as things can get complicated very quickly in a multisite environment.
 * Per-site activation ensures that:
    1. Each subsite properly runs the plugin’s setup routine.
    2. Database tables and metadata are created correctly for each site.
    3. Site admins have individual control over the plugin.
    4. Unexpected conflicts across the entire network are avoided.
 * While you will need to track which sites have the plugin activated, this approach
   gives you much greater flexibility and control overall. Your instinct is correct.
   The per-site (single site) activation is the preferred and safer approach for
   a plugin like Masteriyo LMS, especially because it is a complex plugin that creates
   its own database tables, pages, and settings during activation.
 * Best Regards!
 *  Thread Starter [neuromatto2012](https://wordpress.org/support/users/neuromatto2012/)
 * (@neuromatto2012)
 * [2 weeks ago](https://wordpress.org/support/topic/multisite-proper-workflow/#post-18907011)
 * Great, thank you

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

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fmultisite-proper-workflow%2F%3Foutput_format%3Dmd&locale=en_US)
to reply to this topic.

 * ![](https://ps.w.org/learning-management-system/assets/icon-256x256.gif?rev=3520181)
 * [Masteriyo LMS – LMS Course Builder, Quizzes & Certificates](https://wordpress.org/plugins/learning-management-system/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/learning-management-system/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/learning-management-system/)
 * [Active Topics](https://wordpress.org/support/plugin/learning-management-system/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/learning-management-system/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/learning-management-system/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [neuromatto2012](https://wordpress.org/support/users/neuromatto2012/)
 * Last activity: [2 weeks ago](https://wordpress.org/support/topic/multisite-proper-workflow/#post-18907011)
 * Status: resolved