This official feed from the Google Workspace team provides essential information about new features and improvements for Google Workspace customers.
rss_feed

The Google Workspace Allowlisted Domains API is now generally available. Previously, administrators had to manage their allowlisted domains list manually through the Google Workspace Admin console. With this release, hosted under the Cloud Identity API suite as a top-level resource, organizations can securely automate and programmatically manage their list of allowlisted domains.

By programmatically managing trusted external sharing boundaries, Workspace administrators can easily automate domain lists. This allows organizations to restrict external collaboration to verified, trusted partners, thereby mitigating data exfiltration risks and strengthening overall security posture without manual administrative overhead.

This launch includes a robust set of core capabilities to support your domain management workflows:

  • Core CRUD operations: Programmatic Create, Delete, List, and Get capabilities to manage your list of allowlisted domains
  • Exact-match filtering: Easily check and verify the presence of specific domains using exact-match filtering within the List API

Note: Reseller-managed workflows are not currently supported.

Getting started

  • Admins: To configure these rules via the API, administrators must have either domain management or domain allowlist management privileges for Google Workspace. See our documentation to learn more.
  • End users: There is no end-user setting or action required for this feature.

Rollout pace

Availability

  • Available to all Google Workspace customers

Resources

Read More

We’re introducing two enhancements to the Calendar API that make it easier for admins to programmatically manage secondary calendars within their organization: a transfer API and a filter for secondary calendars owned by your organization.

Transfer API

As previously announced, the new endpoint in the Google Calendar API that allows administrators to programmatically transfer the ownership of secondary calendars is now being rolled out. Its functionality mirrors the data transfer feature currently available in the Admin console by permitting transfers between users in the same organization without sending emails or requiring confirmation from the recipient. Beyond replicating the Admin console functionality, the API provides greater flexibility by allowing administrators to transfer specific, individual secondary calendars.

Organization filter

To help organizations prepare for the upcoming secondary calendar data lifecycle changes, where secondary calendars will follow the lifecycle of their owner, administrators can now programmatically monitor the ownership status of their users' secondary calendars.

A new filtering option will be available in the CalendarList:list API method that restricts results to return only secondary calendars owned by the organization. When combined with the users.list method of the Admin SDK API, administrators can retrieve a comprehensive list of organization-owned secondary calendars across their users' calendar lists. The dataOwner field can then be used to verify current ownership status and make any necessary adjustments.

Getting started

Rollout pace

Transfer API
Organization filter

Availability

  • Available to all Google Workspace customers

Resources

Read More

At Cloud Next ‘26, we announced a new suite of agent tools for Google Workspace, including a Workspace MCP server, command line interface (CLI), and remote MCP integrations. 

Today, we are opening the Workspace MCP server to public developer preview. As AI agents become a central part of how we work, they need a standardized way to access the right context and tools. The Workspace MCP server provides that bridge, allowing AI agents to safely tap into the richness of Workspace capabilities.

Workspace MCP server: Now in public developer preview

The Workspace MCP server allows developers to access a suite of dedicated tools to power agents interacting with Workspace data:

  • Gmail MCP: Profile access, drafting, searching, and read/write capabilities.
  • Drive MCP: File fetching, permissions management, listing, and uploading.
  • Calendar MCP: Finding available times and managing events.
  • Chat MCP: Finding conversations, searching messages, and reading/sending replies.
  • People dictionary MCP: Managing user contacts and accessing profile information.

Empower agents with a secure ecosystem

As these agents scale, we are committed to maintaining a healthy ecosystem by addressing the unique risks associated with large-scale agentic actions, such as API abuse and unintended large-scale data egress. To foster innovation while managing the potential impact of high-volume data access, we are introducing a standardized tiering model for all agent tools inclusive of our APIs in Workspace.

This model is designed to manage agent workflows at scale, providing a structure as application impact increases The framework is intended to maintain the agility of developers:

  • Empowering the community: We expect less than 1% of active Workspace developers will need to move beyond our standard usage tiers. This means the vast majority of our developer community can continue to build and innovate without friction.
  • Scalability with confidence: For those developers and agents that grow to serve millions of users, the model provides a clear, predictable path to scale safely, ensuring the performance and data integrity that enterprise customers expect.

Getting started

Rollout pace

  • Workspace MCP server: Gradual rollout starting May 1, 2026
  • Workspace API and MCP tiering: Updated usage quotas for new projects only will roll out starting May 1, 2026. We'll notify owners of existing projects at least 60 days before any changes go into effect to ensure a smooth transition.

Availability

  • Available to all Google Workspace customers and developers

Resources

Read More

Last year, we announced the launch of the Google Classroom API Student Groups endpoints through the Google Workspace Developer Preview Program (DPP). Now, Student Groups endpoints are generally available, so developers no longer need to be in the Developer Preview Program (DPP) to access them. 

Student Groups endpoints enable developers to manage student groups and group members on behalf of administrators and teachers. Specifically, developers can: 

  • Create, modify, and delete student groups within a course 
  • Add and remove members within student groups 
  • Read members of student groups 

With this launch, developers can programmatically read and manage student groups in Google Classroom, enabling greater integration between Google Classroom and other tools used by teachers and schools. 

Getting started 

Rollout pace 

Availability 

  • API requests are permitted on behalf of teachers and administrators who have Google Workspace for Education Plus licenses 

Resources 

Read More