design question: context: an organization wants t...
# prisma-whats-new
q
design question: context: an organization wants to have a user mgmt system in their intranet. This is the flow 1. admins add which users, identified by unique email addresses, are eligible to login - they add them to their user mgmt 2. admins add roles to each user 3. users login with google/FB or register in the app of the organization 4. only users with a verified email can access (some parts - depending on their roles) the application problem: using auth0 integration in graphcool, this seems impossible: admins can't add user profiles if they don't know the
auth0Id
. Since they first want to add eligible addresses before people can login, it's impossible for them to know this
auth0Id
. Admins don't want to wait for users to login first, since that isn't very user friendly.