> For the complete documentation index, see [llms.txt](https://guardian.hedera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guardian.hedera.com/docs/develop/guardian/workspace/decentralized-guardian/connecting-your-mgs-instance-with-verra/before-you-begin.md).
# Before You Begin
To run a policy across two instances you need at least four users, as described below. Verra operates in this case as the main instance, while other instances operate as the dependent instances.
| **User** | **Where** | **Purpose** |
| --------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------ |
| Main standard registry | Main instance | Owns and publishes the policy. |
| Remote user | Main instance | A local copy of the user created in a dependent instance. Holds the imported decentralized access key. |
| Dependent standard registry | Dependent instance | Approves the imported remote policy so local users can run it. |
| Dependent user | Dependent instance | The project developer or VVB who requests access, registers for the policy, submits projects, etc. to the remote policy. |
You also need a policy that is ready to publish, or already published. This guide uses the VM0047 methodology published on the Verra’s UAT environment using the Hedera testnet (public link: 1785511586.942929104).
*Figure 1. The Verra Portal. VM0047 in the first row is installed but not published yet.*
{% hint style="info" %}
Tip: Take note of the public link and, later, of the decentralized access key as you work through the setup. Both values are needed again at later steps.
{% 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://guardian.hedera.com/docs/develop/guardian/workspace/decentralized-guardian/connecting-your-mgs-instance-with-verra/before-you-begin.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.