[aureliensibiril]

Why

The console replaced the Access Review > Connections page with Settings > Connectors > Marketplace, but the access review pages still sent readers to the old page, to per-row OAuth / API Key buttons, and to an organization dropdown on the source row. None of those exist any more.

What

Every connector page, _api-key-template.mdx, the overview, CSV sources and integration security now describe the current flow:

1. Settings > Connectors > Add more opens the Marketplace. Open the vendor, and when it offers several methods, pick one on "Choose how to connect".
2. Fill in Name and the method's fields, then click Connect.
3. In Access Review > Sources, click Add sources, tick the vendor and click Add.

Other corrections:

• The organization picker is the connector's Organization field in Settings, not the source row.
• An expired or rotated API key is replaced in place with Update API key, the key icon on the connector card (probod v0.320.0). The connector keeps its name and its sources. The Supabase, Mercury, authentik, Tailscale, Render, 1Password and Brex pages used to say to delete the source, disconnect and connect again.
• Reconnect only shows once a connection fails. The PlanetScale troubleshooting asked readers to reconnect a healthy connector to tick another organization, so it now says to disconnect and connect again.
• Client-credentials, workload-identity and app-install connectors are still replaced by disconnecting (the trash icon) and connecting again, after removing the sources that use them.
• Integration security: listing connectors never returns secrets, but showing a connector's health can decrypt the credential in memory. The diagram now shows removing the source and disconnecting the connector as two steps.
• Smaller fixes: Supabase connect errors appear in the Could not connect toast, not under a field; OVHcloud has no Scope field; authentik without Can view Brand keeps the Base URL as the source name.

Provider facts, Collected Fields tables, cautions and screenshots are unchanged.

How it was checked

Labels come from the console's locale files and the provider registrations at probod v0.330.2. Codex (gpt-6-astra) reviewed the final diff against that source. It found the six problems in the last two bullets above, and each was checked in source before fixing. npm run check:docs, docs:check-reference and npm run build pass locally.