> For the complete documentation index, see [llms.txt](https://docs.m-xr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.m-xr.com/marso-measure/resources/multiple-machines.md).

# Multiple Machines

Follow this page if you are going to be using multiple machines.

Your M-XR Account can be used to access Marso Measure from multiple machines, however **only one can be activated for using Marso Measure at a time**.

The first time you log in to a new machine, you will be prompted to activate it, this will deactivate your previously active machine. The system settings will also need to be set per machine.

Your presets will then be available to you, across any machine. 

{% hint style="danger" %}
Activating another machine while a job is processing may cause unexpected behaviour on both machines. 
{% endhint %}

***

## Sharing Jobs

Jobs can be accessed from any machine logged into your account. 

Jobs can only be processed or exported if the raw photography is available at the same path as it was when the job was created, and the scratch directory is shared.


---

# 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.m-xr.com/marso-measure/resources/multiple-machines.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.