Set authorizations on iView..Please help

Hello all,
1> <b>I want to know how can I set authorization on access of a particular iView in EP (EP6 SP12)?</b>
Had read & tried about the AuthRequirement property but as per the below post, its deprecated on EP6 Portal components. And also it did not work in my ccase (portalapp.xml)
Re: Warning: AuthRequirement property is deprecated for EP6.0 components
Have also read about setting this in Security Zone and in it I have to update permissions in Portal Content since my iView/folder inherits the permissions from Portal Content folder.
2> When I opened Portal Content permissions, it contained groups like Everyone + few custom groups.
<b>In case case wherein there are 100-200 Potal users, how am I suppose to set permissions for a single user</b>?
<b>How would I remove that user from Eveyrone group</b>...?
3> Scenario:
I created a custom iView setting a property as:
<property name="AuthScheme" value="basicauthentication" /> in the portalapp.xml
After creating an iView, i also changed the authscheme property of this iView to basicauthentication and had also set its permission to 3 users only.
But all in vain!!
This particular iView is accessible to even other users who have not been permitted to do so.
If my question is not clear...please do wrrite back and i'll try explaining into other words.
Awaiting Reply.
Thanks and Warm Regards
Ritu R Hunjan
Message was edited by: Ritu  Hunjan


(as Detlev seems to be currently involved in other issues, I will hop in for him)
Detlev is right, the authorization concept works as designed:
Whenever you assgin portal content (i.e. pages, iviews ...) to a user by placing this content in a role and giving the user the role, the portal assumes that you want wo grant him access to all content included disregarding any authorizations given on iview level.
So, why can you set permissions on iview level at all?
First, you can also define administrative permissions here (modify/delete iview...). These are not automatically granted by role assignments.
Second, these permissions come in play if a user wants to perform page personalization and place additional iviews on a given page. For this "End user read" permissions will be required.
Lastly, you can also launch iviews directly via a URL without having it placed in a role (e.g. the "preview" mode in PCD does exactly this). In this case, too, "end user read" permissions will be evaluated.
PS: Please consider giving points if this answer was helpful for you. Otherwise leave an additional post prodiving more information to help you. Thanks.