I have a good understanding how the permissions work in the Users section, which are fine for the Content & Media sections.
Is there a way of restricting a (back-end) user to only the Members section (just tick the box in the 'sections' panel) and only have permission to create & edit, but not delete any of the members?
Reason for this is that we've got a couple of freelancers manually importing data (it's a long story) - so don't want anything to go wrong, (yep, we've taken DB back-ups, etc beforehand) ;-P
Thanks skiltz, it's a good approach, I may well just do it! I've created a new User Type for the new users, (so they are completely locked down), I could always check which User Type the user is in the "Member_Delete" method.
Alternatively, I recall someone mentioning manipulating the appTree recently... maybe I could hide the 'delete' context menu item from them?
If you wanted to change the tree you'd probably have to create a class that inherits from loadMembers and then override the AllowedActions method (I think, you'll need to double check that)
Restrict User to Not Delete Members
Hi all!
I have a good understanding how the permissions work in the Users section, which are fine for the Content & Media sections.
Is there a way of restricting a (back-end) user to only the Members section (just tick the box in the 'sections' panel) and only have permission to create & edit, but not delete any of the members?
Reason for this is that we've got a couple of freelancers manually importing data (it's a long story) - so don't want anything to go wrong, (yep, we've taken DB back-ups, etc beforehand) ;-P
Many thanks, Lee
You could create a Member Event handler which acts on the Member.BeforeDelete method and then returns cancel.
Untested, not sure if this work.
Ohh and also and if this works it would stop anyone front deleting. You'd need to add some more logic to test if they had permission.
Thanks skiltz, it's a good approach, I may well just do it! I've created a new User Type for the new users, (so they are completely locked down), I could always check which User Type the user is in the "Member_Delete" method.
Alternatively, I recall someone mentioning manipulating the appTree recently... maybe I could hide the 'delete' context menu item from them?
If you wanted to change the tree you'd probably have to create a class that inherits from loadMembers and then override the AllowedActions method (I think, you'll need to double check that)
is working on a reply...