https://linen.dev logo
I have a question about use case two different cas...
# 🖥│support-forum
d
1. One client that has multiple Gmail accounts for support. Can I connect them through Composio? 2. The second one is multiple clients that have one Gmail account each. Can I also connect them and use Composio's authorization instead of creating my own Google authorization workflow?
u
Hey @DerHerrDirector, yes, your use case is supported. You can refer this doc on user management: https://docs.composio.dev/docs/user-management and lmk if you need any help. Thanks!
d
ok got it. and you mention in the docs that hosted auth is just for testing and not production? i feel like one of the benefits is that we do not do our own costly google approval for using login. is that not that case?
u
Hey @DerHerrDirector, "*I feel like one of the benefits is that we do not do our own costly Google approval for using login*" — I'm assuming you are referring to custom auth(Bring your own credentials). It is recommended to use your own credentials for production as you'll have more control over your auth app and branding. You can still use Composio's managed auth(default auth app) for production, but it is recommended to be used for testing/development due to the above caveats.  Also, just an FYI as you might've confused Custom auth with Hosted authentication (auth link). Hosted auth is an interface that lets you handle the entire authentication process—OAuth flows, API key collection, or custom fields like subdomain, etc., and not the actual auth app credentials.