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

# Policy Workflow Step 4

Next, we want to add another step to our policy action. To do this we again go back to the Policy Action itself by clicking on the “init\_installer\_steps” Policy Action icon on the left.

This time we need to deal with the new approval document that was sent, so we add an “information” step as a block by clicking on the “Information” icon in the top navigation bar.

Again we are naming the “Tag” to better identify this policy action step. In this case, we want to inform the user of the status of the approval in the previous workflow step.

Next, we are setting the Permission to “Installer”.

Since approval is mandatory, the step must be active by default.

Also, the next step cannot occur before approval is given. Therefore we set “Stop Propagation”.

For the approval UI, we then specify what Type it is from the drop-down. In our case, a simple TEXT UI is enough to display the approval status.

We then finish by giving the UI a Title and Description.

![](https://content.gitbook.com/content/EvaEsaNo09Ib5tjr1yj1/blobs/6EKBIw9Dtg4wTxu56iTI/PW_image_9.png)

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

```
   // Notify the user after submitting the request for approval.
    {
      //"InformationBlock" - block type which can display a notification or a progress bar.
      "blockType": "InformationBlock",
      "tag": "wait_fo_approve",
      "children": [],
      "uiMetaData": {
        //"type" - notification type, possible values:
        //  "text" - textual message.
        //  "loader" - progress bar.
        "type": "text",
        // Set title and description for the page, only if the "type" is "text".
        "title": "Waiting for approval",
        "description": "Waiting for approval"
      },
      "permissions": [
        "INSTALLER"
      ],
      // Do not pass control to the next block after displaying the message as need to wait for Standard Registry approval.
      "stopPropagation": true,
      "defaultActive": 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/creating-a-policy-through-policy-configurator/policy-workflow-step-4.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.