Most teams end up running two tools: one for the company and one for the community. They drift apart, permissions diverge, and search stops telling the truth.
Kemble treats them as two surfaces over one core. Channels, threads, files, voice and search are shared. What differs is the shape of authority: Work resolves permissions through an org chart, Circle through roles and categories.
The hard part is not the UI. It is making one permission engine answer both questions correctly, every time, at the database level.