# Connection not enabled
## The error
`{"error": "invalid_request", "error_description": "...connection... not enabled for this client"}` or the Universal Login page missing the expected button.
## Why
Connections (database, Google, enterprise) are enabled per application. Creating a connection does not attach it to any app. The authorize call can also pin a connection with the `connection` parameter; if that connection is not enabled for the client, it fails.
## Fix
1. Dashboard > Authentication > Database (or Social/Enterprise) > your connection > Applications tab > enable the toggle for your application.
2. Or Application > Connections tab > enable it there. Same setting, two paths.
3. If you pass `connection` explicitly in the authorize call, verify the name matches exactly (it is the connection NAME, e.g. `google-oauth2`, `Username-Password-Authentication`, not the display name).
## Related: button missing on Universal Login
Same root cause, softer symptom: the social button does not render because the connection is not enabled for the app. Also check the connection itself is enabled at the tenant level (some social connections need keys configured before they activate).
## Multi-connection routing
- Identifier-first: let the user type their email and route by domain (home realm discovery) instead of showing every button.
- Organizations: enable the connection on the ORGANIZATION, not just the app; org logins only offer org-enabled connections.
## Checklist
- Connection enabled for the app AND (for orgs) the organization.
- `connection` parameter uses the exact connection name.