CiviCRM multisite allows separate sites to access the same CiviCRM database with segmented data access, with each site having its own website. Great for chapter, regional, or multi-brand organizations that need some shared infrastructure while still separating parts of their configuration or access.
Multisite is powerful, but admittedly it has rough edges and quirks that if not known, can make organizations shy away from digging in to it. I've made good use of CiviCRM multisite over the years under Wordpress, but sometimes it is forgotten in the dev cycle.
With all that said, there is now an active Make It Happen campaign to improve multisite support by making contributions, memberships and participants fully domain-aware.
This would make multisite administration and reporting much clearer, especially where different domains need to manage or review their own activity. For instance, let's take one situation where the parent domain may want to see all contribution records, be able to filter contributions on their own to file compliant reports while child domains only need to see their contributions (to also file compliant reports) and not see other related chapters contributions
And optimally, see parent contribution and membership records too.
Join the Multisite Roundtable - July 24
Date: July 24, 2026 at 11:00 AM US EDT / 15:00 GMT
Location: Online, available after registration
We are also organizing an open CiviCRM Multisite Roundtable for organizations, partners, developers, and implementers who use multisite, or are considering it.
This roundtable is meant to surface potential enhancements and ways to collaborate better.
We especially want to hear about:
- How your organization uses multisite
- What works well today
- What is confusing or difficult
- Permission concerns
- Reporting across domains
- What would be the biggest improvement you would like to make?
If you rely or support multisite, please pitch in to the Make It Happen campaign and look forward to seeing you on the roundtable.
