> ## Documentation Index
> Fetch the complete documentation index at: https://docs.izumi.akiaconsulting.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Sign-in (Google, Entra)

> Set up sign-in with Google or Microsoft accounts.

Checked on Izumi 0.5.7, 2026-11-21 (code and production, read only).

Izumi has no passwords. People sign in with a Google or Microsoft (Entra ID) account. Here you set up those two sign-ins on the server. Sign-in for reading documents from Drive or SharePoint is a different thing: you set that up in [Connectors](https://docs.izumi.akiaconsulting.com/en/install/connectors.md).

> [!WARNING]
>
> Not checked live yet: creating the Google and Microsoft sign-in apps from scratch, and signing in with a Microsoft account. Google sign-in works on production (the sign-in page offers Google), and Microsoft sign-in is not turned on in production. The steps in the Google Cloud and Entra portals come from the install guide and the code.

## How it works

* A provider shows up on the sign-in page only when both its client ID and its secret are set. An ID without a secret (or the other way round) stops the app at start.
* The redirect URIs are exactly `<TB_PUBLIC_URL>/v1/auth/google/callback` and `<TB_PUBLIC_URL>/v1/auth/entra/callback`, without a trailing slash.
* After every change to `.env` run `docker compose up -d app`.
* When no provider is set up, the sign-in page says *"Sign-in is not set up yet. Ask the operator of this installation."*

![Izumi sign-in page with one provider, Google](https://mintcdn.com/akia-consulting/UfDKk95B0JApANc6/images/en/sign-in/01-sign-in-page.png?fit=max\&auto=format\&n=UfDKk95B0JApANc6\&q=85\&s=300683d9525b1adb479081300ab4abfe)

The image is the production sign-in page, where only Google is set up.

## Google

**1. Create an OAuth client**

In the Google Cloud console open `APIs and Services`, `Credentials`, `Create credentials`, `OAuth client ID`, type `Web application`.

**2. Add the redirect URI**

Under `Authorized redirect URIs` add `<TB_PUBLIC_URL>/v1/auth/google/callback`.

**3. Put the ID and secret into .env**

The client ID goes into `TB_OIDC_GOOGLE_CLIENT_ID` and the secret into `TB_OIDC_GOOGLE_CLIENT_SECRET`. Then `docker compose up -d app`.

* The scopes are `openid email profile`.
* Izumi trusts only addresses that Google has verified.

## Microsoft (Entra ID)

**1. Create an app registration**

In the Entra admin center open `App registrations`, `New registration`. For the default `TB_OIDC_ENTRA_TENANT=organizations` choose `Accounts in any organizational directory`. For a single tenant choose one tenant and put its GUID into `TB_OIDC_ENTRA_TENANT`. Personal Microsoft accounts are rejected.

**2. Add the redirect URI**

Under `Authentication` add the platform `Web` with the address `<TB_PUBLIC_URL>/v1/auth/entra/callback`.

**3. Create a client secret**

Under `Certificates & secrets` create a client secret. Its `Value` (not the `Secret ID`) goes into `TB_OIDC_ENTRA_CLIENT_SECRET`, and the `Application (client) ID` goes into `TB_OIDC_ENTRA_CLIENT_ID`. Write down the secret's expiry date.

**4. Add the optional claim email**

Under `Token configuration` add the optional claim `email` to the ID token. Without it Izumi compares `preferred_username` with the invitation, which can differ from the invited address.

**5. Restart the app**

`docker compose up -d app`. The Microsoft button appears on the sign-in page.

This app is only for signing people in. The app registration for reading SharePoint is separate and has different permissions: see [Connectors](https://docs.izumi.akiaconsulting.com/en/install/connectors.md).

## Who can sign in

* Sign-in needs an invitation. Invitations are created by a company admin in the app, see [People and invitations](https://docs.izumi.akiaconsulting.com/en/admin/people.md).
* Every company can restrict who may accept an invitation (allowed Google domains, allowed Microsoft tenants) in its settings, see [Companies, domains, roles](https://docs.izumi.akiaconsulting.com/en/admin/companies-domains-roles.md).

## Limits

* Sign-in with a Microsoft account has not been checked live (HC-OA-10 is open). Before you offer it to a company that uses Microsoft 365, go through the whole flow once on a test tenant.
* The app has no password sign-in and no other provider.

## Troubleshooting

| What you see | What to check |
| - | - |
| The app stops at start | An ID without a secret or a secret without an ID is set for Google or Entra. Both or neither. |
| A provider does not show on the sign-in page | Neither of the two fields is set, or you did not run `docker compose up -d app` after the change. |
| The provider returns an error about the redirect address (Google: `redirect_uri_mismatch`) | The address in the Google or Entra app is not exactly `<TB_PUBLIC_URL>/v1/auth/<provider>/callback`, without a trailing slash. |
| An invited person sees *"This company does not allow sign-in from this account (its allowed domains or tenants). Ask a company admin."* | Their Google domain or Microsoft tenant is not on the list in the company settings. |
| An invited person sees *"This account does not match the invitation. Open the invitation link again and sign in with the invited account."* (or the same with the address) | They signed in with an account whose address was not invited. With Microsoft also check whether the optional claim `email` is missing: add it under `Token configuration`. |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.