Google Sign-In lets people sign in to your Orbit app with a Google account. The app needs a Google login button and your Google OAuth credentials.
This reference describes the integration settings. It does not cover credential submission or deployment controls.
Where the settings appear
Open your app in Orbit Studio, then open Settings and Integrations. The app's top bar also has Set up integrations.
The Google row appears only when the app has Google sign-in. The row shows Set up before configuration and Manage when credentials already exist. Get OAuth keys opens the Google Cloud credentials page.
The Orbit product FAQ describes the login button and Google credentials as the two parts that enable sign-in.
Credential fields
| Field | Required | Value |
|---|---|---|
| Client ID | Yes | The ID of a Google OAuth client with the Web application type. |
| Client secret | Yes | The secret for that same OAuth client. |
Orbit stores the secret encrypted. The secret reaches the app at the next deployment, not when you edit the credentials.
Do not put the client secret in an Orbit Agent request or on a public page.
Callback URL
In Google Cloud Console, the OAuth client's Authorized redirect URIs must include the app address followed by /auth/google/callback.
For an example customer portal at https://portal.example.com, the callback URL is:
https://portal.example.com/auth/google/callbackReplace the example address with the address people use to sign in. Add one redirect URI for each address that serves sign-in. This includes a custom domain or another environment when people use that address.
Requested scopes
Orbit requests these Google scopes itself. You do not enter them in Orbit:
openidemailprofile
These Google scopes do not define which private pages or records a person can access in your app.
Check sign-in and access separately
For the example portal, a sign-in check must use an app address with a matching redirect URI. After deployment, a test account must return from Google to the app without a sign-in error.
That result checks sign-in, not the portal's access rules. Before you use customer data, test that each account can access only the pages and records you intend. Use Review an app before launch for those separate checks.