Certain data boundaries in Assured Workloads, such as Department of Defense (DoD) Impact Level 4 (IL4) and Impact Level 5 (IL5), include unsupported Google Workspace features that aren't turned off automatically. When possible, you must turn them off manually to help meet your compliance obligations.

<br />

## Before you begin

When you configure the settings in the Google Admin console, apply the
following guidelines:

- Confirm that your account has the required [administrator
  privileges](https://knowledge.workspace.google.com/admin/users/administrator-privilege-definitions)
  for each setting.

- Apply each restriction to your top-level organizational unit or to the child
  organizational units that contain users and data that are subject to your data
  boundary. Verify that configuration groups don't override these organizational
  unit settings.

## Turn off Google Takeout

Google Takeout lets authorized users export data to unmanaged environments. Turn
off Google Takeout for each service that supports it.

1. In the Admin console, go to **Menu \>
   Data \> Data import \& export \> Google
   Takeout**.
2. In **User access to Takeout for Google services** , configure the following settings:
   - For services without an individual administrative control, set **Data
     export permission** to **Don't allow for everyone** (or **Don't allow** for your organizational unit).
   - For services with an individual administrative control, set each service to **Don't allow**.

For instructions, see [Allow or block Google
Takeout](https://knowledge.workspace.google.com/admin/users/advanced/allow-or-block-google-takeout).

## Turn off Google Drive for desktop

Drive for desktop lets users synchronize files to local,
potentially unmanaged hard drives. Turn off Drive for
desktop for all users within your data boundary.

1. In the Admin console, go to **Menu \>
   Apps \> Google Workspace \> Drive and
   Docs \> Google Drive for desktop**.
2. In **Enable Drive for desktop** , clear the **Allow Google Drive for desktop
   in your organization** checkbox.

For instructions, see [If you don't allow Drive for
desktop](https://knowledge.workspace.google.com/admin/drive/set-up-drive-for-desktop-for-your-organization#block).

## Turn off offline access for Google Docs, Google Sheets, and Google Slides

To help prevent browser-based local caching, turn off offline access for
Docs, Sheets, and Slides and block
the Google Chrome extension.

To turn off offline access, complete the following:

1. In the Admin console, go to **Menu \>
   Apps \> Google Workspace \> Drive and
   Docs \> Features and Applications**.
2. In **Offline** , clear the **Allow users to enable offline access** checkbox for your organizational unit or for all users.

For instructions, see [Set up offline access to Docs,
Sheets, and
Slides](https://knowledge.workspace.google.com/admin/drive/set-up-offline-access-to-docs-sheets-and-slides).

To block the Google Chrome extension, complete the following:

1. In the Admin console, go to **Menu \> Devices** \> **Chrome \> Apps \& extensions \> Users \&
   browsers**.
2. Select or add the **Google Docs Offline** extension and set **Installation
   policy** to **Block** for your organizational unit.

## Turn off POP and IMAP access

Turn off POP and IMAP access so that users can't download data to unmanaged
email clients such as Apple Mail on personal devices.

1. In the Admin console, go to **Menu \>
   Apps \> Google Workspace \>
   Gmail \> End User Access**.
2. In **POP and IMAP access** , clear the **Enable POP access for all users** and **Enable IMAP access for all users** checkboxes for your organizational unit.
3. In **Google Workspace Sync** , clear the **Enable Google Workspace Sync for
   Microsoft Outlook for my users** checkbox for your organizational unit.

For instructions, see [Turn POP and IMAP access on or off for
users](https://knowledge.workspace.google.com/admin/sync/turn-pop-and-imap-on-or-off-for-users).

## Turn off consumer apps

Google Workspace lets users access additional consumer apps such as
YouTube, Google Photos, Google Maps, Google Play, and Blogger, which
aren't supported in data boundaries such as IL4 and IL5. To restrict user
access to unauthorized consumer services, turn off these services for your
organizational unit or for all users.

1. In the Admin console, go to **Menu \> Apps** \> **Additional Google services**.
2. Configure the following settings:
   - For **Access to additional services without individual control** , turn off access. For instructions, see [Manage access to services that aren't
     controlled individually](https://knowledge.workspace.google.com/admin/users/advanced/manage-access-to-services-that-arent-controlled-individually).
   - Under **Settings for all additional Google services** , set the service status to **Off** for each service that isn't authorized for your data boundary. For instructions, see [Turn
     on or off additional Google
     services](https://knowledge.workspace.google.com/admin/users/advanced/turn-on-or-off-additional-google-services).

## Turn off consumer-facing generative AI tools

Turn off access to consumer-facing generative AI tools such as Gemini
for Google Workspace apps, Workspace Intelligence, the standalone
Gemini app, and NotebookLM. Limit generative AI tools to
authorized, enterprise-governed apps that meet your specific boundary
requirements.

1. In the Admin console, go to **Menu \>
   Generative AI**.
2. Configure the following settings for your organizational unit or for all users:
   - To turn off Gemini for Google Workspace apps, go to **Gemini for Workspace \> Feature access** and set each service to **Off** . For instructions, see [Manage access to
     Gemini in
     Workspace](https://knowledge.workspace.google.com/admin/generative-ai/workspace-with-gemini/manage-access-to-gemini-features-in-workspace-services).
   - To turn off Workspace Intelligence, go to **Gemini for
     Workspace \> Workspace Intelligence** and set each data source to **Off** . For instructions, see [Control Workspace Intelligence
     for generative AI
     features](https://knowledge.workspace.google.com/admin/generative-ai/workspace-intelligence/control-workspace-intelligence).
   - To turn off the standalone Gemini app, go to **Gemini
     app \> Service status** and set the service status to **Off** . For instructions, see [Turn the Gemini app on or
     off](https://knowledge.workspace.google.com/admin/generative-ai/gemini-app/turn-the-gemini-app-on-or-off).
   - To turn off NotebookLM, go to **NotebookLM \> Service
     status** and set the service status to **Off**.

## Turn off Cloud Shell

Cloud Shell remains available in the Google Cloud console after
you apply a data boundary. However, Cloud Shell is bound to the user's
identity, not to the Google Cloud folder or project that's selected in the
Google Cloud console. This Cloud Shell instance launches from a
personal VM in a Google-owned project that's outside your organization. Turn
off Cloud Shell to stop users from launching an interactive shell
environment that's outside your organization.

> [!NOTE]
> **Note:** Cloud Shell isn't available in the [Jurisdictional
> console](https://docs.cloud.google.com/assured-workloads/docs/jurisdictional-console) or for Workforce Identity Federation users.

1. In the Admin console, go to **Menu \>
   Apps \> Additional Google services \> Google
   Cloud Platform \> Cloud Shell Settings**.
2. Turn off **Cloud Shell Access Settings** for your organizational unit or for all users.

For instructions, see [Disable Cloud Shell for managed user
accounts](https://docs.cloud.google.com/shell/docs/resetting-cloud-shell#disable-shell-for-managed-user-accounts).

If supported by your data boundary, consider using
[Cloud Workstations](https://docs.cloud.google.com/workstations/docs/overview.md.txt) for workloads that require
an interactive development environment.

You can also use [VPC Service Controls service
perimeters](https://docs.cloud.google.com/vpc-service-controls/docs/create-service-perimeters) to block
Cloud Shell from accessing resources inside your perimeter.

## Turn off OAuth 2.0 access for third-party apps

Turn off access to OAuth 2.0 so that users can't grant API access to
third-party apps without administrator approval.

1. In the Admin console, go to **Menu \>
   Security \> Access and data control \> API
   controls**.
2. In **Settings \> Unconfigured third-party apps** , select **Don't allow users to access any third-party apps** for your organizational unit or for all users.
3. Optional: To require administrator approval for internal apps, in **Settings \> Internal apps** , clear the **Trust internal,
   domain-owned apps** checkbox.

To configure access for specific trusted apps or for more instructions, see
[Control which third-party and internal apps access Google Workspace
data](https://knowledge.workspace.google.com/admin/apps/control-which-third-party-and-internal-apps-access-google-workspace-data).

## Turn off Google Workspace Marketplace apps, Drive add-ons, and Docs extensions

Restrict users from installing or authorizing
Marketplace apps,
Drive add-ons, or Docs extensions that aren't
approved by your organization.

1. In the Admin console, go to **Menu \>
   Apps \> Google Workspace Marketplace apps \>
   Settings**.
2. In **Manage access to apps** , select **Don't allow users to install and run
   apps from the Marketplace** for your organizational unit or for all users.

For instructions, see [Set whether users can install Marketplace
apps](https://knowledge.workspace.google.com/admin/apps/set-whether-users-can-install-marketplace-apps).

To set up an allowlist, see [Manage the Marketplace app
allowlist for your organization](https://knowledge.workspace.google.com/admin/apps/manage-the-marketplace-app-allowlist-for-your-organization).

## Enable Context-Aware Access

Context-Aware Access lets you control access to Google Workspace apps and
the Google Cloud console based on contextual factors. Configure
Context-Aware Access so that only authorized users can access
Google Workspace apps and the Google Cloud console from approved
geographic locations, networks, and devices.

1. In the Admin console or Google Cloud console, create an
   access level with rules that permit specific IP addresses, IP address
   ranges, geographic locations, and device policies. For instructions, see
   [Create Context-Aware Access
   levels](https://knowledge.workspace.google.com/admin/security/create-context-aware-access-levels)
   or [Create a basic access
   level](https://docs.cloud.google.com/access-context-manager/docs/create-basic-access-level).

2. In the Google Cloud console, create an access binding that binds a group to
   the access level that you created in step 1. For instructions, see [Set up
   Context-Aware Access](https://docs.cloud.google.com/access-context-manager/docs/securing-console-and-apis).

3. To enforce the access level on Google Workspace apps, assign the
   access level to your apps in the Admin console. For
   instructions, see [Assign Context-Aware Access levels to
   apps](https://knowledge.workspace.google.com/admin/security/assign-context-aware-access-levels-to-apps).

## Enforce multi-factor authentication with hardware security keys

To help mitigate phishing attacks, configure your organization to require
administrators to sign in with multi-factor authentication (MFA) using hardware
security keys such as Titan Security Key. In certain high-security data boundaries,
standard 2-step verification methods, such as SMS and one-time passwords (OTPs),
aren't sufficient.

1. Distribute hardware security keys to your administrators and users. For
   Titan Security Keys, see
   [Titan Security Key](https://store.google.com/product/titan_security_key_kit).

2. In the Admin console, go to **Menu \>
   Security \> Authentication \> 2-Step
   Verification** and select the **Allow users to turn on 2-Step Verification**
   checkbox for your administrator organizational unit or group. Set
   **Enforcement** to **Off** for a period of time to let users enroll their
   security keys. For instructions, see [Deploy 2-Step
   Verification](https://knowledge.workspace.google.com/admin/security/deploy-2-step-verification).

3. Enroll the security keys. Google Workspace administrators or users
   can enroll security keys. For enrollment instructions for administrators, see
   [Manage a user's security
   settings](https://knowledge.workspace.google.com/admin/security/manage-a-users-security-settings#securitykey).
   For enrollment instructions for users, see [Use a security key with your
   Google Account](https://support.google.com/accounts/answer/6103523).

4. In the Admin console, go to **Menu \>
   Security \> Authentication \> 2-Step
   Verification** and set **Enforcement** to **On** . Set **Methods** to **Only
   security key** . In **Security codes** , select **Don't allow users to generate
   security codes**.

5. To restrict passkeys to physical hardware security keys, go to
   **Menu \> Security \>
   Authentication \> Passwordless \> Passkeys
   restriction** and select **Hardware security keys only**.

## Restrict external collaboration for Drive and Gmail

To help prevent data leaks, restrict users from sharing Drive
files with external users, restrict shared drive access to internal users, and
turn off Gmail auto-forwarding to external addresses.

1. To restrict external sharing of Drive, complete the
   following:

   1. In the Admin console, go to **Menu \>
      Apps \> Google Workspace \> Drive and
      Docs \> Sharing settings**.
   2. In **Sharing options** , select **Off** to turn off external sharing. Clear the **Allow users in your organization to receive files from users or
      shared drives outside of your organization** checkbox. For instructions, see [Turn on or off external sharing of files and folders in
      Drive](https://knowledge.workspace.google.com/admin/drive/manage-external-sharing-for-your-organization#external_on_off).
2. To restrict shared drive access to internal users, complete the following:

   1. In the Admin console, go to **Menu \>
      Apps \> Google Workspace \> Drive and
      Docs \> Sharing settings**.
   2. In **Shared drive creation** , clear the **Allow members with manager
      access to override the settings below** and **Allow users outside your
      organization to access files in shared drives** checkboxes. For instructions, see [Set the default sharing settings for shared
      drives](https://knowledge.workspace.google.com/admin/drive/manage-shared-drives-as-an-admin#default).
   3. In **Sharing options \> Distributing content outside of your
      organization** , select **Only users in your organization** or **No
      one** . For instructions, see [Restrict who can move content to external
      shared
      drives](https://knowledge.workspace.google.com/admin/drive/manage-shared-drives-as-an-admin#control_sharing_for_your_organization).
3. To turn off Gmail auto-forwarding to external email addresses,
   complete the following:

   1. In the Admin console, go to **Menu \>
      Apps \> Google Workspace \>
      Gmail \> End User Access**.
   2. In **Automatic forwarding**, complete one of the following:

      - To turn off automatic forwarding completely, clear the **Allow users to
        automatically forward incoming email to another address** checkbox.
      - To allow automatic forwarding only within your organization, select the **Allow users to automatically forward incoming email to another
        address** checkbox and then select **Internal email addresses only**.

      For instructions, see [Let users automatically forward their own Gmail
      emails](https://knowledge.workspace.google.com/admin/gmail/let-users-automatically-forward-their-own-gmail-emails).

## What's next

- Review additional requirements for your [data
  boundary](https://docs.cloud.google.com/assured-workloads/docs/control-packages).

- Implement the [Deployment guidance for
  Gemini for Government](https://docs.cloud.google.com/docs/security/compliance/deploy-gemini-gov).