.jpeg)
Two new buttons on the login page: “Sign in with Google” and “Sign in with Microsoft.” That's it. No setup, no configuration, no token handling on your part.
For existing customers: If the email address on your Google or Microsoft account matches your bchic account, you can log in with it now. The account is automatically linked the first time. Your previous password will still work.
For new users: Registration is now just one click away. Select a Google or Microsoft account, confirm access, done. Don't set a password, don't wait for a confirmation email.
Two reasons.
First, passwords are friction. Every forgotten login is a support ticket or a user who simply won't come back. OAuth eliminates the problem at the source.
Second, enterprise customers expect SSO capability. Google Workspace and Microsoft 365 are standard in virtually every company. Anyone who rolls out an analytics tool doesn't want to send 30 people individual login details.
The integration uses OAuth 2.0 with PKCE. That means:
For teams with multiple users, this also works when inviting: New team members receive an invitation email and can register directly via Google or Microsoft without having to create a password first.
Your data, dashboards, and settings remain exactly the same. OAuth only changes the way to the door, not what lies behind it. And if you want to continue using your email and password, you can do so.
Just click “Sign in with Google” or “Sign in with Microsoft” the next time you log in. It's done.