Introduction
Multi-tenant environments should be compatible, as each tenant operates on its own database and URL. However, because this is a custom-built system rather than a standard WordPress setup, we recommend testing with the default theme first—if that works, BuddyBoss should function correctly.
Multi-Tenant Architecture and BuddyBoss
Separate Databases and URLs
- Isolation: Each tenant site maintains its own WordPress database and URL. BuddyBoss must be installed and activated on each tenant as a standalone plugin/theme.
- Code Consistency: All tenants share the same BuddyBoss codebase—updates to the BuddyBoss Platform and Theme propagate uniformly across tenants.
Activation and Licensing
- Per-Tenant License: Even though you use one codebase, each tenant URL requires its own BuddyBoss license key. Enter each key under BuddyBoss → License Keys on the corresponding tenant site.
- Automated License Provisioning: If you use a managed hosting provider or WP-CLI scripts, you can automate license activation across multiple tenant environments.
Key Consideration
- We have not tested BuddyBoss for Multi-Tenant sites yet. We are still working on BuddyBoss products to make them fully compatible with Multisites and Multi-Tenant sites.
- We are not able to guarantee that it will work 100% properly in those environments.
Troubleshooting and FAQs
Q: Can I share user accounts across tenants?
A: No. Each tenant has its own user database. Shared single sign-on requires a custom SSO solution or a WordPress multisite network with a centralized user table.
Q: My tenant shows a license error after cloning—what’s the fix?
A: Cloning copies the license key to the new URL, which invalidates it. Log into BuddyBoss → License Keys on the cloned site and activate its own license.
