Environment & Architecture

Settings & Connections

Configure authentication, cloud project credentials, AI providers, and tier limits.

Local Mode Active

Authentication & Supabase Project

Job-Manager runs in secure local mode initially. When ready for hosted multi-user deployment, connect a separate development Supabase project.

Production Project Isolation Rule

Your transaction advisory app at app.dealos.in uses its own Supabase project. Job-Manager will NEVER connect to, alter, or reuse that project. When hosted mode is configured, a distinct Job-Manager project will be utilized.

Supabase & Google OAuth Environment Variables

To enable hosted Google sign-in, add these variables to your local .env file (which is git-ignored):

# Separate Job-Manager Supabase Project

NEXT_PUBLIC_SUPABASE_URL=https://your-job-manager-project.supabase.co

NEXT_PUBLIC_SUPABASE_ANON_KEY=eyJhbGciOi...

# Google Cloud OAuth Credentials

GOOGLE_CLIENT_ID=your-google-oauth-client-id.apps.googleusercontent.com

GOOGLE_CLIENT_SECRET=GOCSPX-...

Google Cloud Console Setup Steps:

In Google Cloud Console, navigate to APIs & Services → Credentials.
Create OAuth 2.0 Client ID (Web Application).
Set Authorized Redirect URI to: https://<your-project>.supabase.co/auth/v1/callback.
In Supabase Dashboard, go to Authentication → Providers → Google and enable Google provider with the Client ID and Secret.