Other knowledge bases and wikis tend to rely on a tree-like hierarchy and setting access permissions with a top-to-bottom approach. In Emvi permissions are set on per article basis, so they can have company-wide reach and still be edited by a small team only. We think this scales better with growing organizations, because silos are removed by default.

Let me know if you have any more questions.