Locking pages from editing - problems with hierarchy

[safety3rd]

Ok, I'm missing something here! I'm trying to restrict publishers from editing
a specific folder (x) in a site hierarchy. However, if I add all of the folders
except X to the "allow editing" section...the user cannot edit X or the main
index page located "above it" in the architecture. If I allow editing on the
main index page, Contribute forces me to allow editing on all sub-folders,
including X.

How do I stop editing only on folder x?

I've tried marking the files in folder x (and folder x) as read only, but that
didn't work either.

Thansk for your advice.

Jeff

[ThinkInk]

I don't think that you are missing anything, you just encountered a problem
because of the way Contribute is set up.
To restrict the access to certain folders, you will have to consider the way
Contribute handles these matters before you build your site.
So when you want your users to be able to edit only a restricted number of
pages, you will have to place thes pages in a folder and create roles that
allow these users to edit pages in these folders, but not in all the other
folders.
They will of course not be able to edit files in the root folder, because of
the restrictions in Contribute you already encountered.
So basically Contribute works 'the other way around' concerning your thinking
pattern.

grtz.
Hayo

[safety3rd]

Thank ThinkInk. Unfortunately, the site wasn't designed with Contribute in mind.

Cheers

[abna]

If you have active directory, you can limit the access to that folder within
the folder permissions, by group. Then, even if Contribute "allows" access to
the folder, they still won't be able to make any changes there.