Multi-Tenant Community Management
Community-isolated data with role-based access control per tenant.
- Each Waddles installation hosts multiple independent communities, each with its own members, roles, settings, and connected platforms, keyed by community_id across every feature module.
- Role-based access control follows a resource:action permission format (e.g. community:moderate, module:install), with a default role hierarchy of admin, community_owner, moderator, and user.
- Every request carries a community_id (or equivalent tenant context) so queries are scoped and cross-community access is prevented by default.
- Community platform connections store credentials per platform, isolated from other communities on the same installation.
