> For the complete documentation index, see [llms.txt](https://docs.zeedrive.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zeedrive.com/feature-guide/supports-office-co-authoring-and-autosave.md). # Supports Office Co-Authoring And AutoSave space.vars.PRODUCT\_NAME offers two options for opening Microsoft Office documents; either in [exclusive editing mode](/feature-guide/locks-office-documents-for-exclusive-editing.md) which is similar to the behaviour when working from a traditional on-premises file server, or, opening the document for co-authoring. When opened for co-authoring, advanced Office features such as collaborative editing and AutoSave are available.

When an Office document is opened for co-authoring, the AutoSave slider is set to the On position

When editing documents with co-authoring enabled, you can see the edits of other users *live* in your document:
The default behaviour when opening an Office document from Windows File Explorer (either exclusive or for co-authoring) can be [changed by the Zee Drive subscription administrator](/administration-guide/co-authoring-and-exclusive-editing.md). Users can also open Office documents for co-authoring via the File Explorer context menu:
{% hint style="info" %} Check the [user guide](/user-guide/co-authoring-and-autosave.md) for more information on co-authoring {% endhint %} --- # 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.zeedrive.com/feature-guide/supports-office-co-authoring-and-autosave.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.