Create Context-Aware Access policies

Supported editions for this feature: Frontline Standard and Frontline Plus; Enterprise Standard and Enterprise Plus; Education Standard and Education Plus; Enterprise Essentials Plus; Cloud Identity Premium. Compare your edition

After you create context conditions, you can enforce them by building an access policy. You can control access by user identity, device security status, IP address, and geographical location. You can also control access for apps that attempt to access Google Workspace apps and Google Workspace data through APIs.

Note: Context conditions were previously referred to as access levels in the Google Admin console.

When you configure a policy...

  • By default, selecting a policy sets it to Monitor mode. Monitor mode lets you simulate the effects of enforcing a policy without blocking user access. For details, go to Deploy Context-Aware Access.
  • Users get access to the app when they meet the requirements in at least one of the context conditions you select, which acts as a logical OR. If you want users to meet the requirements in multiple context conditions as a logical AND, create a context condition that includes multiple attributes. To assign more than 10 context conditions to a policy, use nested context conditions.
  • For mobile apps, if you use integrated Gmail, you can give or deny access to Gmail, Google Chat, and Google Meet all at once. If you implement Chat and Meet as separate apps outside of integrated Gmail, you must give or deny access to those apps separately.
  • Some apps need API access to other apps to work correctly. For example, Gmail needs access to the Google Calendar, Drive, and Meet APIs. Google Calendar needs the Tasks API, and Gemini needs the Gmail API. When creating a policy, take these dependencies into account to ensure apps work as intended.
  • Applying a policy to an app doesn't automatically block its API. If you block an app, such as Gmail, users can't sign in directly to the app. However, other apps or third-party clients might still access the app's data through its API, such as email messages through the Gmail API. To prevent all access through APIs, you must also apply context conditions to the app's API.

Create and enforce a policy

Before you begin: If needed, learn how to apply the setting to a department or group.

  1. In the Google Admin console, go to Menu and then Security and then Access and data control and then Context-Aware Access.

    Requires the Data security access level and rule management privileges and the Admin API groups and users read privileges.

  2. In the Policies section, click Create new policy.
  3. For Policy status, at the top of the page, choose an option:
    • Monitor—Assess a policy's impact on users before implementing the policy.
    • Active—Enforce the policy immediately.
  4. For User conditions, click Edit. (Optional) To apply the setting only to some users, at the side, select an organizational unit (often used for departments) or configuration group (advanced).

    Group settings override organizational units. Learn more

  5. Click Save.
  6. For Context conditions, click Edit.
  7. Check the boxes next to the context conditions from your library list that you want to apply and then click Save.
  8. For Apps, click Edit.
  9. Select the target apps that you want to control access to and then click Save.
  10. For Action, click Edit and choose which action to enforce when selected context conditions aren't met:
    • Warn—Context conditions are enforced, and the user is warned when accessing selected apps.
    • Block—Context conditions are enforced.
  11. Click Save.
  12. For Policy settings, click Edit.
  13. We recommend that you check the Block users from accessing Google desktop and mobile apps if context conditions aren't met box to apply the requirements to users of native desktop, Android, iOS, and web apps. For details about expected app behaviors, go to App behavior based on policy settings on this page.
  14. (Optional) To block apps from attempting to access Google Workspace data through public APIs, check the Block other apps from accessing the selected apps via APIs, if context conditions aren't met box.
  15. (Optional) To exempt trusted apps from being blocked through APIs, check the Exempt allowlisted apps so they can always access APIs for specific Google services, regardless of context conditions box.
    • To review the apps excluded from API blocks, click View exempted apps.
    • You can only exempt apps from API access blocks if they are already configured as trusted in App Access Control. To verify or trust new apps, click Manage apps.
  16. Click Save.
  17. For What will this policy do?, review the policy summary generated by your selections. To update any section, click Edit next to it.
  18. Click Create policy.

App support for Context-Aware Access policies

Google app Block mode support Warn mode support
Calendar ✔ ✔
Chat ✔ ✔
Drive ✔ ✔
Gmail ✔ ✔
Google Docs (includes Google Sheets and Google Slides) ✔ ✔
Google Keep ✔ ✔
Google Tasks ✔ ✔
Admin console ✔ Web only
Gemini ✔ Web only
Google Sites ✔ Web only
Meet ✔ Web and Android only
Gemini Notebook ✔ Web only
Data Studio ✔
Gemini Enterprise ✔
Google Classroom ✔
Google Cloud ✔
Google Cloud Search ✔
Google for Business ✔
Google Play Console ✔
Google Vault ✔

App behavior based on policy settings

The following table summarizes app behavior based on whether you check the Block users from accessing Google desktop and mobile apps if context conditions aren't met box and whether you deploy endpoint verification.

Key terms for this table:

  • Policy applied—Access is granted based on the context conditions that you set up in the Context-Aware Access configuration.
  • Access allowed—Context-Aware Access is not applied, and all access is allowed.
  • Access blocked—Access is blocked because Context-Aware Access isn't configured, or you don't have endpoint verification turned on.

Context condition

Context-Aware Access enabled

Allow or block native and web access

Mobile

Desktop

Mobile native

Mobile web

Desktop web

Desktop native

Endpoint verification deployed?

Context condition with only IP/Geo attributes

Block users from accessing Google desktop and mobile apps if context conditions aren't met box is checked*

Policy applied

Policy applied

Not required

Block users from accessing Google desktop and mobile apps if context conditions aren't met box is not checked

Access allowed

Policy applied

Policy applied

Access allowed

Not required

Context condition with device attributes

Block users from accessing Google desktop and mobile apps if context conditions aren't met box is checked*

Policy applied

Policy applied

Yes

Block users from accessing Google desktop and mobile apps if context conditions aren't met box is checked

Policy applied

Access blocked

No

Block users from accessing Google desktop and mobile apps if context conditions aren't met box is not checked

Access allowed

Policy applied

Policy applied

Access allowed

Yes

Block users from accessing Google desktop and mobile apps if context conditions aren't met box is not checked Access allowed Policy applied Access blocked Access allowed No

* Recommended setting

Notes:

  • The Gemini mobile app has its own built-in system for blocking content. When a query violates a policy, instead of a standard system warning, the app shows an "access denied" message.
    • Simple queries, such as greetings, don't trigger this message because they don't require an access evaluation.
    • If a simple query follows a blocked complex request, the app might reprocess the previous prompt. This can result in another "access denied" warning or an unintended response to the blocked query.
    • When under restrictions, Gemini responds to simple queries using only its core system. Access to Google Workspace data, such as Gmail or Google Drive, remains severely restricted.
  • When Block other apps from accessing the selected apps via APIs, if context conditions aren't met is turned on for Google Calendar or Drive, the Gemini app is also blocked. This occurs because the Gemini app needs access to Google Calendar and Drive scopes, not data. To turn on this setting, in the Policy settings section, check the Block other apps from accessing the selected apps via APIs, if context conditions aren't met box.
  • Context-Aware Access policies for Gemini Enterprise apply only to web and mobile apps, not direct calls to the Discovery Engine API. To enforce access policies through the API, go to Set up Context-Aware Access.

Review or modify assigned policies

This setting applies changes locally and does not display inherited assignments.

  1. In the Google Admin console, go to Menu and then Security and then Access and data control and then Context-Aware Access.

    Requires the Data security access level and rule management privileges and the Admin API groups and users read privileges.

  2. For Policies, click View all policies.
  3. Find your policy in the list, point to its row, and click Edit policy.
  4. To change the enforcement state, set Policy status to Monitor or Active.
  5. To change specific components, click Edit next to any of the following sections:
    • User conditions—Update your targeted organizational units or configuration groups.
    • Context conditions—Update which context conditions apply to this policy.
    • Apps—Update your protected target apps.
    • Action—Verify whether the policy is set to Block or Warn users when context conditions aren't met:
      • Block—Blocks access to the app.
      • Warn—Allows access to the app and sends the user a warning notification in the app. If they continue to use the app, they get a new notification every 48 hours. If different apps are protected with the same context conditions, only the first access attempt triggers a notification to reduce the number of notifications.
    • Policy settings—Verify whether the policy blocks desktop and mobile apps, blocks API access, or exempts trusted apps on the allowlist.
  6. After you change a component, click Save.
  7. In the What will this policy do? section, review the impact that your Context-Aware Access policies will have on your organization and its apps.
  8. Click Save.

View logged events for a policy

You can view log reports to track whether your assigned policies are working properly and controlling user access to apps. Policies set to either Monitor or Active mode generate events that are saved in the Context-Aware Access log events.

  1. In the Google Admin console, go to Menu and then Security and then Access and data control and then Context-Aware Access.

    Requires the Data security access level and rule management privileges and the Admin API groups and users read privileges.

  2. For Policies, click View all policies.
  3. Point to an app and click Actions and then View logs.
  4. On the side, click the link to the security investigation tool to automatically run a search for Context-Aware Access log events for the selected app.

The search results include the following information:

  • Users who would have been blocked if the policy was enforced appear in the Access denied (Monitor mode) events list.
  • Blocked users appear in the Actor column.
  • Policies that were applied, satisfied when access conditions were met, and unsatisfied when access conditions weren't met.

For more details, go to Context-Aware Access log events.