Can i set own permissions in modx?

1)
can i prohibit a user from having access to documents BUT for one resource group? That would be a pity if permissions for resource groups are not overwriting those general ones. If it’s not that way i’m doing something wrong.

I have a created a role "Editor". This Editor is supposed to be the one accessing the "News" Resource group (allready created and assigned resource News(3) to it - he shouldn’t have access to another ressource in my test case "Home" and "Info" which are unprotected [i think this is the problem, but that would be a pity]). So i created a "BasicAdmin" policy granting minimal permissions for the admin interface ( - that works ). Then i went to the "resources access" tab of my Admin group (the "Editor"-role user is in there, as well as the great working context access restrictions) and added "News|Editor-500|Administrator|Web". Now the admin can access this group (thats clear and desired) while the "Editor" cannot.

Edit:
okay i think i got that. I missunderstood the resource group concept at first. I somehow thought it was for granting some people permissions but actually it’s for protected. I have to protect the other resources and leave the news alone. Then i just need to give anonumous users and members frontend access to the protected resources with the load policy.


2)
Can’t i reate my own permission from the manager interface?

I have some comonents installed i want restrict access for different users. So i go the the "actions" menu and add for example "manage_events" in permission. Now the according component menu is gone. So i want to assign that permission to some Policies, but i can’t. It seems not possible to create own permissions.


P.S:
Revo 2.0.4.

You’ll get more response if you change the subject to be more descriptive of your questions, something like "How do I set permissions in Revo?" would be more useful.

Changed it...

2.0.5 packs in a lot of improvement regarding permissions, so I would advise to update first.

Be sure to check http://rtfm.modx.com/display/revolution20/Upgrading+from+Versions+Earlier+than+2.0.5 for specifics.

You can definitely add your own permissions, but in recent versions of MODx you have to edit the Policy Template rather than the Policy.

You’re correct about having to protect the all resources you don’t want the user to see.

You might want to look here if you haven’t already:

http://bobsguides.com/revolution-permissions.html

thanks mark.

thanks bob. For sure i know your site and allready read a lot there including the thing on permissions thanks for the effort!


Just 2 further question:

• we’re planning to update soon. But i have no experience updating modx. Is there an update script or how do i achieve it? Especially the changes from 2.0.4 to 2.0.5. Do i have to upload all the new files and run setup / process?
• I created an RestrictedAdmin policy that should be assigned to the Administrator role in the Administrator group. But the user still seems to receive all Admistrator policy permissions.
  The user is added to the group with Administrator role and in the context access tab i added mgr|Administrator-1|RestrictedAdmin and web|Administrator-1|RestrictedAdmin. Any ideas why?

Re 1: Yea - just upload all the files (so not just the setup folder) and navigate to site.com/setup. You will run setup in upgrade mode (should be selected automatically).

Re 2: did you also assign a level 1 role to the user? (1 is highest, 9999 is lowest when it’s about roles)

ad 1) Is the newest version sufficient or do i need to upgrade to 2.0.5 before 2.0.6, and so on?

ad 2) Yes Administrator - 1. But i have a Super User - 0 with all the admin perms (think it was there by default). Could that be the deal? Is 0 not likely to be used? Should i rather have Administrator - 1 with all perms and something else with authority 2 and less perms?

The installer carries specific upgrade instructions on how to update from what version, so you should be able of doing it all in one go.


As 2.0.5 made quite some changes, you could decide to simply upgrade to 2.0.5 first and take the jump after that.

Do check the link I posted about upgrading before 2.0.5!