Open Source Document Management System | OpenKM

Is it possible to configure several independent repositories? So that users from different groups were unaware of its existence and had no access to Documents from other groups? It's important hide folders from one group to second group.

That can be done with one repository it's the same idea. In root taxonomy you must define some structure and decide there which users and roles have access. Remember that UserRole must be removed ( it's a connection grant role that must not be propagated across the repository, but that all user must have )

I don't understand exactly what you mean. You are saying that I need to remove UserRole but all users must have it?

1- All users must have UserRole to connect OpenKM ( it's connection grant )
2- You must remove in taxonomy, templates and categories node any reference to UserRole in other places must not make changes
3- Then must add other roles to taxonomy, categories, templates ( the users must have UserRole and others, that's the idea ).

I try this and seems to work fine, thx But for my 100% success I will need one more thing.
Is there any way to make taxonomy folder looks like a personal folder for user? When I login as a regular user, in personal, trash or mail folder I see only folder with my name (I cant see okm:Personal or okm:trash folder). Can it be done in taxonomy?
You ask why? Well if I had an idiot user (sorry ) and that user send document to root directory, not to his special group folder, everyone can see it. Now the only thing I can do, is to remove write access on okm:root for UserRole. It works but didn't look good.

Not possible unless you perform some hacking. The "okm:personal" folder is the root of all user's personal folders:
This is the way it is organized and change this is not an easy task. The only easy way should be a change in the representation name of the shown folder node.

In okm:root only administrator have read access. Usually the first nodes on taxonomy are used as user entry points they must not write or create folder on root node. It's a good practice.

About UserRole that's role mandatory needed to all user for connection, but first administrator task is remove from okm:root and replace for other roles than users must have ( a user can have UserRole and ManagerRole for example, both at the same time, but only ManagerRole has presence under taxonomy ).