How to handle Google OAuth setup for multiple client projects in Memberstack: Personal vs client Google Cloud accounts Answered
Quick question. For Google Oauth, when you use the Google Cloud, do you guys use your own account and just add a new project for each client or do you have the client do it on their account and walk them through the setup process?
Comments
4 comments
Hi Abel,
I'm not sure I understood your question... Did you follow the Google Authentication Tutorial to allow your clients to login using Google.
https://docs.memberstack.com/hc/en-us/articles/8327236548379-Google-Authentication
This setup you only have to do it once using your own account to integrate it with your project. After it has successfully integrated, your users can sign up and sign in using their Google accounts with the click of a button
Sorry for the confusion, I watched the tutorial and Julian used Google Cloud to make a new project in order to integrate Google Auth into the site. The thing is that it's not my site I want users for but a client's site that I am currently developing so that's why I'm wondering if the Google Cloud project should be on my gmail account or on theirs since it's their site or does it not make a difference?
When the site launches to production it should have the owner's account, because ethically the site belongs to the owner. That way it's only configured once and then you can forget about it.
Gotcha! Thanks!
Please sign in to leave a comment.