Editor permissions for specific documents?

Hi,

I’ve read the notes on manager permissions several times and I still don’t get it.

What I want to do is have an editor login to the back end and only be able to see and edit certain documents.

Is this possible?

Any pointers, tips?

The documents will still be public at the front end.

I’m using evo

1. Create manager user groups, resource groups, and connect them. (Security -> Manager Permissions)

2. Create a role, checking all the actions you want the manager user to be able to perform (Security -> Roles)

3. Assign users to the appropriate role (admin users, editor users, etc) and manger user groups.

4. Assign resources to the appropriate resource groups.

Now only manager users belonging to group xyz can access the resources belonging to the resource group that manager user group xyz was connected to in step 1. They cannot see any resources assigned to a resource group they are not associated with. Resources not assigned to any group will be available to all users.

It is possible, using the Configuration (Interface and Features tab) Show Protected Pages setting to allow all users to see the entire resource tree, but still only access the resources they have permission to. This way they can work with children of a parent/container resource they can’t work with. If that setting is No (the default), then they cannot see any resource they don’t have permission to access nor can they see its children, even if they do have permission to work with the children, that entire branch of the Tree is not loaded.

ooops,

I’ve been guilty of cross posting.

Wasn’t really intentional, the two topics just seemed to collide.

Anyway, got what I need from this post http://modxcms.com/forums/index.php?topic=55647.new;topicseen#new

as i said in the other post I got into all sorts of bother doing it this way with the dreaded Too many forward attempts.

Will reread your notes below in the morning and maybe have another play.

That "too many forwarding attempts" usually involves user permissions, and accidentally securing the Unauthorized page (can’t access that page, so get forwarded to the "unauthoraized" page, can’t access that page so get forwarded to the "unauthorized" page... until the server gets fed up and throws an error).