Allow the orgaadmin to do more

[luisa-beerboom]

Closes #2737
Also allow cloning and deleting of locked meetings as long as the caller has settings manage perms in that meeting

[hjanott]

LGTM. I added some suggestions of which some repeat in other places of the code.

[luisa-beerboom]

I'll preface this by saying: If you want backend development to run efficiently please provide payloads if something's not working. Otherwise the bugs may be hard to replicate.

Also: From the fact that I couldn't even replicate the easy-to-understand ones, I wonder if maybe you tested with the wrong backend version.

Found some permission issue: All is tested as Orgaadmin which is not part of a committee or meeting.

* Committee menu: Create a meeting is not possible. Orgaadmin needs to be committee admin to create a committee. Following the superadmin permissions, this should be possible without setting the orgaadmin as committee admin.

Couldn't replicate.

* Committe menu > meeting edit: Edit is not possible. Wanted behavior: Same as above.

There's some fields that shouldn't be working, like the jitsi fields, however I can't tell if they're the ones causing problems for you. Please tell me what fields are causing problems specifically (maybe using the action documentation for meeting.update as a guideline) and please provide a payload anyway.

* Meeting > Participants > Add or edit a user: Adding or editing a participant doesn't work. Permission is missing. Wanted behavior: Should work, without being a part (admin) of the meeting.

Couldn't replicate, neither with user.create nor user.update.

* Motions > create a motion: Didn't work if the submitter is a new participant. This is a follow up of the previous point. I assume, that this behavior will happen on every action that requires to add or edit a participant. Wanted behavior: Creating a motionwithout being part of the meeting should be possible. Just like superadmins can do it.

As far as I know the client adds the new user separately. Since there are two actions involved, I can't even tell if this is actually a backend problem, or if the client is doing something wrong.

* Meeting > Autopilot: If something is projected, that provides the possibility to create a point of order, this action doesn't work. An error appears, because the orgaadmin is not part of the meeting. -> Creating a point of order should be possible, just like it is for a superadmin.

I don't fully grasp what situation you are talking about, since projection dont' have points of order. Also the snackbar message is clearly a client-side error. While this may just be a chain reaction thing caused by a backend error, I really can't tell what the error would actually be, so please provide more information

[Elblinator]

The first one is an already existing issue
an other issue will be created for that
OpenSlides/openslides-client#4608

Committe menu > meeting edit: Edit is not possible

{
   "action": "meeting.update",
   "data": [
       {
           "start_time": 1738710000,
           "end_time": 1739401200,
           "name": "Test (2)",
           "location": "",
           "organization_tag_ids": [
               1
           ],
           "external_id": "",
           "id": 22
       }
   ]
}

{"success": false, "message": "Missing permission: Not admin of this meeting"}

Meeting > Participants > Add a user

{
    "action": "user.create",
    "data": [
        {
            "first_name": "",
            "last_name": "",
            "username": "ihklh",
            "is_active": true,
            "is_physical_person": true,
            "email": "",
            "meeting_id": 22,
            "vote_delegations_from_ids": [],
            "group_ids": [
                93
            ]
        }
    ]
}

{
    "success": false,
    "message": "You are not allowed to perform action user.create. Missing permission: Permission user.can_manage in meeting 22"
}

Meeting > Participant > edit a user:

{
    "action": "user.update",
    "data": [
        {
            "id": 11,
            "meeting_id": 22,
            "vote_delegations_from_ids": [],
            "group_ids": [
                95
            ]
        }
    ]
}

{
    "success": false,
    "message": "You are not allowed to perform action user.update. Missing permission: Permission user.can_update in meeting 22"
}

Motions > create a motion: Didn't work if the submitter is a new participant.:
this should word with yourself as the orgaadmin:

[
    {
        "action": "motion.create",
        "data": [
            {
                "meeting_id": 22,
                "title": "jlk",
                "text": "<p>jjkl</p>",
                "workflow_id": 33,
                "agenda_create": false,
                "agenda_type": "internal"
            }
        ]
    }
]

{
    "success": false,
    "message": "The following models do not belong to meeting 22: ['user/1056']",
    "action_error_index": 0,
    "action_data_error_index": 0
}

Meeting > Autopilot: If something is projected, that provides the possibility to create a point of order, this action doesn't work. An error appears, because the orgaadmin is not part of the meeting
-> seems to be a client related issue
is also an issue in main aka it's own issue
OpenSlides/openslides-client#4607

[luisa-beerboom]

Motions > create a motion: Didn't work if the submitter is a new participant.: this should word with yourself as the orgaadmin:

[
    {
        "action": "motion.create",
        "data": [
            {
                "meeting_id": 22,
                "title": "jlk",
                "text": "<p>jjkl</p>",
                "workflow_id": 33,
                "agenda_create": false,
                "agenda_type": "internal"
            }
        ]
    }
]

What does "new participant" mean? Does that mean that you create a user before? Can you add a payload for that then?
Also I do not see a submitter id in the payload anyway. How's this supposed to work?

[Elblinator]

Motions > create a motion: Didn't work if the submitter is a new participant. This is a follow up of the previous point. I assume, that this behavior will happen on every action that requires to add or edit a participant. Wanted behavior: Creating a motionwithout being part of the meeting should be possible. Just like superadmins can do it.

What does "new participant" mean? Does that mean that you create a user before? Can you add a payload for that then?
Also I do not see a submitter id in the payload anyway. How's this supposed to work?

The new participant is working. Please ignore that part.
The orgaadmin cannot add themselves if they are not part of the meeting. The superadmin can do so.
That the submitter_id is not send is correct. The submitter_ids is only send if the submitter(s) are changed manually. Meaing if a user is not sending submitter_ids then they are themselves assignt as the submitter

The orgaadmin should be able to add themselves (only if they do not send submitter_ids) as submitter.
The only other part where I see this relevant is the speaker.create action

[hjanott]

code lgtm.