You wouldn't need to edit everyone's psml, no. Assuming you want to have user-based psml, set each new user psml document to use as a base a psml doc that only you can edit. (services.Profiler.newuser.template property). On that psml you could define an admin-only editable reference to a public Group psml file. In that psml you could then add and remove whatever portlets you wanted, and they would be available to every user.
In your psml browser you might have a setup like: User -> baseUser -> ... -> default.psml (so then you'd specify: services.Profiler.newuser.template=baseUser) Group -> public -> ... -> PublicPortlets.html Where baseUser's default.psml has a non-editable reference to PublicPortlets.psml. I've not actually done this, but it should work. There may be an easier way also. hth, stu >>> [EMAIL PROTECTED] 09/22/03 10:43AM >>> Greetings to the list... I'm planning the rollout of my portal and have a question... I am planning a phased roll-out of my portal. I have big plans, but only so much time so while some of my apps are finished, I will continue to enhance the site over time. Part of what I will want to change will be customizable elements and I want to have a high degree of control over the site layout and content. So, when I add a new portlet, I want to add it to ALL users, and not just to the environment and expect users to add it themselves. So the question is, if a site has several hundred users and one wants to add a new portlet to all user's experience, do I really need to edit all user's individual PSML files? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
