Google Workspace logo A new agentic setting for OAuth clients ahead of Workspace MCP servers. Dear developer, You are receiving this communication because your organization administers or develops applications that connect to Google Workspace via OAuth. We will soon roll out Google Workspace Model Context Protocol (MCP) servers that expose new functionality to external AI agents across Gmail, Drive, Calendar, and other Workspace apps using the open MCP. Ahead of this launch, we are introducing an “agentic” setting ( is_agentic ) on Google OAuth clients, so that Google and Workspace administrators can differentiate AI agent traffic from traditional app traffic. Only OAuth clients marked as agentic will be able to call Workspace MCP servers. We are announcing this change early so developers have time to prepare. If your app is not an AI agent and only uses Google Workspace REST APIs (for example, the Gmail API or Drive API), you do not need to take any action for this change. We have provided additional information below to outline the technical impact of this change and the actions required to keep access to Workspace MCP servers. What this means for your organization Key changes and timelines: October 12, 2026 (New “agentic” OAuth client classification): Developers can directly mark their OAuth clients as "agentic" ( is_agentic ) in the Google Cloud console. November 11, 2026 (Only agentic clients can call Workspace MCP servers): Google will reject requests to Workspace MCP servers from OAuth clients that are not marked as agentic. November 12, 2026 (The agentic setting becomes permanent): Starting on this date, you can no longer change the agentic setting on an existing OAuth client. To change it, create a new OAuth Client ID. Potential impact: Refused access: Starting November 11, 2026, Workspace MCP servers will reject requests from any app or integration whose OAuth client is not marked as agentic. The error message will state “the client isn't marked as an AI agent” and will link to steps to fix it. New OAuth Client ID requirement: OAuth clients that are not marked as agentic by November 12, 2026 will remain non-agentic and cannot call Workspace MCP servers. To use MCP after this date, you will need to create a new OAuth client marked as agentic and update your app to use it. Unaffected applications: Apps that are not AI agents and only call Google Workspace REST APIs are not affected by this change. Impacted customers/accounts: Your affected projects are listed below: automated-skein-503416-b4 What you need to do Action required: Identify your AI agent clients: Identify your OAuth clients that belong to AI agents, including agents that currently use Workspace REST APIs only. Only mark OAuth clients that are used by AI agents. Agentic clients will have separate security controls applied, such as agent access controls. If an app handles both AI agent and non-agent traffic, use a separate OAuth client for the AI agent. Mark them as agentic between October 12 and November 11, 2026: Turn on the agentic setting for these OAuth clients in the Google Cloud console so they can call Workspace MCP servers. Plan for the setting becoming permanent starting November 12, 2026: To change the setting on an existing OAuth client after this date, you will need to create a new OAuth Client ID. When you create a new OAuth client, you must choose whether it is agentic. We are here to help If you have any questions or require assistance classifying your OAuth clients: Review our documentation on Managing OAuth Clients Contact your Google Account Manager or Technical Account Manager Contact Google Workspace Support with your OAuth 2.0 Client ID and Google Cloud Project ID Thanks for choosing Google Workspace. – The Google Workspace Team © 2026 Google LLC 1600 Amphitheatre Parkway, Mountain View, CA 94043 You have received this important update about your Google Workspace account because you designated this email addres … (truncated)

From: "The Google Workspace Team" [workspace-noreply@google.com] Subject: Thank you for activating your subscription Thanks for activating your subscription ## Your Google Workspace Business Starter subscription has been activated Hello, Thank you for taking the steps to activate your Google Workspace Business Starter subscription. You can continue using the available services. If you are looking for additional services, you can compare Google Workspace editions (https://support.google.com/a/answer/6043385?utm_source=10901509&utm_medium=email) or visit the Get more services page in the Google Admin console. To prevent disruption of services, follow the steps below to keep your billing information up to date. ### Update billing information - Sign in to your Google Admin console (https://admin.google.com?utm_source=10901509&utm_medium=email). - Go to **Billing > Payment accounts > View payment methods**. - Review your primary payment method and update if necessary. For more information on updating your payment method go to Fix payment and billing issues (https://support.google.com/a/answer/2523116?utm_source=10901509&utm_medium=email). ### Your Google Workspace account **Username:** info@bennettandgrant.com **Domain:** bennettandgrant.com Sign in (https://admin.google.com) Sincerely, The Google Workspace Team (C) 2026 Google LLC 1600 Amphitheatre Parkway, Mountain View, CA 94043 * Google Asia Pacific Pte. Ltd., 8 Marina View, #30-01, Asia Square 1, Singapore 018960 * Google Ireland Ltd, Gordon House, Barrow Street, Dublin 4, Ireland. You're receiving this mandatory email service announcement to update you about important changes to your Google Workspace product or account.

From: "The Google Workspace Team" [workspace-noreply@google.com] Subject: Payment failure: Google Workspace Business Starter for bennettandgrant.com Update payment method to avoid suspension ## Don't lose access to Google Workspace Business Starter The last payment for your Google Workspace Business Starter subscription for bennettandgrant.com failed. This indicates that there's something wrong with your payment method. To prevent the suspension of all services for all users on October 2, 2026: - Contact your bank or credit card company to resolve the issue with your payment method. - Sign in to your Google Admin console and click **Billing** to retry or update your payment method and pay your outstanding balance. If you can't resolve the issue, you'll need to add a new payment method instead. See complete instructions for fixing payment and billing issues (https://support.google.com/a/answer/2523116?utm_source=9055414&utm_medium=email) or contact our support team (https://support.google.com/a/answer/1047213?utm_source=9055414&utm_medium=email) for additional help. Sign in (https://admin.google.com) Sincerely, The Google Workspace Team (C) 2026 Google LLC 1600 Amphitheatre Parkway, Mountain View, CA 94043 * Google Asia Pacific Pte. Ltd., 8 Marina View, #30-01, Asia Square 1, Singapore 018960 * Google Ireland Ltd, Gordon House, Barrow Street, Dublin 4, Ireland. You're receiving this mandatory email service announcement to update you about important changes to your Google Workspace product or account.