> For the complete documentation index, see [llms.txt](https://docs.trymito.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trymito.io/how-to-1/share-mito-spreadsheets-across-users.md).
# Share Mito Spreadsheets Across Users
This documentation explains how to set an environment variable to share Mito spreadsheets using shared drives.
## Context
Each Mito spreadsheet has a unique ID called the `analysis_to_replay` ID. When you create a new Mito spreadsheet, a new analysis\_to\_replay ID is automatically created. It will look like this.
That ID is used for a couple different things:
1. When you edit a Mito spreadsheet, Mito saves metadata about your analysis in the `.mito` folder on your computer.
2. When you rerun a `mitosheet.sheet()` call with an analysis\_to\_replay parameter, Mito looks up the metadata for that analysis saved in the `.mito` folder and uses it to repopulate the Mito spreadsheet with your analysis. That means, *if you want to load an existing Mito spreadsheet, you need to have the metadata file in your .mito folder.*
## Sharing Mito Spreadsheets through a Shared Drive
If you want to share your Mito spreadsheet with your team, they must have access to the metadata file for the analysis. To do that, set the following environment variables in your Jupyter server to change the location of your Mito to a shared drive.
```
'MITO_CONFIG_HOME_FOLDER' = 'path/to/shared/drive'
```
You can save this environment variable in your virtual environment for persistent use.
---
# 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.trymito.io/how-to-1/share-mito-spreadsheets-across-users.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.
