what is the pourpose of "fake" projects?

My production server is an (old) ogo 1.0a2. I have both fs and db 
project backend installed.

I created a number of enterprises in the webui, and noticed that a 
project was automatically created for each enterprise, which was not 
listed at first in the webui (I can see these projects listed in db 
"projects" table, with an empty path and an attribute is_fake=1). I am

When I set some permission for the created projects using the web ui 
(these projects can be reached using the "projects" tab in enterprise 
webui), these projects apparently spring into existence (projects are 
listed in the "project" section of the webui, documents can be added) 
but I noticed that everyone has full access to project settings and 
documents, regardless from applied permissions, so their usefulness is 
limited, for my purposes.

Is this the intended behaviour? Can "fake" projects be turned into 
"normal" ones (i.e.: projects with configurable permissions) or is there 
some default that can be set to avoid "fake" projects creation?

Many thanks in advance. Renzo Vettori

-- 
OpenGroupware.org Users
[email protected]
http://mail.opengroupware.org/mailman/listinfo/users