#Native access content location plus

You can’t enforce Context-Aware Access policies for mobile on third-party native apps (for example, Salesforce).Google Chat (you can apply access control policies to Google Chat using Hangouts Chat)

Google Meet (you can apply access control policies to Google Meet using Hangouts Meet) (Mobile devices are managed using Google Endpoint Management basic or advanced.)ĭrive and Docs (includes Sheets, Slides, and Forms) Context-Aware Access supportĮxpand section | Collapse all & go to top For example, you could create an access level that requires app access from devices that are company-owned, encrypted, and meet a minimum OS version. You can also combine more than one use case into a policy.

Restrict access to apps from outside the corporate network.

Allow access to Drive only if a user storage device is encrypted.

Allow access to apps only from company-issued devices.

You can use Context-Aware Access when you want to: The exception to this rule is SAML apps, which are evaluated on sign-in. Context-Aware Access provides additional granular and contextual controls for those users.Īccess for apps is evaluated continuously after access is granted. You can still set access policies, such as 2-Step Verification, for all members of an organizational unit or group. Using Context-Aware Access, you can create granular access control policies to apps based on attributes such as user identity, location, device security status, and IP address.Ĭontext-Aware Access gives you control over which apps a user can access based on their context, such as whether their device complies with your IT policy.

#Native access content location plus

Supported editions for this feature: Enterprise Education Standard and Education Plus Cloud Identity Premium.