Sign-in providers
Prove an account is really you by signing in to a service you already use elsewhere.
Connecting one of these accounts is a step in identity verification: signing in somewhere you already have a real presence is evidence the account belongs to you. It has nothing to do with signing into the Xuda dashboard itself, that is a separate, always-available flow; this is what Verification calls Level 4, Established.
Providers
How connecting one works
Xuda checks the provider has an app registered
A provider with no client id and secret configured on this server is reported unavailable rather than offered as a button that would fail.
You are sent to the provider to sign in
Every provider redirects back to the same fixed address, https://xuda.ai/social-oauth (or the dev
equivalent), so nothing about the redirect depends on which provider you picked.
Xuda reads back a stable identity
The code Xuda receives is exchanged for the provider's own id, display name, and a public profile address where the provider has one, and that becomes the evidence attached to your verification.
Where Xuda already holds a client for a platform, registered for something else entirely (Google's YouTube integration, X's OAuth2 client), that same app is reused here rather than asking anyone to register a second one. A dedicated entry always wins if one exists.