It would not quite work the way you want it to.
The DenyEdit: all would override the AllowEdit:Wilson.
What I believe you should do is
AllowRead: all
AllowEdit: Wilson
It is also good in a testing system to ensure that your admin has a
ManageNamespace permission, as that will allow corrections to be made when
setting permissions in topics.
Another option would be to use topic locking and allow Wilson to Lock/Unlock
topics.
John Davidson
On Feb 2, 2008 3:12 AM, Wilson Chuah <[EMAIL PROTECTED]> wrote:
> Hi All,
>
>
>
> I've been reading
> http://www.flexwiki.com/default.aspx/FlexWiki/FlexWikiAuthorization.htmland
> before I start configuring, can I ask if DenyEdit takes precedence over
> AllowEdit? Example:
>
>
>
> AllowEdit: Wilson
>
> DenyEdit: all
>
>
>
> Would the above authorization allow Wilson to configure the topics while
> denying everyone?
>
>
>
> Regards,
>
> Wilson Chuah
>
>
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Flexwiki-users mailing list
> Flexwiki-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flexwiki-users
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Flexwiki-users mailing list
Flexwiki-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flexwiki-users
