> For the complete documentation index, see [llms.txt](https://docs.skyone.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skyone.cloud/english/admin/google.md).

# Google

In **Google**, you set the workspace's Google Workspace integration policy and see which users have connected their Google accounts.

Here are the available features:

### Enable Google Workspace <a href="#enable-google-workspace" id="enable-google-workspace"></a>

Turn on **Enable Google Workspace** to let users connect their Google accounts to Astro.

> When this option is off, no one can connect a Google account, regardless of the products selected.

### Choose allowed products <a href="#choose-allowed-products" id="choose-allowed-products"></a>

Under **Allowed products**, select the Google products Astro can access:

* **Gmail**
* **Drive**
* **Docs**
* **Sheets**
* **Slides**
* **Calendar**
* **Chat**
* **Contacts**

### Control actions <a href="#control-actions" id="control-actions"></a>

Beyond read access, you can allow specific actions:

* **Allow sending email:** lets Astro send email through Gmail on the user's behalf.
* **Allow Calendar changes:** lets Astro create or change events on the user's Calendar.

### Restrict the domain <a href="#restrict-the-domain" id="restrict-the-domain"></a>

In the **Allowed domain** field, enter the domain of the Google accounts you accept (e.g., **yourcompany.com**). This way, only company accounts can be connected.

### Review connected users <a href="#review-connected-users" id="review-connected-users"></a>

The **Connected users** section lists who has connected a Google account, with the following information:

* **Name** and **Email:** who the user is.
* **Products:** Google products the user has authorized.
* **Connected on:** connection date.

To remove a user's access, click **Disconnect** in their row.


---

# 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.skyone.cloud/english/admin/google.md?ask=<question>&goal=<user_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.
