> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blackmountain.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Google Workspace Setup

> Make Gmail, Drive, Docs, Sheets and Calendar available to your organization

> [!NOTE]
>
> Requires the **Integrations (MCP)** feature to be enabled for your organization. Ask your administrator if you can't see it.

With the Google Workspace integrations, assistants can search and read mail, files and calendars, and act in them on a member's behalf. Each Google product, such as Gmail, Google Drive, Google Docs, Google Sheets, Google Slides or Google Calendar, is a separate integration. As an Owner or Manager, you decide which ones your organization uses. Members then connect their own Google accounts.

## Enable the Google integrations

1. Open the profile menu in the sidebar and select **Workspace Settings**.
2. Under **Modules**, click **Integrations**.
3. Under **Public catalog**, turn on each Google product you want to offer.

Members now see the enabled products in the **Google Workspace** box on their **Integrations** page.

If a Google product you need isn't in the catalog, click **Can't find your integration? Request one**, or contact BlackMountain support.

## Register your own Google app

Some Google integrations need your organization's own OAuth app before anyone can connect. They show a **Setup required** badge, and members see **Waiting for admin setup**.

**1. Copy the redirect URI**

Next to the integration, click **Configure for this organization** and copy the **Redirect URI**.

**2. Create an OAuth client in Google Cloud**

In the Google Cloud console of your company, create an OAuth client for a web application. Add the 48° redirect URI as an authorized redirect URI. If a setup guide is linked in the dialog, follow it for the exact APIs and scopes.

**3. Enter the client in 48°**

Back in **Configure for this organization**, choose **This organization's client**, paste the **Client ID** and **Client secret**, and save.

Your organization's client is used only by your members. It doesn't affect other organizations. The integration then shows a **Customized** badge, and members can connect with one click.

> [!TIP]
>
> If your Google Workspace limits which third-party apps members may use, ask your Google Workspace administrator to allow your new OAuth app. Otherwise members may be blocked when they sign in.

## What members do

1. Click **Integrations** in the sidebar.
2. In the **Google Workspace** box, click **+** on a product and review what it can access.
3. Sign in with their Google account and grant access.

Each member connects each product separately, and only their own account. Access tokens are stored encrypted, for that member and organization only. Members then use Google tools by picking a toolset or an assistant that includes them.

## Recommendations

* Start with read access, such as searching Drive or reading the calendar, before offering tools that send mail or change files.
* Build a shared toolset, for example "Google research", with the tools most people need. See [Toolsets](https://docs.blackmountain.io/admin/integrations/toolsets.md).
* Tell members that content from Google is passed to the AI model, and that the model can act in Google on their behalf.

## Related

> [card] [Organization MCP servers](https://docs.blackmountain.io/admin/integrations/mcp-servers.md)
>
> Enable integrations and manage OAuth clients.

> [card] [Toolsets](https://docs.blackmountain.io/admin/integrations/toolsets.md)
>
> Bundle Google tools for your teams.

> [card] [Google Workspace for members](https://docs.blackmountain.io/integrations/google-workspace.md)
>
> How members connect and use Google.

> [card] [Microsoft 365 setup](https://docs.blackmountain.io/admin/integrations/microsoft-365.md)
>
> The same for Microsoft 365.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.