How to set permissions for new user?
Permalink
Hi all, I've done my homework - spent a solid 1-hour+ reading the documentation and forum messages. I love c5.7, but I gotta say permissions are rather frustrating...!
I've created a new user called Editor. I simply want to create a basic set of permissions - access to File Manager, etc. - that a content editor would need, and restrict access elsewhere.
When/if time, someone offer a step-by-step procedure for this? Can't believe this should be as difficult as it appears to be...
Thanks in advance!
Charlie
I've created a new user called Editor. I simply want to create a basic set of permissions - access to File Manager, etc. - that a content editor would need, and restrict access elsewhere.
When/if time, someone offer a step-by-step procedure for this? Can't believe this should be as difficult as it appears to be...
Thanks in advance!
Charlie
Anyone...?
With advanced permissions on you have a LOT of flexibility, and yeah that can sometimes leave things overwhelming at first... In broad strokes, we'd typically do something like:
1) Make an "editor" group that you'll use for this role, that way you can put the next intern in the group or the old one out of it easily later.
2) Make the editor have Edit rights to the home page (in simple permissions mode) or Edit Contents and Approve Changes (at least) if you're in advanced permissions. Typically sites are setup to inherit permissions down the tree, but if you're using Page Defaults for that you would set them there.
3) Change the few dashboard/task permissions you need so they can get to the parts of the dashboard required. Do a search in your toolbar for "Task Permissions" and from there you will find a bunch of one off things and also Access Sitemap which the editor group will need to be in to use any page picker UI in block edit mode.
4) Similarly there's a File Manager Permissions page in the Dashboard. You can put the Editor group in all of those roles so they can get at files in the file manager.
5) Theres also a Universal block/stack permission page in the dashboard. You want to add the editor group to that as well.
6) Goto the sitemap, turn on the Hidden System pages, change the permissions on pages in the dashboard to let the right people get at the right pages in the dashboard. (The file manager/sitemap permissions you changed were for in-line use of that stuff from blocks)
That's one way to do it...
Alternatively - you could consider putting the new guy in the Administrator group, and then adding a new group to /exclude/ them from parts of the dashboard you don't want them in...
1) Make an "editor" group that you'll use for this role, that way you can put the next intern in the group or the old one out of it easily later.
2) Make the editor have Edit rights to the home page (in simple permissions mode) or Edit Contents and Approve Changes (at least) if you're in advanced permissions. Typically sites are setup to inherit permissions down the tree, but if you're using Page Defaults for that you would set them there.
3) Change the few dashboard/task permissions you need so they can get to the parts of the dashboard required. Do a search in your toolbar for "Task Permissions" and from there you will find a bunch of one off things and also Access Sitemap which the editor group will need to be in to use any page picker UI in block edit mode.
4) Similarly there's a File Manager Permissions page in the Dashboard. You can put the Editor group in all of those roles so they can get at files in the file manager.
5) Theres also a Universal block/stack permission page in the dashboard. You want to add the editor group to that as well.
6) Goto the sitemap, turn on the Hidden System pages, change the permissions on pages in the dashboard to let the right people get at the right pages in the dashboard. (The file manager/sitemap permissions you changed were for in-line use of that stuff from blocks)
That's one way to do it...
Alternatively - you could consider putting the new guy in the Administrator group, and then adding a new group to /exclude/ them from parts of the dashboard you don't want them in...
Many thanks, Franz - really appreciate this (guessing others will too ;-).
- C
- C
