You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently in the Meeting Application (Pro) 1.9.8 any user can Edit any meeting.
A suggestion would be to only allow simple users to Edit their own meetings or the meetings they are Leaders of, while Admins can Edit / Remove any of them.
Environment: Windows 10, XWiki 11.3.5 with MySQL 5.7 and Edge 18
The text was updated successfully, but these errors were encountered:
I disagree with making any rights settings on the meetings by default through the meeting application.
The 'wiki' principle is that this application is a helper for creating structured pages in a wiki which is that it is a collaborative place where anyone can contribute, unless otherwise specified for the entities which are wiki pages.
The "collaboration by default" is very important to me as a feature of XWiki. If the application would be imposing a rights schema for the different roles of the meeting, I would consider that a break of that principle.
It would also encourage rights proliferation, as it would set rights at the level of each page of the meeting.
Also, keep in mind that the meeting allows to create meeting notes pages in any page hierarchy of the wiki. So if at some point some meeting notes need to be protected from collaboration with some people, they can be stored in a hierarchy on which the access is restricted.
Regardless of whether it may be a good idea (which I think it isn't), one thing is sure, for me, this is by no means Critical, for the reasons I explained above.
Currently in the Meeting Application (Pro) 1.9.8 any user can Edit any meeting.
A suggestion would be to only allow simple users to Edit their own meetings or the meetings they are Leaders of, while Admins can Edit / Remove any of them.
Environment: Windows 10, XWiki 11.3.5 with MySQL 5.7 and Edge 18
The text was updated successfully, but these errors were encountered: