Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/gcsconsultores/centros-estrategicos-gcs/llms.txt

Use this file to discover all available pages before exploring further.

GCS Centros Estratégicos uses environment variables to connect to Google Gemini AI and Microsoft 365 services. All variables go in .env.local for local development and are never committed to version control. In production (Vercel), set them in the Vercel dashboard under Settings → Environment Variables — the app reads them at build time and at runtime without any additional configuration.

​
Complete .env.local Template

Copy the block below into a new .env.local file at the root of the project and fill in each value before starting the development server. 
# ===================================================
# REQUIRED: AI Chat (Sally)
# ===================================================
GOOGLE_GEMINI_API_KEY=         # From https://aistudio.google.com/app/apikey

# ===================================================
# REQUIRED: Microsoft 365 (SharePoint + Teams)
# ===================================================
AZURE_AD_CLIENT_ID=            # Azure App Registration: Application (client) ID
AZURE_AD_CLIENT_SECRET=        # Azure App Registration: Client secret value
AZURE_AD_TENANT_ID=            # Azure App Registration: Directory (tenant) ID

# ===================================================
# REQUIRED: SharePoint Lead Storage
# ===================================================
SHAREPOINT_SITE_ID=            # SharePoint site ID
SHAREPOINT_LIST_ID=            # SharePoint list ID for leads

# ===================================================
# REQUIRED: Teams Meeting Creation
# ===================================================
DEFAULT_ORGANIZER_EMAIL=       # consultant@yourorg.com

​
Variable Reference

VariableRequiredDefaultDescription
GOOGLE_GEMINI_API_KEYYes—Google Gemini API key for Sally’s AI chat
AZURE_AD_CLIENT_IDYes*—Azure AD App Registration client ID
AZURE_AD_CLIENT_SECRETYes*—Azure AD App Registration client secret
AZURE_AD_TENANT_IDYes*—Azure AD tenant ID
SHAREPOINT_SITE_IDYes*—SharePoint site ID for lead storage
SHAREPOINT_LIST_IDYes*—SharePoint list ID within the site
DEFAULT_ORGANIZER_EMAILYes*—Organizer email for Teams meetings
* Required for production Microsoft 365 features; the app runs in development mode without them.

​
Required vs Optional

Not all variables are needed to run the app locally. Here is exactly what breaks — and what degrades gracefully — depending on which variables are present:
  • GOOGLE_GEMINI_API_KEY is the only variable required for Sally’s chat to work. Without it the AI streaming endpoint will fail immediately.
  • AZURE_AD_CLIENT_ID, AZURE_AD_CLIENT_SECRET, and AZURE_AD_TENANT_ID are all required together for Microsoft Graph authentication. Without them, lead submissions fall back to console logging (storage: 'local') instead of writing to SharePoint.
  • SHAREPOINT_SITE_ID and SHAREPOINT_LIST_ID are required for leads to be stored in the correct SharePoint list. The list must already exist with all required columns before the app first writes to it.
  • DEFAULT_ORGANIZER_EMAIL is required for Teams meeting creation. Without it, the meeting scheduling API returns mock join URLs rather than real Teams links.

​
Vercel Deployment

Once you are ready to deploy, add every variable to the Vercel project before the first production build. Changes to environment variables require a redeploy to take effect.
1

Open your Vercel project dashboard

Navigate to vercel.com and open the project for centros-estrategicos-gcs.
2

Go to Settings → Environment Variables

In the left sidebar, click Settings, then select Environment Variables from the sub-menu.
3

Add each variable with its value

For every variable in the template above, enter the Name and Value fields and click Save.
4

Set the correct scope

Choose Production as the environment. Enable Preview as well if you want full Microsoft 365 integration in preview deployments.
5

Redeploy the project

Trigger a new deployment (push a commit or click Redeploy in the dashboard) so that the new values are picked up by the build.

​
Security

Never commit .env.local to version control. It is already listed in .gitignore — do not remove that entry. The AZURE_AD_CLIENT_SECRET is a sensitive credential: rotate it before it expires and store it in a dedicated secrets manager (e.g. Azure Key Vault or Vercel’s encrypted environment variable store) for production deployments.
All variables listed here use the standard Next.js server-side convention — no NEXT_PUBLIC_ prefix — which means they are evaluated exclusively on the server and are never included in the JavaScript bundle sent to the browser. GOOGLE_GEMINI_API_KEY and all Azure AD credentials remain server-only at all times.

Build docs developers (and LLMs) love

Get started for freeTalk to us