> 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/creating-a-policy-through-policy-configurator/policy-workflow-step-17.md).

# Policy Workflow Step 17

Next, we need to add an information block to our policy to specify what happens if the application is rejected by clicking on the information button in the top navigation bar.

We then name the block through the tag, set permissions, activate by default such that rejection notifications are caught, stop the process if received, and then name the notification and define the message.

![](https://content.gitbook.com/content/EvaEsaNo09Ib5tjr1yj1/blobs/vMuhFduGQKddSdeIos2y/PW_image_23.png)

**Programmatically this workflow step looks like this:**

```
    // Block to display rejection info (i.e. the INSTALLER was not approved by StandardRegistry).
    {
      "tag": "installer_rejected",
      "blockType": "InformationBlock",
      "children": [],
      "uiMetaData": {
        "type": "text",
        "description": "Your application was rejected",
        "title": "Rejected"
      },
      "stopPropagation": true,
      "permissions": [
        "INSTALLER"
      ],
      "defaultActive": true
    }
  ]
},
```

This completes the installer steps of the policy.


---

# 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/creating-a-policy-through-policy-configurator/policy-workflow-step-17.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.