Where it lives
Open Platform > Agents > Skills registry and select a skill that signs people in. Its card has a Sign-in app section (The app people sign in through when they connect Gmail.) whose first line says which app is in use:
A member's view of the Sign-in app section: which app Gmail signs in through, and its client ID. Shown with sample data.
Shared app or one per skill
Admins choose between two apps:Set it up
Open the form
Create the client at the provider
Save the client

Setting up a separate app for Gmail: the steps for Google, the redirect URI to register, the scopes to enable, and the client fields. Shown with sample data.

Your organization's shared Google app, ready: its client ID, the redirect URI, the scopes to enable, and Remove or Replace. Shown with sample data.
Where else it appears
- The connect dialog. An admin who connects an app with no sign-in app available can set one up right there; the dialog then reads You’ll sign in with Google through your organization’s app. Other people are asked to have an admin set it up.
- Company Brain. Platform > Agents > Knowledge > Settings > Sign-in apps shows the Google and Microsoft apps your sources sign in through, for example Google Drive sources sign in through it, and lets admins set them up there. When you add a source, admins also get a Sign-in app link there (Company Brain).
- Your own APIs. An API you add from an OpenAPI spec can use OAuth 2.0 (each person signs in) (admins only). Enter the Authorization server URL and select Find endpoints to fill the Authorize URL and Token URL from its OAuth metadata, or type them. Add the Scopes (separated by spaces), register the Redirect URI shown in your OAuth app, then paste its Client ID and Client secret. The secret is stored encrypted and never shown again. Its card in the Skills registry then shows its Sign-in app.
Google Cloud Console
Pick a project and enable the APIs
Set up the consent screen
Add the scopes
Create the client

