chris.schults at pccsea
May 6, 2008, 3:05 PM
Post #1 of 1
(29 views)
Permalink
|
> Sorry for the delay here Chris (and many thanks for kicking the
> tires!).
You're welcome Phillip. Sorry I haven't replied sooner, but I'm just
getting back to this.
> I was able to achieve what you're after by setting the "DEFAULT SITE
> SITE CATEGORY PERMISSIONS" on / to DENY, while leaving it set to READ
> on /blog/
>
> I'll update that in my notes. Let me know if it works for you.
So, after closer review, it looks like my HR user only has access to
other "non-approved" assets *only* when they are active. I assume it is
because they have the EDIT permission on the Story workflow and
EDIT/CREATE/PUBLISH on Story desks -- the most permissive rule wins.
As you suggested, I can change a category permission to DENY, but it
appears I'd have to do this for every category (at least those used by
story assets), and I still have a lot more to add.
Is there a better way, or do I have to make it part of the process to
adjust perms whenever a new category is added?
Chris
--------------------------------
Chris Schults
Web Developer
PCC Natural Markets
206-547-1222 x104
chris.schults[at]pccsea.com
http://www.pccnaturalmarkets.com
Sign up for PCC Fresh, a monthly newsletter filled with seasonal
recipes, exciting new products, and more:
http://www.pccnaturalmarkets.com/enews
|
