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

Prevent possibility to edit "new participant" #2787

Closed
Elblinator opened this issue Sep 12, 2023 · 0 comments · Fixed by #2815
Closed

Prevent possibility to edit "new participant" #2787

Elblinator opened this issue Sep 12, 2023 · 0 comments · Fixed by #2815
Assignees
Labels
Milestone

Comments

@Elblinator
Copy link
Member

Elblinator commented Sep 12, 2023

Current behaviour:
If an admin adds an account to a meeting and changes the personal information (without having the right to do so) then the following Error is thrown and the account is not added as participant:

Error: You are not allowed to perform action user.update. Missing permissions: OrganizationManagementLevel can_manage_users in organization 1 or CommitteeManagementLevel can_manage in committee 10 or Permission user.can_manage in meeting 56

Recreation:

  1. create an admin (not super-/orga-/accountadmin) who is only admin in one meeting (meeting A)
  2. create a participant (C) in meeting B
  3. With the admin in meeting A try to add C (select C in step 2)
  4. go to step 3 and change your present status from present to not present to present
  5. and change/add some information
  6. press save
  7. the error is thrown

if you were not able to change/add any information in 4. then do not add C and reload the participant-list and try again

Wanted behaviour:
a normal admin should not be allowed to change any information from an already existing account, except if the admin is an admin in ALL meetings from this account.
The personal information-fields of such accounts should be disabled

What the add page most of the time looks like:
add_account

(edited after revelation that the bug needs an autoupdate to make changes possible, for the whole discussion see #2815 )

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

Successfully merging a pull request may close this issue.

2 participants