> For the complete documentation index, see [llms.txt](https://techresources.gitbook.io/microsoft-word-tips-and-tricks/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://techresources.gitbook.io/microsoft-word-tips-and-tricks/viewing-word-comments-in-google-drive.md).

# Viewing Word Comments in Google Drive

**Word Comments** and **Tracked Changes** are features that work best in **Microsoft Word**. To prevent problems from occurring, download and install the [**Microsoft 365 Apps**](/microsoft-word-tips-and-tricks/downloading-and-installing-microsoft-365-apps-for-free.md) (free of charge) on your personal computer. Then use **Microsoft Word** to work with **Comments** and **Tracked Changes. Note: Microsoft Word** can also be found on all JAMS Lab and CCL computers. 

To view **Word Comments** and **Tracked Changes** in **Google Drive**, you'll need enable this feature in your **Account Settings**. 

1. Open **Chrome** and log in to your **Google Account**. **Note**: You must use the **Chrome** browser to view **Word Comments** in **Google Drive**. This feature may not work in other browsers.
2. After logging in, click the **Google apps** button (square group of dots) in the upper-right corner of the browser window. In the fly-out menu, select **Drive**. 
3. In **Google Drive**, click the **Settings** button (gear icon.) In the fly-out menu, choose **Settings**.
4. In the **Settings** window, go to the **Uploads** section. Select the **checkbox** next to **Convert uploads to Google Docs editor format**. Navigate back to **Google Drive**.
5. After uploading a **Word Document** to **Google Drive**, you should be able to interact with **Comments** and **Tracked Changes**.
6. If necessary, [download the file as a **Word Document**](/microsoft-word-tips-and-tricks/saving-a-google-doc-as-a-word-file.md) when finished. 


---

# 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://techresources.gitbook.io/microsoft-word-tips-and-tricks/viewing-word-comments-in-google-drive.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.