[RFC] Changes in signup flow

Problem

The current PATCH /users/self API allows users to update their roles even after joining the server. Restricting the update creates an issue, as this API is utilised in the signup flow where users select their roles while joining the RDS community. Restricting the roles update will impact the signup flow especially for user who wish to join as mavens.

Proposed Solution:

Solution 1 :

To address this issue, role update should be restricted to once per user in the PATCH /users/self API. By doing so, users will still be able to select their roles during the signup process, but subsequent role changes will not be allowed.

Solution 2 :

Role update will be allowed only when the field incompleteUserDetails is set to false and the username is yet to be updated in RDS backend. Both the solutions will have the same end result

Acceptance Criteria:

• Users should have the ability to select their roles during the signup process for the RDS community.
• Users should not be able to change their roles through any UI or API once they have successfully joined the RDS community.
• Users who wish to join as Mavens should have least steps in the signup process.
• Super Users will retain the ability to update their roles and the roles of other users.

Start by tracing the PATCH /users/self API and the signup flow described in the issue, including how role updates, incompleteUserDetails, username changes, and Super User permissions are handled. Resolve which proposed solution applies, then verify the acceptance criteria for regular users, Maven signups, and Super Users across the UI and API.