Hi, First make sure you have an add-on to Pier that allows you to manage users. I use Pier Unix Security (you can load it from Squeak Map and it will load Pier as well). When it comes to rights, pages and components are similar. Here is one solution I used for a similar problem: - Load Pier Unix Security from Squeak Map. - Add System page as child of the root. I named it =System to make it appear first in the list of pages. - Add System Users component as child of the =System page. - Add System Groups component as child of the =System page. - Add a user that is in the admin group (or just use the default admin user). - Go to the root page, select Change Owner command, check the Recursively check box to affect all pages, and change the owner to be the admin user. - Go to the pages you do not want the others to see, and using the Change Other command remove the View ability. You can also play with groups, by making the page belong to a certain group and then place the wanted users in that group. Cheers, Doru On Oct 14, 2007, at 1:15 AM, tournesolo(a)gmail.com wrote: -- www.iam.unibe.ch/~girba www.iam.unibe.ch/~girba/blog/ "Sometimes the best solution is not the best solution."

Hi, The reason for that is that you wrap the Views command with a div, and that div is not affected by the rights of the inner component/ page. For example, by default in Pier you get in the Environment page: <div class="box"><h1>Views</h1>+views+</div> If you want to control the visibility of the surrounding div as well, you can just create a page with only the above content, include the page in the Environment without any surrounding div and then give the page the wanted rights. Cheers, Doru On Oct 14, 2007, at 12:55 PM, tournesolo(a)gmail.com wrote: -- www.iam.unibe.ch/~girba www.iam.unibe.ch/~girba/blog/ "Problem solving efficiency grows with the abstractness level of problem understanding."