Title: Multisite Permissions
Last modified: September 1, 2016

---

# Multisite Permissions

 *  [gpirie](https://wordpress.org/support/users/gpirie/)
 * (@gpirie)
 * [10 years ago](https://wordpress.org/support/topic/multisite-permissions-1/)
 * Hi,
 * I’ve installed the plugin on a multi-site install and have ran into the permissions
   issue that I’ve seen others suffer from – was there any resolution for this?
 * The only way I can update scores and results is directly in the database, which
   obviously isn’t ideal.
 * I’m logged in as super admin, plugin set up with active predictions. I tried 
   to network activate the plugin but that takes me to the root site plugin when
   trying to update scores.
 * [https://wordpress.org/plugins/world-cup-predictor/](https://wordpress.org/plugins/world-cup-predictor/)

Viewing 1 replies (of 1 total)

 *  Plugin Author [landoweb](https://wordpress.org/support/users/landoweb/)
 * (@landoweb)
 * [9 years, 1 month ago](https://wordpress.org/support/topic/multisite-permissions-1/#post-9081401)
 * This will be corrected in version 2.0 of the plugin, when the administrative 
   panel of the plugin will be reformulated.

Viewing 1 replies (of 1 total)

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

 * ![](https://s.w.org/plugins/geopattern-icon/world-cup-predictor.svg)
 * [World Cup Predictor](https://wordpress.org/plugins/world-cup-predictor/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/world-cup-predictor/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/world-cup-predictor/)
 * [Active Topics](https://wordpress.org/support/plugin/world-cup-predictor/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/world-cup-predictor/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/world-cup-predictor/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [landoweb](https://wordpress.org/support/users/landoweb/)
 * Last activity: [9 years, 1 month ago](https://wordpress.org/support/topic/multisite-permissions-1/#post-9081401)
 * Status: not resolved