please send me your JIRA login privately and i'll try to grant you necessary permissions
On Thu, May 12, 2016 at 12:01 PM, Tom Wagner <[email protected]> wrote: > Thank you, Maxim. Very helpful. > > Wilco on the JIRA additions. I've created a login there just now, but it > seems the site is currently in an anti-spam lockdown for non-implementors > like myself. I will try again when this is lifted...they project some time > tomorrow. I will also try to provide a precise description of the failure > of the participant reminders in my 3.1.1 install there. > > Best, > =tew= > > > On 05/11/2016 08:03 PM, Maxim Solodovnik wrote: > > Will answer inline :) > > On Thu, May 12, 2016 at 12:58 AM, Tom Wagner <[email protected]> wrote: > >> TWIM, >> >> The most complete OM Documentation I've been able to find is the issue >> for 2.x on the Wiki. But, there are some puzzling new additions to the >> Admin UI in 3.x, and some ambiguities for me that my thrashing about in the >> underbrush of the Wiki and JIRA has not resolved. >> >> I'm hoping this list can shed some light for me on the following: >> >> 1. Administration / Users / *Rights*: can someone provide a detailed >> description of the permissions granted and functionality/UI enabled by the >> pull-down items. Sorry, but these are not self-explanatory to me, >> particularly the "Room" permission. >> 1. Admin >> >> means user has access to Administrarion area > >> >> 1. Room >> >> mean user can enter the room > This might be the only right for ex. for users enter the room via plugin, > these user have no rights to other areas of OM > >> >> 1. Login >> >> mean user can login to application > This right is given on user activation (in case activation is turned on) > >> >> 1. Dashboard >> >> mean user can browse all non-admin areas of OM (recordings, dashboard, > profile etc.) > >> >> 1. Soap >> >> mean user can act as SOAP admin to authenticate requests via REST/SOAP API > should be added with Login right > >> >> 1. Administration / Conference Rooms: >> 1. *Appointment Room* Checkbox: Checking this has the >> counter-intuitive (for me) result of removing the Room from the >> pull-down >> assignment in the Calendaring UI. What is an 'Appointment Room' and >> how >> does toggling it modify the functionality of the 3 basic room types? >> >> Actually this checkbox should be "disabled", it shows with Room is tied > with appointment > So it must be read as "This room was created by appointment" > Could you please file JIRA issue against this? > >> >> 1. *Allow Recording* Checkbox: does this block *all* recording of the >> room activity, or just recording by the participants? It would be >> valuable >> to block participants, yet allow the originator/moderator to record. >> >> In case this checkbox in UNchecked all recording controls will be removed > from the room for everybody > >> >> 1. *Wait for Recording* Checkbox: completely unclear on what this >> means. ?? >> >> In case this checkbox is checked special alert dialog will be displayed > to the user > with some info message > >> >> 1. Administration / Configuration: >> 1. *number.minutes.reminder.send* setting: the intentions seems >> quite clear with respect to calendared meetings, but it only appears to >> work for the Originator of the calendar event. Participants do get an >> initial notice email, but the reminder only seems to go out to the >> originator. This may be a bug, or might it be be affected by the User >> Rights assigned to the participants vs. the rights of the Originator?? >> I've been playing with adjusting the participant rights, but I'm not >> sure >> (see Question 1 above) what rights I am giving participants in order to >> possibly enable the reminders....of if this is even a factor. >> >> seems to be an issue :( reminder should be sent to all participants > could you please file JIRA issue? > >> >> >> Thanks for any response. I will continue to poke at item 3a, and >> possibly generate a bug report if I can't get the reminders to work >> reliably for me as this seems like key functionality in the Calendaring >> feature. >> >> If there is a 3.x copy of the User/Admin documentation out there that I >> have missed, please accept my apologies and point me to it SVP. >> >> Best, >> Tom Wagner, Jackson Orthopaedic Foundation IT >> > > > > -- > WBR > Maxim aka solomax > > > -- WBR Maxim aka solomax
