Hi,<div><br></div><div>I can understand how the current implementation of Pier security could work well in the case of a set of users each with their own sub-tree - a little like Unix&#39;s &#39;/home/user1&#39; &#39;/home/user2&#39; etc, where users can control the commands allowed to be executed on their sub-trees.</div>
<div>However I&#39;m looking for a more capability model, for example:</div><div>* does the user have permission to see this view in wiki mode? </div><div>* does the user have permission to create verbatim html?</div><div>
* does the user have permission to create value links?</div><div>* etc</div><div><br></div><div>Is there a sensible way to map this onto the current security implementation? I&#39;ve currently mapped it with code like:</div>
<blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
editorConfiguration allowWikiTextEditing: ((self context command: PRWikiTextEditingCommand new)  isValid).</blockquote><div><br></div><div>This works however the owner/group/other structure permissions mapping seems too coarse grained. I&#39;d like to be able to have groups relating to these permissions then add groups to users, depending upon the permissions I&#39;d like to assign to them. Am I looking at this in the wrong way? Is there a mechanism to support a capability model?</div>
<div><br></div><div>Cheers</div><div><br></div><div>Nick</div>