Hello, > Hello, > > in the permissions tab it is possible to set permissions for > particular parts of document tree (folders or documents). > However, I noticed that it works only for the preview site. > After restricting access to a folder, I cannot see it when I > log into the repository using a browser. But the > corresponding folder in the live site is still visible. What > I would expect is that setting permissions in CMS would > affect both preview and live sites, or at least a mechanism > that does that (i.e. publishing a document publishes it's > permissions).
No, this is not possible. ACL's in slide/hippo repository do not work this way. That we have a seperation between live and preview documents is merely copying documents from preview to live. It is not possible to automatically copy the ACLs. I though however, that since some time, you were able to set also ACLs on the live folders, and not only on the preview...Anybody else knows this?? Furthermore, I do not know what your goals in the end are, but discriminating on using different urls (repository paths) between groups of users is often more efficient than based on ACLs. Only ACL based will give you the risk of slow searches: every search hit must be checked for valid ACL. If you are a user with very few access rights, *many* results might have to be checked before having, say 10, valid results. This may impose quite some performance slowdown when you will get *many* documents. Anyway, I think it should be possible with the cms to set ACLs on the live (perhaps somebody can affirm this?), though do be aware of the risks of slower queries for users which have few access -Ard > > Why do I need this? In our project we want to log into our > portal with the same credentials as into CMS (that is using > hippo repository users). And we thought that it would be > convenient and flexible if restricting access for a > group/user to certain documents in CMS would also affect > documents visibility in portal. But without propagating the > permissions to the live site I see no way to accomplish this. > > Or maybe we are missing something here? Maybe there's a > better approach to restricting access to certain parts of the > portal? Any thoughts? > > Regards, > Chris > > ExOrigo > http://www.exorigo.pl > ******************************************** > Hippocms-dev: Hippo CMS development public mailinglist > ******************************************** Hippocms-dev: Hippo CMS development public mailinglist
