Hey all, One very nice feature would be to have "read only" groups for certain users, so they could actually see what's inside (to avoid importing new songs and make doubles, for example), but wouldn't edit the carts' details.
Hoggins! Le 04/04/2017 à 16:28, Fred Gleason a écrit : > On Apr 4, 2017, at 09:13, Andy McCall <[email protected] > <mailto:[email protected]>> wrote: > >> In RDLibrary it works fine - the groups we don't want them to see are >> duly hidden but in RDAirplay all groups are still visible. I'm >> guessing that it's going to be something simple I've missed but for >> the life of me I can't find what it is. > > You have two different permission systems in play here: > > 1) The “Production” one — configured in RDAdmin->ManageUsers. > Controls what groups are visible ‘per user’; in RDLibrary. This is > the one that you’ve configured already. > > 2) The ‘On Air’ one — configured in RDAdmin->ManageGroups. Controls > what groups are visible ‘per service; in RDAirPlay. > > You may be asking: “why have two?” One reason is because you > sometimes want your on-air folks to be able to get to things for > on-air playout, but not be able to modify them in RDLibrary (think > station imagers, EAS scripts, legal IDs, etc). > > Cheers! > > > |----------------------------------------------------------------------| > | Frederick F. Gleason, Jr. | Chief Developer | > | | Paravel Systems | > |----------------------------------------------------------------------| > | A room without books is like a body without a soul. | > | -- Cicero | > |----------------------------------------------------------------------| > > > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
