There are many resources that all have emails on them. The projectMembership, the User, the Patient / Practitioner etc. Just confirming that the email that matters here, for auth0 login, is the email on User. Or is it supposed to be projectMembership's email? Side-question: I noticed that if I go to project / users it lists users (people that can login to medplum), but if I go to "resource type User" it only shows Users I have manually created in our backend logic. Meaning, if we use the medplum app "invite user", it doesnt create a User resource for that user, BUT that user still shows up under project / users. Its confusing. Is project / users pulling from "projectMembership" or something? What is a User for then? Do I need to create Users for external IDP to work, or should I only use projectMemberships and not create Users at all?

@oscadev The User resource is the one that matters for login. Have you seen the User Management Guide - https://www.medplum.com/docs/auth/user-management-guide. This should explain the relationship between all the Resources

Hey @oscadev , to answer your second question, I think you are creating server scoped Users, which you do not have access to. When you go to, project/users, that is showing you all the ProjectMemberships. You can invite Users as project scoped, and you will be able to manage the actual User resources. You can read about project vs server scoped Users [here](https://www.medplum.com/docs/auth/project-vs-server-scoped-users).