> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/saas-data-monitoring/inventory/inventory-assets/google-drive-assets/google-gemini-gems.md).
# Google Gemini Gems
DoControl recognizes Gemini Gems as files within Google Drive and includes them in the asset inventory. This means your organization can identify, monitor, and govern Gems using the same workflows and policies applied to any other Google Drive asset.
### **What is a Gemini Gem?**
A Gemini Gem is a custom AI assistant created in Google Gemini. Because Gems are stored as files in Google Drive, they are treated as **assets** in DoControl and subject to the same visibility, event monitoring, and remediation capabilities.
> **Note:** Sharing a Gem may also imply access to the sensitive files connected to it, making governance of Gems especially important.
### **Visibility and inventory**
Gems appear in the **Google Drive asset inventory** alongside other assets. For each Gem, you can view:
* Sharing status — whether the Gem is shared internally or externally
* Sensitivity and exposure level
* Who has access and what they're doing with it
* When it was last modified
This gives teams immediate visibility into a previously unmonitored surface area.
### **Gem sharing events**
When a Gem is shared externally, DoControl captures a **user access change** event with `doc_type = gem`. This allows teams to:
* Detect when an internal user shares a Gem externally
* Understand when and how Gems are being exposed
* Maintain an audit trail of all Gem-related activity
All event types apply to Gems — view, access, edit, share, download, and more.
### **Remediation**
From the asset inventory, you can remediate Gems directly using the same inventory actions available for other Google Drive assets, including:
* Removing public or external sharing
* Adjusting access permissions
* Revoking specific collaborators
### **Automating responses to Gem sharing**
Because Gem sharing events are captured in DoControl, you can build workflows to automate your response at scale. For example, when a user shares a Gem externally, a workflow can:
1. Retrieve the user's identity and associated context
2. Analyze the activity for risk signals — such as a personal email address or signs of data exfiltration
3. If no risk is detected, notify SecOps
4. If a risk is identified, remove the external collaborator from the Gem and notify both the user and SecOps
This enforces consistent policy around AI asset sharing without requiring manual intervention.
---
# 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.docontrol.io/docontrol-user-guide/saas-data-monitoring/inventory/inventory-assets/google-drive-assets/google-gemini-gems.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.