Workspace and accounts
How the two-tier shell maps a Google login to a workspace and each Google Ads customer to its own account.
The app has two tiers. The workspace holds the account list and shared settings — your profile, the Google Ads connection, and the org-wide kill switch. Everything account-specific lives under a project, where one project is exactly one Google Ads customer account.
Workspace tier
One Google login and its encrypted refresh token belong to the workspace. From it you connect Google Ads,
discover accessible accounts, and import the ones you manage. Workspace settings live under /app/settings:
- Profile — your account.
- Google Ads — connect, disconnect, and import accounts (
/app/settings/integrations/google-ads). - General — the org-wide auto-apply kill switch (see Safe-apply policy).
- MCP — the connect instructions for the MCP server (
/app/settings/mcp). - API — mint org-scoped REST keys (
/app/settings/api).
Account (project) tier
Each imported account gets its own space under /app/[projectId], grouped in the sidebar:
| Group | Pages |
|---|---|
| — | Overview, AI Copilot |
| Performance | Campaigns, Keywords, Quality score, Search terms, Ads |
| Growth | Audit, Recommendations, Approvals, History |
| Settings | General, Optimization, Tracking, MCP, API |
Account-scoped settings — including optimization targets, the
account's MCP connect instructions, and per-account REST API keys — live under /app/[projectId]/settings.
The distinction shows up over MCP as an argument, not a credential: a connected session reaches the whole
workspace, so account-scoped tools take a projectId (from gads_list_ad_accounts). See
Authorization.