> For the complete documentation index, see [llms.txt](https://docs.material.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.material.security/workspace-protections/google-drive-security/google-workspace-sharing-policies.md).
# Google Workspace sharing policies
See how Material uses your Google Workspace sharing policies to detect truly public files.
Material uses your Google Workspace organizational unit and group Drive sharing policies to decide whether a file is truly shared externally or publicly. When your policies keep a file login-restricted, Material no longer flags it as publicly shared, so you don't spend time on file issues for links that can't be opened from outside your organization.
{% hint style="info" %}
Material applies your sharing policies only after you grant the sharing-policy permission. Until you grant it, your file detections work exactly as they do today.
{% endhint %}
## How Material resolves your sharing policies
For each file, Material determines the effective sharing policy the same way Google Workspace does, then uses it when evaluating your file detections.
| File location | Policy Material applies |
| ------------- | --------------------------------------------------- |
| My Drive | The file owner's organizational unit policy |
| Shared drive | The organizational unit the shared drive belongs to |
Groups can override organizational unit policies. When a user belongs to a group that has its own sharing policy, Material applies that policy.
{% hint style="info" %}
If Material can't interpret a sharing policy, it falls back to its standard detection behavior for that file.
{% endhint %}
## Grant the sharing-policy permission
Material needs a read-only permission to read your Google Workspace Drive sharing policies. Until you grant it, Material can't tell which files your policies keep login-restricted.
To grant the permission, click **Action Required: Grant additional permissions** in the bottom left, then click **Review permissions** and follow the prompts.
{% hint style="warning" %}
Until you grant the permission, your file detections behave as before and may flag files as publicly shared even when your sharing policies keep them login-restricted.
New customers grant this permission during onboarding.
{% endhint %}
## When a sharing policy changes
When you change a Drive sharing policy in Google Workspace, Material updates the files that policy affects and automatically opens or closes file issues to match. Stale issues clear on their own, and new issues appear where a policy now exposes a file. This can take up to a day or two to fully reflect.
## Viewing policy details on a file
When a sharing policy applies to a file, Material shows the relevant policy information on the file's detail page, so you can see why a file was or wasn't flagged as externally shared.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.material.security/workspace-protections/google-drive-security/google-workspace-sharing-policies.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
