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

<figure><img src="https://3006114282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXVOaWpJKxLZf1Tee9eCO%2Fuploads%2Fbw3vEl4iLGAjBkKk7PsL%2Fimage.png?alt=media&#x26;token=61f29d74-e375-48e1-98dd-7a59bcf7c68e" alt=""><figcaption></figcaption></figure>

**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: 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:

```
GET https://docs.guardianservice.io/technical-information/users/standard-registry-users-schemas-and-policies/policies/creating-a-policy-using-policy-configurator/policy-workflow-step-4.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
