Karl Ottenstein wrote:
The information is visible to every user who is signed into the project, so there is no harm in having it available to them for internal use. If someone is stupid enough to print a page with the IP address, login id and password, that is their problem. ArchiCAD does not prevent anyone from publishing their bank accounts, so there is no reason to constrain information - it is the user's information for them to manage as they see fit.
Sure, some things like team members might only be visible to a lead architect role, but that kind of information is useful to put on internal documents and it belongs as part of the project IMHO. The BIM Server Manager has no report-writing capabilities. The schedule function in ArchiCAD does. It is a no-brainer I think. ;-)
A solution to satisfy both viewpoints might be to have that user configurable. There are cases where we might like the system to prevent us from pasting in our bank account instead of something less "sensitive." Likewise there may be some types of easily made mistakes that we would like the system to help prevent (but not with the intrusiveness and uniformity of Vista). In some apps, such as Goldmine, there are configs for beginners, intermediate level users, and masters. Maybe something like that could work.
Among gov't folks, suppressing some fields so that some users are not aware of the fields' existence, may be required. Striking a balance between flexibility and rapid configuration is the art required to make it sensible, easy, and fast for users who have an open environment, yet flexible for those needing a relatively secure environment where a config guru is SOP.