-
- 121 Posts
Hi,
here’s a Security wish:
I’d like to exclude Templates for lower usergroups. When a client is logged in as a Webmaster (user who’s part of the usergroup Webmasters), I’d like to give him only access to 2 templates in the template dropdown field, instead of also giving access to the third, the Homepage template for example.
However, a client should be able to edit a resource which uses the denied template. He should be able to edit a document which uses the Homepage template (and the TVs which go with it ofcourse), but not create a new document with that template.
Also, and this can be trickier: I want get rid of the "(empty)" template. It was doable with ManagerManager in the Evo days.
Thanks in advance, Shaun!
-
- 121 Posts
Posting the FR as we speak.
-
- 4,149 Posts
Actually, Martin, that can be done - you just add another Element Category ACL to the user group:
- Category: "My Category"
- User Group: mygroup
- Context: mgr
- Policy: Load Only
However, this gives them access to create documents with that Template. What’s your intention with these users? You just dont want them to specify templates at all? Or do you want them even creating Resources?
Edit: Just tested, actually, they cannot create docs with that Template. So adding the Load Only policy should work fine.
shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect |
github |
splittingred.com
-
- 121 Posts
Okay thanks! I haven’t checked the page yet, but it doesn’t give clients access to TVs belonging with the denied template right? I’ve justed posted a FR for that!
Again, this is a great move!
-
- 121 Posts
Nevermind, I’ve just read the page. Excellent work!