Access User Details, when Microservice/business is about handling Auth and users

[deadmann]

Dear folks,

My case is a little different from those duplicated answers you pointed out.

I wished to separate my services and be a separate clean architecture project.
I have a few businesses currently, including:

• Identity,
• Supports (provide after-sale support),
• Integrations (Data that should be read from another system),
• Web Container (although I couldn't separate it to call it a container)
• ... later Notification as well

In these ten years of my programming career, I didn't have many failures, and everyone was happy with my work.
However, when it comes to Identity, even though I had to implement all Microsoft contracts for Identity myself for using MongoDB, long ago, From the beginning of time it was too hard for me to comprehend it, or use it, and still it troubles me.

Due to that, I went searching for too long to find a full course 7.5~H, and I found out that my migration doesn't apply,... there is no DbSet, and I can't add DbSet to the interface because it's in a lower-level architecture.

But in this business, I need admins to list support members and customers, and support members too, need to list customers...

Customers need to have more details, otherwise, I don't understand the meaning of using ApplicationUser instead of IdentityUser...

1. Should I separate the Users table?
2. Should they also be divided into Customer and Member considering they may switch hats?
3. If I separate them, how can I keep integration between Users and the Identity?

Thank you,
Hassan F.