p.s.
tecxx wrote:- a lookup menu/system, to see in what category "facebook.com" would fall in, is nowhere to be found. does something like this exist? how do we test what category a site belongs to?
OK that's a good idea. In the meantime, you can log category and classifier to the usage logs. That will tell you the classification results independently of blocking or allowing. You can also see this in timeline if you hover on a block of activity.
To log extra fields, double-click on the logger for WWW proxy server usage logging, select format, and scroll down, you should see the additional fields you can log.
tecxx wrote:- contrary to what we found on this forum, the menu controlpanel-permissions-puresight is not expandable like a treeview, it's a single object that can not be utilized expect setting permissions. is this by design?
We changed the way this works when we added the classification subsystem and web access control system. Prior to this (early betas) PureSight itself did the blocking. Now it only classifies, and the web access control system does the blocking based on the classification. This allowed us to separate a lot of functionality out of PureSight (like manual rules) and put them in WinGate itself (for people who aren't using PureSight) and also gives us a system we can expand with additional / alternative classifiers.
So now to do per user control of categories, you use Web Access Control rules.