The MainWP Child Plugin only connects with a single MainWP Dashboard, so all the WordPress sites managed under your Dashboard will only respond to requests from your installation. Data tampering is almost impossible in this way.

Couldn’t someone else connect their Main Dashboard to my child?

Once the Child and MainWP Dashboard are connected, someone would need access to your child sites WP-Admin to disable and re-enable the plugin, thus breaking the connection between the two.

Why do most of the alternative systems use a unique ID if it’s not necessary?

We have strived from the beginning of development to make everything as user-friendly as possible. We found requiring you to enter a unique ID a wasted step for users when we can programmatically establish the secure locked connection without additional user input.

We believe if someone can get into your Child sites wp-admin area to disable and re-enable the MainWP Child Plugin to break your Main Dashboards lock on it, then you probably have bigger security problems than a unique ID is going to solve.

However, we always try to listen to our users, and we know some of you do not feel secure without having a unique security ID for each of the child sites, so we added one for you in Main Version 0.1.0 and Child Versions 0.1 and above.

The Unique Security ID will need to match when being added to the Main Dashboard. This is additional security and should not be needed in most situations.