> 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/3.5.1/guardian/standard-registry/policies/policy-creation/introduction/global-events-writer-block.md).
# Global Events Writer Block
Publishes document references to one or more global Hedera topics.
* Publishes reference/metadata only (does not create, update, or re-anchor the document).
* Can publish to multiple global topics.
* Publishes each time the block is executed in the policy flow.
* Lets you control publishing per topic/stream in the Writer UI:
* Active ON/OFF — ON = publish, OFF = skip.
* Hidden (optional) — stays in configuration but is hidden in UI.
* Document Type — set per-topic type (vc/json/csv/text/any).
## 1.1 Properties
| Property Name | Description | Example |
| -------------------------------------- | --------------------------------------------------------------------------------------------------------- | ----------------- |
| Default Active(in the block Meta Data) | controls the visibility in the runtime UI | Checked/Unchecked |
| Show Next button | enable to use this block inside a Step container | Checked/Unchecked |
| Global topics | the list of default topicIds that Admin adds to the block configuration | 0.0.7559767 |
| Active by default | controls the visibility | Checked/Unchecked |
| Document type | which documentType the Writer writes into the event message for this topic (VC / JSON / CSV / TEXT / ANY) | VC |
## 1.2 API
* Uses the standard policy blocks API (setData), same as other blocks.
* Reader/Writer don’t introduce a new API — they only define their own payload format and supported operation values.
```
Writer payload (Update streams):
{
"operation": "Update",
"streams": [
{ "topicId": "0.0.45345345", "documentType": "vc", "active": true }
]
}
```
---
# 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/3.5.1/guardian/standard-registry/policies/policy-creation/introduction/global-events-writer-block.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.
