Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Users should be able to Edit only their own Meetings, Admins all #63

Open
ane-gabriela opened this issue Oct 11, 2019 · 2 comments
Open

Comments

@ane-gabriela
Copy link

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

EditAction

@ane-gabriela ane-gabriela added this to the 1.10 milestone Oct 11, 2019
@acotiuga acotiuga removed this from the 1.10 milestone Aug 27, 2020
@lucaa
Copy link

lucaa commented Sep 2, 2020

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.

@lucaa
Copy link

lucaa commented Sep 2, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants