4.20. Organisation Administrator - Update organisation users

Preconditions

1. The User must be authenticated and have the Organisation Administrator role.
2. The system must have a list of predefined roles that organisation administrators can assign to their users. This is not the full list of roles available (only will include Editor, Organisation Approver, Viewer and Organisation Administrator).
3. The user to be modified must exist on the platform and belong to the organisation of the Organisation Administrator
   

Postconditions

1. The user list is updated with the modified account.
2. The modified user belongs to the Organisation Administrator’s organisation
3. The modified user only has roles that can be assigned by the Organisation Administrator.
4. All assigned roles are correctly enforced by the system
   

Main flow

1. The Organisation Administrator retrieves a list of existing users that belong to his organisation with their details and roles (GET).
2. The Organisation Administrator uses an API to modify an existing user by modifying the required details (e.g., name, email) and assigning roles (PUT/PATCH).
3. The system validates the input data.
4. The system saves the changes and updates the user list.
   

Exceptions

[400 Bad Request] Invalid input:

If mandatory fields are missing or invalid, the system returns an error message.

[404 Not found] User not found

If the Organisation Administrator attempts to modify a user that does not exist or does not belong to his organisation, the system returns an error and prevents the action.

[500 Internal Server Error] System Error

If the system fails to save changes due to an internal error, it displays an appropriate message and logs the error for further investigation.