Create user and limit access

There is an option in the site config "Show Protected Pages" or similar, which lets you choose to show/hide the protected (the page user can’t edit).

But to restrict the editing of the documents, u logically needs to put the other documents into some group which denies the access to that particular user you are talking about.

Hope this makes sense.

This might help you as well: http://bobsguides.com/permissions.html

To: zi Fm: geronimo

OK, I think I see what you are saying.

1. Let’s say I have 10 documents.
2. All 10 can be modified by the "administrator".
3. Documents 8,9, and 10 are the documents that I want the "manager user" to be able to edit.
4. I set it up so the "manager user" has access to documents 8, 9, 10.
5. Then "documents" 1-7 are put into a group that "CANNOT" be accessed by the "manager user".

This might hide these documents from the "manager user" (in the back end) but not from those web/internet - surfers/visitors to the website (in the front end).

Is that what you are saying?

Sort of like doing it from the opposite end. Making "everything" I don’t want her to access "off limits"....as opposed to.....limiting where she can go by restricting "her".

This would mean that everytime I create a new document, I would have to add it to the "restricted group - off limits group".

Is that correct?

Thanks
geronimo

This would mean that everytime I create a new document, I would have to add it to the "restricted group - off limits group".

Yes, bcz if you do not put it in any group, it is in "public" group. You cannot restrict access to it unless u add it to some group.

New child documents usually inherits the permissions IIRC.

This might hide these documents from the "manager user" (in the back end) but not from those web/internet - surfers/visitors to the website (in the front end).

Unless you restrict something with "Web Users Permissions" its public in the frontend.

Web Users and Manager Users are separate from each other.