Another vote for this. Using something like a client called Knowledge Base (because there is no over-arching ability for a KB), and being restricted to one level of document folder creates some pain. The alternative is creating another client called something else, but then info is silo'd into that client which has other ramifications.
Kinda depends how complex the change is (or it's impact on anything else related to it) and whether allowing one more nested folder level would be sufficient for enough people to defer more complex changes.
