Setyenv · Docs
  • English
  • Spanish
  • Chinese
  • Japanese
  • Arabic
  • German
  • French
  • Hindi
  • Indonesian
  • Italian
  • Dutch
  • Portuguese
  • Russian
  • Turkish

WordPress multisite

WP-PFWorkflow on WordPress multisite networks. Each site in the network operates independently — workflows, executions, and settings are per-site.

Per-site isolation

  • Each site has its own workflows (stored as per-site CPT pfw_workflow)
  • Each site has its own execution queue and logs
  • License keys are per-site (one license = one site activation)
  • Network admins do NOT automatically see all sites' workflows

Activation

  • Network activate: The plugin is available to all sites but not active on any until individually activated
  • Per-site activate: Standard single-site activation flow
  • Each site requires its own license key

Database tables

All pfw_* tables use the $wpdb->prefix for the current site. On multisite, each site has its own set of tables (e.g., wp_2_pfw_executions, wp_3_pfw_executions, etc.).

Capabilities

Capabilities are per-site. Granting pfw_manage_workflows to a role on Site A does not grant it on Site B. Network admins with manage_network_options get all capabilities on all sites.