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

# notificationBlock

This Block is used to generate Notifications.

<figure><img src="/files/gqdm5o6Rbc85I5B3XGyz" alt=""><figcaption></figcaption></figure>

## 1.1 Properties

| Property Name               | Description                                                                                           | Example                                                                      | Status |
| --------------------------- | ----------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- | ------ |
| Tag                         | Unique name for the logic block.                                                                      | notificationBlock                                                            |        |
| Permissions                 | Which entity has rights to interact at this part of the workflow.                                     | Standard Registry                                                            |        |
| Default Active              | Shows whether this block is active at this time and whether it needs to be shown.                     | Checked or Unchecked                                                         |        |
| Stop Propagation            | End processing here, don't pass control to the next block.                                            | Checked or Unchecked                                                         |        |
| On Errors                   | Called if the system error occurs in the Block                                                        | <p>- No action<br>- Retry</p>                                                |        |
| Title                       | .Notification title                                                                                   | Schema Creation                                                              |        |
| Type                        | type of notification                                                                                  | ERROR, SUCCESS, INFO, WARN                                                   |        |
| Message                     | Notification message                                                                                  | Schema is created                                                            |        |
| Link notification to policy | If checked : policy will be opened by clicking on notification                                        | Checked or Unchecked                                                         |        |
| User                        | If User == “ROLE”, users can setup appropriate role and also mark it as “Only for current user group” | ALL,CURRENT,POLICY\_OWNER,DOCUMENT\_OWNER,DOCUMENT\_ISSUER,GROUP\_OWNER,ROLE |        |


---

# 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/3.5.1/guardian/standard-registry/policies/policy-creation/introduction/notificationblock.md?ask=<question>&goal=<endgoal>
```

`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.