Dear all,
what rights are required in order to give a user the ability to select a
screen when scheduling a layout (on window “Scheduling now”)?
Greatings, Jörg
Dear all,
what rights are required in order to give a user the ability to select a
screen when scheduling a layout (on window “Scheduling now”)?
Greatings, Jörg
If you have made a new user account you will have to give this user account permissions on a display.
Go to Displays > displays and click the arrow down button. Then choose permissions and give this user the read rights.
Thank’s,
this setting I’ve made. But selection of the monitor isn’t still
possible (I cant’t upload a screenshot, as a new user I have no right’s ).
Greatings, Jörg
PS: I use version 1.7.4.
Hi Jörg,
Besides permissions to specific displays and layouts, you need some more permissions set.
Everything with ‘*’ is not essentially needed to what you asked, but you may consider it, other settings are essential.
Basically with minimum permissions, user will only see ‘Displays’ page and will be able to schedule/schedule now layouts from that page.
With ‘*’ permissions too, user will be able to schedule now specific layouts from layout page and schedule page (and see the scheduled events)
User/Usergroup permissions:
Page security:
displays
schedule
homepage
layouts ()
content ()
Menu security (it has drop down menu too)
dashboard
layouts ()
schedule ()
design
layouts (*)
display
displays
top nav
displays
design ()
schedule ()
As for the minimum permission, I would imagine you were missing the schedule in page security, anyway I gave you a bit more info, I hope you will find it useful
Thank’s I have setting the right’s so.
But it dosn’t work … User can see display on top nav -> displays, but can’t select this display on layouts -> jetzt einplanen.
Greatings, joesch
Dear all,
I have found the cause. It was the following right: “SCHEDULE_WITH_VIEW_PERMISSION”
(under admin - configuration - rights - Event planning with " View " rights).
Greatings, Jörg
Hi Jörg,
I am glad you found it, I didn’t have to change it, because it is pre configured in our test CMS.
Anyway, good news is everything is working now