Restricting access to certain elements

If’n I wanna hide certain templates, chunks, etc. from certain groups and-or user roles, how would I go about doing that? With resources the key is resource groups... but there isn’t an equivalent concept with elements. By category? Or properties?

Note: the presence of three question marks above does not constitute a three-part question, but rather demonstrates my complete inability to express myself concisely.

Quote from: jrotering at May 13, 2010, 10:54 AM

If’n I wanna hide certain templates, chunks, etc. from certain groups and-or user roles, how would I go about doing that? With resources the key is resource groups... but there isn’t an equivalent concept with elements. By category? Or properties?

Note: the presence of three question marks above does not constitute a three-part question, but rather demonstrates my complete inability to express myself concisely.

ACLs on Elements are not supported at this time, but are in the Roadmap. You could file that as a JIRA feature request: http://bugs.modxcms.com/

Or, you can hide the entire tree by removing the ’element_tree’ permission, or if you want to just not allow them to edit them, you can remove the respective ’edit_chunk’, ’delete_chunk’, ’view_chunk’, etc (for each element type) permissions.

I’ll do that. For my purposes, it seems like the most logical/useful behavior would be to be able to assign resources, elements and files all to a particular group (’resource group’ would no longer be an accurate name, I guess). Then users in department X could edit "dept X" resources (for their pages), "dept X" elements (for chunks of content), and "dept X" files (for images, pdfs, etc).

For the "files" stuff, though, maybe I’m just suffering from a lack of understanding of static resources and content types? Should I instead be looking at a way for my users to manage their images and binary files through the resource tree?

The more I think I know, the more I realize I don’t know.

Splittingred, I haven’t tried it, but might there be a way to disable the editing of some elements using a Form Customization rule and constraints?

Quote from: jrotering at May 13, 2010, 12:34 PM

I’ll do that. For my purposes, it seems like the most logical/useful behavior would be to be able to assign resources, elements and files all to a particular group (’resource group’ would no longer be an accurate name, I guess). Then users in department X could edit "dept X" resources (for their pages), "dept X" elements (for chunks of content), and "dept X" files (for images, pdfs, etc).

Right; eventually you will be able to - we’ll add the same sort of permissions (or something like it) to Elements as well. I think that’s slated for 2.1.

For the "files" stuff, though, maybe I’m just suffering from a lack of understanding of static resources and content types? Should I instead be looking at a way for my users to manage their images and binary files through the resource tree?

Oh, no, I mean - you can - but it’s best just to assign them a directory, and use the filemanager_path (buggy in RC-1, working in RC-2/SVN) to restrict them to a directory.

The more I think I know, the more I realize I don’t know.

Welcome to the club.

Quote from: BobRay at May 13, 2010, 01:06 PM

Splittingred, I haven’t tried it, but might there be a way to disable the editing of some elements using a Form Customization rule and constraints?

Call me Shaun, Bob. Nope, FC only allows for customization within the forms, not the editing process itself.

Quote from: splittingred at May 13, 2010, 01:20 PM

Quote from: BobRay at May 13, 2010, 01:06 PM

Splittingred, I haven’t tried it, but might there be a way to disable the editing of some elements using a Form Customization rule and constraints?

Call me Shaun, Bob. Nope, FC only allows for customization within the forms, not the editing process itself.

Ok Shaun, I was thinking it might be possible to hide the content field of the Create/Edit Element form, which would effectively disable editing the element -- maybe not.