In a WPMU environment how does FLuentCRM support multiple subdomains.
I’ve been reviewing the recent tutorial “Sync Fluent Forms with FluentCRM on a Different Domain Using Webhooks,” and while digging deeper into multisite support, I’ve come across something that needs clear confirmation from the FluentCRM team or anyone who has implemented this at scale.
Some other sources state that FluentCRM offers a dedicated FluentCRM Multisite plugin that must be installed and activated at the network admin level. Once active, it introduces a Multisite settings section inside FluentCRM, including an “Enable Multisite Integration” checkbox, and allows individual subsites to connect their own FluentCRM instances to the network‑level CRM.
This discovery raises an important architectural question.
My current design assumes that ONE centralized FluentCRM instance—paired with WP Fusion—can manage all subdomains through role‑based and tag‑based segmentation, ensuring that each subdomain remains isolated while still benefiting from a unified CRM. In other words, the entire multisite network would rely on a single FluentCRM database, with tags/roles acting as the insulation layer between subdomains.
Before proceeding, I urgently need confirmation on whether FluentCRM Multisite actually supports this model.
Specifically:
- Does FluentCRM Multisite allow one CRM instance to serve the entire network, with subsites simply feeding data into it? OR
- Does the architecture require separate FluentCRM instances per subsite, with the multisite plugin acting only as a synchronization or coordination layer?
This distinction is critical. My deployment strategy—and the way roles, tags, and WP Fusion are structured—depends entirely on whether FluentCRM can operate as a single, centralized CRM in a multisite environment.
Any authoritative clarification or real‑world experience would be greatly appreciated.
So when you are using Multi-site the webhooks should work. It treat as single sites.
Shahjahan Jewel i've been working for months with CRM, SMTP, FORMS, COMMUNITY, BOARDS and recently PLAYER with the expectation that a SINGLE CENTRAL CRM would serve the subdomains. Now it appears that the single CRM domain tip was not correct and I now need to introduce a network of webhooks. I am really ready to drop the suite and start over with a system that natively will mesh the subdomain activity. So likely this is sayonara. I realize now that This means that our planned architecture — one FluentCRM + WP Fusion controlling all subdomain segmentation via tags/roles — is not supported by FluentCRM’s multisite design. further disappointment is discovering each subsite will require:
- Its own contacts table
- Its own tags
- Its own lists
- Its own automations
- Its own email logs
- Its own WP Fusion tag mappings
And that there is no shared tag/role system across subsites.
Stephen Ward We don't have any different multi-site specific feature. Our Plugins are multi-site compitable, that means each site will work same as the single site installation. We don't want to mix up data with child site so each site will get it's own db isolation with site prefix. That's how most of the plugins work like Woo and all others.