Hi, I need your opinion on a phenomenon i observed. i created some wsp files (which were actually web parts). i scoped them to be a site feature (not a site collection feature). the scope settings were set to 'site' in the project settings. when i deployed the wsp file. i selected only 1 web application on which i wanted it to be there. All worked fine but 1. the feature is availble to be activated at site collection feature rather than site feature. 2. despite of the fact that i just deployed the wsp by selecting only 1 web application, i can see the corresponding feature availalbe for activation on all other site collections within the same web application (which is ok no problem with that) AS WELL AS on ALL other web applications where the wsp is NOT deployed. activating a feature will not make it work on such other web apps, becuase their web.config file do not have the safecontrols entries yet. but i do not want the portal administrator on other web apps to see the feature there in the first place. ..... i though since i am putting the corresponding dll in GAC thats why all other web apps are also reading it and showing it but putting the dll to vti_bin also shows similar behavior. any suggestions?Adnan Shamim