In terms of architecture, how does one differentiate the identities of common users and respondents?

A WebApp has two types of users at the same time. one is asking questions and the other is answering questions. how can we better maintain these two identities and their respective states? Solution 1: the same person needs to register two times. one account is the user and the other account is the responder. to change the identity, log out first and select the identity duplication... A WebApp has two types of users at the same time. one is asking questions and the other is answering questions. how can we better maintain these two identities and their respective states?

Solution 1: the same person needs to register two times. one account is the user and the other account is the responder. to change the identity, log out first and then select the identity to log on again. This seems clearer.

Solution 2: All users are normal users in the initial state. to be promoted to the respondent, you must submit an application. after the application is approved, add the respondent tag under the original user information, the corresponding display content will also change. it can be said that the normal user status may not be returned.

Solution 3: The two types of user registration procedures are the same. After registration, the logon page is redirected to the logon page. on the logon page, select an identity to log on. In fact, this is to differentiate identities under a single account, you also need to log on again when switching.

The answer is just an example. the user behavior of these two types of users is very different, and some content presentation will also be differentiated. for example, the first type is the patient, one is doctors, the other is drivers, and the other is passengers. which solution is used for better management and maintenance?

I don't know if my description is clear. if you have any experience in dual-end or multi-Account logon, please give me some advice.