Authentication identifies the person who signs in to your Orbit app. Google sign-in needs a login button in the app and Google OAuth credentials.

The [Orbit product FAQ](https://orbitapps.io/) describes these two parts. Sign-in does not, by itself, establish which private pages or records that person should see.

## Identity and access are different checks

Consider an example customer portal with two customers, Alice and Ben. Each customer should see only their own requests.

When Alice returns from Google without a sign-in error, you have checked her sign-in. You have not yet checked whether she can open Ben's requests.

The portal needs separate access rules for private pages and records. Test those rules with separate accounts and test data before you add customer data. A successful login is not a substitute for that test.

[Review an app before launch](/guides/review-an-app-before-launch) covers checks for signed-out visitors, signed-in accounts, and private records.

## Google credentials belong to the app's integration

Google provides the OAuth **Client ID** and **Client secret** for a **Web application** client. Orbit stores the secret encrypted. The secret reaches the app at the next deployment.

Google also needs a matching callback URL. For an example portal at `https://portal.example.com`, that URL is `https://portal.example.com/auth/google/callback`.

Each address where people sign in needs its own matching redirect URI. A custom domain therefore matters to sign-in configuration, not just to the app's appearance.

Orbit requests the Google scopes `openid`, `email`, and `profile`. These scopes do not define access to the portal's private requests.

Use the [Google Sign-In reference](/integrations/google-sign-in) for the settings location, credential fields, and callback URL rule. That reference does not cover credential submission or deployment controls.

## App sign-in is not platform API authentication

A Google client secret and an Orbit platform API token serve different connections:

| Connection | Credential | Purpose |
| --- | --- | --- |
| A person signs in to your app with Google | The app's Google OAuth configuration | Identify the person who signs in. |
| An HTTP client calls the Orbit platform API | An Orbit API bearer token | Authenticate a platform API request. |

Do not use a Google client secret as an Orbit API bearer token. Do not put either secret on a public page or in an Orbit Agent request.

For a client that needs to list Orbit apps, read [API bearer authentication](/reference/api-authentication). That reference does not configure sign-in for your app's users.