> 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.md).

# Decentralized Guardian

Decentralized Guardian enables multiple independent Guardian instances to collaborate on the same policy workflow:

* Policies are published once and can then be imported and executed by external organizations.
* Each participant operates from their own environment while staying synchronized.
* It can be used through the Guardian UI (import remote policies, execute workflows through the Remote Policy tab, manage users and approvals visually) or through APIs (automate interactions and submissions, integrate Guardian into external systems, enable backend-driven workflows).

#### **Key terms** <a href="#key-terms" id="key-terms"></a>

<table data-header-hidden data-search="false"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Term</strong></td><td><strong>Meaning</strong></td></tr><tr><td>Main instance</td><td>The environment where the policy owner (the publishing standard registry) operates.</td></tr><tr><td>Dependent instance</td><td>A different environment whose users want to run the published policy.</td></tr><tr><td>Public policy</td><td>A policy published with Availability set to Public so other instances can request access.</td></tr><tr><td>Public link</td><td>The Hedera message timestamp that identifies the published policy. It is copied from the publishing instance and used to request access, generate keys, and import keys.</td></tr><tr><td>Remote policy</td><td>A policy that lives in another instance but is imported and executed as it was locally installed.</td></tr><tr><td>Remote user</td><td>A small copy (without credentials) of a user created in the dependent instance and installed to the main instance using a downloaded profile file. It carries the same Hedera identity and receives the decentralized access key.</td></tr><tr><td>Decentralized access key</td><td>A key generated by a user on the dependent instance for a specific policy message ID. It gives the remote user the rights to submit to the policy.</td></tr><tr><td>Remote Policy Requests</td><td>A queue of pending actions (for example, selecting a role or signing a document) the user must approve before the decentralized workflow continues.</td></tr></tbody></table>

<br>


---

# 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://guardian.hedera.com/docs/develop/guardian/workspace/decentralized-guardian.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.