User accessable pages or container

Is there any way to simply create a "user page" or user specific container.
Basically to allow a specific user or user group to access / edit only a specific page or container of multiple pages.
Preferably through the backend but not allow them access to anything else.
I’ve tried creating admin users and and web users and user groups and resource groups and none of it seems to do anything!
For example : I created a admin user called FRED. I created a new role called FREDROLE and allocated it to Fred. I created a user group called FREDGROUP and a resource group called FREDRESOURCE and created a grouplink FREDGROUP to FREDRESOURCE.
I then created a page and set its access to FREDGROUP.
I was expecting everybody including visitors to be able to see the page but FRED (and admin) being the only one to be able to edit it. WRONG! Nobody sees it and anybody with back end access can edit it! (And Fred can edit evything else!)
Any ideas as this has all but caused abandoning Modx out of user frustration! :’(

There seems to be very little concise information on User management and permissions. It would make a great tutorial

If you are working with manager users, use the Manager Permissions and Roles. Web Permissions are for setting up groups for securing the final web pages on the front-end; you don’t need to deal with them at all when working with manager permissions.

Document groups are global, so make sure to create different document groups to associate with your manager groups if you have any web groups in use.

Thanks for your reply.
I was getting confused with the web access side and admin etc. I tried what you said and almost got it working.
I’ve had to set up a ADMIN based group and resources etc and link every other page to it to stop them being accessed by the members.
Basically it appears that by default every user with backend access (and editing rights) can edit anything, so I’m now trying to set up various groups and trying that with users.
Ideally I want specified users to simply login and they can access their own container, and ideally no access to anything else. THis way I can setup the initial page (container) and hopefully link the specific end user to it, to allow them to post their own info.
I was getting confused and frustrated with the Web user side.
I’ll keep on trying but at least I seem to heading in the right direction (I hope)

Hi ProgramIT,

Maybe this will help:

Setting manager permissions has no effect on what can be seen in the front end.

Setting web permissions has nothing to do with what can be edited in the back end.

In either place, if you connect a document group to a user group, the documents in the group are protected and can only be seen by those with permission. If a document is not in a document group that is connected to a user group, it is not protected and can be seen by everyone.

Quote from: BobRay at Feb 02, 2010, 08:07 PM

If a document is not in a document group that is connected to a user group, it is not protected and can be seen by everyone.

And why is that? It seems to me that everything in the manager should be protected and viewable by the admin by default. Has there ever been any work to make that happen? Any branches in svn?

Quote from: devtrench at Mar 22, 2010, 03:33 PM

Quote from: BobRay at Feb 02, 2010, 08:07 PM

If a document is not in a document group that is connected to a user group, it is not protected and can be seen by everyone.

And why is that? It seems to me that everything in the manager should be protected and viewable by the admin by default. Has there ever been any work to make that happen? Any branches in svn?

I’m not an architect of the MODx permission system, so I can’t give a definitive answer here.

What you’re suggesting is kind of true in Revolution, in the sense that, by default, only the super-admin has access to the web context in the Manager, so new users can’t see any resources in the Manager until you give them permission to do so through a Context Access ACL entry. The general philosophy for the front end in both Evo and Revo is to make things unprotected by default. If you want to hide something, it’s easy enough to do it.