craig, also to this one... if i replace the anonymous to authenticated
below... it denies eveyone... but if you have AllowManageNamespace: [to any
role or user]... Deny first then allow... then they can now be able to edit
the _ContentBaseDefinition... but to have this upon namespace creation time
does not create the namespace still...
again, how would i implement these all during namepace creation time?... to
set default access rights...
On 9/18/07, Craig Andera <[EMAIL PROTECTED]> wrote:
>
> > is there a way that we can set who can just "edit" the
> > _ContentBaseDefinition topic without affecting the other topics under a
> > particular namespace?
>
> AllowManageNamespace and DenyManageNamespace define who can edit
> _ContentBaseDefinition (as well as who can lock and unlock topics whenever
> we add that feature to the UI). So you could do something like this:
>
> AllowEdit: all
> DenyManageNamespace: anonymous
>
> And anyone could edit any topic in the namespace except for
> _ContentBaseDefinition. To edit _ContentBaseDefinition, you'd need to be
> authenticated.
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> 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 2005.
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
