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
As an administrator, you can create Context-Aware Access policies for all internal and third-party OAuth apps that use "Sign in with Google." You can control access by user identity, device security status, IP address, and geographical location.
Note: Context conditions were previously referred to as access levels in the Google Admin console.
Context-Aware Access policies are enforced only when a user signs in through Google. After a user is successfully signed in, the third-party app controls the session. Therefore, if the user's context conditions change later, Context-Aware Access won't block the active session. The user would only be checked against the Context-Aware Access policy again during their next sign-in attempt.
When you create policies for OAuth apps
You can use policies to control whether users are granted access to internal and third-party OAuth apps. When a policy includes multiple context conditions, users are granted access if they meet the conditions of any of the selected context conditions using a logical OR. If you want users to meet the requirements of more than one context condition using a logical AND, you must create a single context condition that contains multiple attributes. To control access to more than 10 context conditions for an app, you can use nested context conditions.
Create a policy for third-party apps
Before you begin: If needed, learn how to apply the setting to a department or group.
-
In the Google Admin console, go to Menu
Security
Access and data control
Context-Aware Access.
Requires the Data security access level and rule management privileges and the Admin API groups and users read privileges.
- For General settings, click View settings.
- (Optional) To apply the setting only to some users, at the side, select an organizational unit (often used for departments).
- In the Policy for OAuth apps section, click Edit
.
- Choose the context conditions you want to apply to internal and third-party
OAuth apps using Google sign-in:
- Active mode—Blocks access to apps that don't meet the selected context condition
- Monitor mode—Logs access attempts that don't meet any of the selected context conditions, but doesn't block access
-
Click Save. Or, you might click Override for an organizational unit.
To later restore the inherited value, click Inherit (or Unset for a group).
In the Policy for OAuth apps section, you can review the number of context conditions applied to all internal and third-party OAuth apps in both Monitor mode and Active mode.