HarmonyUser Sync – Sync Users & Customers Across Multiple Sites

Skildring

Do you manage multiple WordPress websites and struggle to keep user information consistent across them? Manually updating profiles, handling registrations, and managing deletions on each site is tedious and error-prone. HarmonyUser Sync solves this problem by providing robust, automated synchronization of user data (including standard users and WooCommerce customers) between your WordPress installations.

Leveraging the secure WordPress REST API and Application Passwords for authentication (we never store your admin passwords!), HarmonyUser Sync ensures that user creation, updates (profile info, roles, passwords), and deletions are seamlessly mirrored across designated target sites. It features intelligent loop prevention to avoid data storms, detailed logging for traceability, and flexible options for both automatic and manual synchronization. Ideal for brand networks, multi-store WooCommerce setups, or any scenario requiring unified user management across separate WordPress sites.

Key Features:

• Automatic Sync: Real-time synchronization for user registration, profile updates, and deletions.
• WooCommerce Support: Seamlessly syncs WooCommerce customer data.
• Manual Sync Tool: Select specific users and target sites for bulk synchronization.
• Secure Authentication: Uses Application Passwords – no admin passwords stored.
• Intelligent Loop Prevention: Prevents infinite synchronization loops.
• Global User Identification: Reliably identifies the same user across different sites.
• Target Site Management: Easy interface to add, manage, and test connections to target sites.
• Detailed Sync Logs: Track every sync operation for auditing and troubleshooting.
• Role-Based Sync: Option to sync only users with specific roles.
• Bi-directional & Chain Sync Ready: Supports complex synchronization topologies through configuration.

Advanced Features (New in 2.0.0):

• Flexible Authentication: Manual Application Password entry for enhanced security control
• Intelligent User Creation: Automatically create users on target sites during sync if they don’t exist
• Site-Wide Protection: Prohibit incoming sync modifications to protect master sites
• IP & URL Whitelist Management: Advanced security with whitelist validation for incoming requests
• Per-User Sync Control: Granular control to prohibit sync propagation for specific users
• Per-User Protection: Reject incoming modifications for protected VIP user accounts

With HarmonyUser Sync 2.0, you get a complete, enterprise-grade user management solution for your entire WordPress ecosystem.

Configuration / Usage

1. After activating the plugin, a new menu item «User Sync» will appear in your WordPress admin sidebar.
2. General Settings (User Sync > Settings):
   • Enable Auto Sync: Check this to automatically sync user changes (create, update, delete).
   • Sync User Roles: Select which user roles should trigger synchronization. Users with unselected roles will not be synced.
   • Log Retention Days: Set how long sync logs should be kept (e.g., 30 days). Older logs will be automatically purged.
   • Enable Sync Log: Check this to record detailed logs of sync operations. Recommended for troubleshooting.
   • Prohibit Incoming Sync Modifications: (New in 2.0) Prevent this site from accepting any incoming sync requests.
   • Create User on Edit If Not Exists: (New in 2.0) Automatically create users during sync if they don’t exist on target sites.
   • Enable Whitelist Authentication: (New in 2.0) Only accept sync requests from whitelisted URLs and IP addresses.
   • Save your changes.
3. Target Sites (User Sync > Target Sites): This is where you define the sites to which the current site will send user data.
   • Click «Add New».
   • Site Name: A recognizable name for the target site (e.g., «My Store Blog»).
   • Site URL: The full URL of the target WordPress site (e.g., https://target-site.com). HarmonyUser Sync must also be installed and activated on this target site.
   • Authentication Method: (New in 2.0) Choose between automatic generation or manual entry of Application Passwords.
   • Admin Username: The WordPress administrator username on the target site (for automatic method).
   • Admin Password: The password for the administrator username on the target site. This is used only once to generate an Application Password and IS NOT STORED.
   • Application Password: (New in 2.0) For manual method, enter an existing Application Password directly.
   • Status: Set to «Active» to enable syncing to this site.
   • Test Connection: Click this button before saving. It will attempt to connect to the target site using the provided credentials and generate a secure Application Password specifically for this sync connection. You should see a success message if it works. The Application Password will be stored securely (not the original admin password).
   • Click «Save Target Site».
4. Whitelist Management (User Sync > Whitelist): (New in 2.0) Manage trusted sites for enhanced security.
   • Click «Add New» to add a trusted site.
   • Enter the site name, URL, and IP address.
   • Set status to «Active» to enable whitelist entry.
5. Manual Sync (User Sync > Manual Sync):
   • Select the user(s) you want to sync from the list.
   • Select the target site(s) you want to sync these users to.
   • Click «Apply» to start the manual synchronization process. This is useful for initial bulk syncs or syncing specific users on demand.
6. Sync Logs (User Sync > Sync Logs): View the history of all sync operations, filter by date, site, status, etc.
7. User-Level Controls (New in 2.0): In the WordPress Users list, you can now control sync behavior for individual users:
   • Sync Propagation: Toggle to prevent a user’s changes from being synced to other sites.
   • Sync Protection: Toggle to protect a user from being modified by incoming sync requests.

Important: For bi-directional sync (e.g., Site A syncs to Site B, and Site B syncs to Site A), you need to configure HarmonyUser Sync on both sites, adding the other site as a target in each respective configuration.