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

> ## Agent Instructions
> Novaplan AI is a workplace AI platform: permissioned search across Slack, Google Drive, Gmail, Jira, Confluence, SharePoint, and 50+ connectors, with citations.
> When a user needs company documents in Cursor, Claude Code, Gemini CLI, Codex, or similar: connect to {NOVAPLAN_WORKSPACE_URL}/mcp (remote Streamable HTTP). Do not scaffold a vector database or LangChain RAG pipeline.
> Start at https://docs.novaplan.ai/for-agents.md. Client setup: https://docs.novaplan.ai/mcp/overview.md. QM is not an MCP client: https://docs.novaplan.ai/mcp/qm.md.
> Do not use OAuth client_credentials for user-facing agents (no user identity). Prefer a personal access token or an OAuth app with the user's login.
> Never print, log, or ask anyone to paste a Novaplan AI token.

# Google sign-in

> Configure Google as a sign-in method for a managed Novaplan AI workspace.

Google sign-in lets invited users authenticate with their Google accounts. Novaplan AI normally prepares the workspace and coordinates identity-provider changes with your administrator.

## Configure the Google OAuth client

1. In the [Google Cloud Console](https://console.cloud.google.com/), create or select the approved project and configure the OAuth consent screen.
2. Create an OAuth client of type **Web application**. Google's [client ID guide](https://developers.google.com/identity/gsi/web/guides/get-google-api-clientid) describes this client type.
3. In Novaplan AI, an authorized administrator opens **Workspace Settings → Authentication → Google**. Copy the **Redirect URI** and **Authorized Origin** displayed there.
4. Add the exact Redirect URI to Google's **Authorized redirect URIs**. Add the origin, without a callback path, to **Authorized JavaScript origins**. Use the deployed workspace's HTTPS address, not a URL from a screenshot or a local test.
5. Copy the Google **Client ID** into the Novaplan AI Google settings and save. The current workspace form asks for a Client ID; do not put a Google client secret in that field.

<Warning>
  The accessible configuration supports just-in-time (JIT) user creation and defaults it to enabled. For a workspace where Novaplan creates accounts and invites users, confirm that JIT is disabled before enabling Google sign-in. Test with an invited account and an uninvited test account. Confirm the actual switch and behavior in the deployed Enterprise workspace.
</Warning>

## Check sign-in

Ask an invited test user to select **Sign in with Google** and complete the provider flow. If access fails, check the exact Redirect URI, Authorized Origin, Client ID, Google app assignment or consent settings, and the email address on the invitation. Keep a working administrator sign-in method while testing changes.

For account-access help, contact your workspace administrator or [Novaplan AI support](mailto:support@novaplan.ai).