How can one disallow a none-Administrator manager to edit and delete specific resources under MODX Evolution 1.0.10?

How can one disallow a none-Administrator manager to edit and delete specific resources under MODX Evolution 1.0.10? Without affecting the child resources of these resources? I mean, the user logged in as a none-Administrator manager may see the whole branch of the unauthorized Parent + all its child resourses, but just can not edit or delete only the resource disallowed.

Create a new Document group. Assign all of your resources to that group. Connect the Document group to your Administrator user group. Now only Manager users who are members of the Admininstrator group can access those resources.

Create a Manager user group for Editors. Create a corresponding Resource group. Assign the resources you want your Editor to access to that Resource group. Assign your Editor users to the Manager User Group. Now they can see their resources.

In the Tools - Configuration - Interface and Features there is a setting for "Show Protected Pages". Set this to "yes".

Quote from: sottwell at Jun 17, 2013, 11:36 PM

Create a new Document group. Assign all of your resources to that group. Connect the Document group to your Administrator user group. Now only Manager users who are members of the Admininstrator group can access those resources.

Create a Manager user group for Editors. Create a corresponding Resource group. Assign the resources you want your Editor to access to that Resource group. Assign your Editor users to the Manager User Group. Now they can see their resources.

In the Tools - Configuration - Interface and Features there is a setting for "Show Protected Pages". Set this to "yes".

- It works, thanks a lot! The minimum is achieved. And it is even enough to follow just the first and the third part of the suggestion to do it.

But going more intent, is it possible somehow to have it more fine-tuned, like to prohibit a none-Administrator manager to delete a resource, but in the same time to allow the none-Administrator to add child resources to it? [ed. note: duiker-op-basis last edited this post 13 years, 4 months ago.]

Found a widget for ManagerManager: mm_widget_accessdenied ( http://code.divandesign.biz/modx/mm_widget_accessdenied ). It allows to close specific resources, but letting to add child resources to them. However, disallowing to edit a resource, it allows to delete it. Can anything be done to prohibit also this deletion? [ed. note: duiker-op-basis last edited this post 13 years, 4 months ago.]

Quote from: duiker-op-basis at Jun 18, 2013, 09:33 AM

But going more intent, is it possible somehow to have it more fine-tuned, like to prohibit a none-Administrator manager to delete a resourse, but in the same time to allow the none-Administrator to add child resourses to it?

That can be handled in the Role assigned to the user.

Quote from: sottwell at Jun 18, 2013, 11:59 AM

Quote from: duiker-op-basis at Jun 18, 2013, 09:33 AM

But going more intent, is it possible somehow to have it more fine-tuned, like to prohibit a none-Administrator manager to delete a resourse, but in the same time to allow the none-Administrator to add child resourses to it?

That can be handled in the Role assigned to the user.

- The "Content management" group in "Create/edit role" does not seem to have any "Create new Child Resources". And whatever is checked there, a resource assigned to the group of the Administrator manager is closed for none-Administrator managers. Or these settings are somewhere else? - where?

If "Delete Resources" is unchecked, then none-Administrator manager can not delete any resource. But I need to have a none-Administrator both prohibited from deleting only specified resources and be able to delete all the rest. [ed. note: duiker-op-basis last edited this post 13 years, 4 months ago.]

Hello.

Is there a solution at this problem?

How can none-Administrator user add child resourse to protected resource?

Thank you.
(sorry for my eng.)

There is a setting to show protected resources, so the editor can see them and their children.

yes, it is. (I find it before... thanks to your posts from another topic)

but editor can not create new document a child of protected document. i think it better to try))
i can record the video) to explain

I make screens. Logged by Editor role:

1. If I create a child of protected doc
http://joxi.ru/Mye5U_3JTJCRefDClmI
http://joxi.ru/bie5UxjKTJClNXh24NY

2. If i creat a child of usual document (not-protected, for all)
all OK
http://joxi.ru/JSi5UxjKTJAhH8qiaAs

Permisions inherited from the parent, i think. How to disable this..?

Thanks..