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

# Policy Workflow Step 8

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.

At this point, we need to create a sub Policy Action process as a dependent workflow. We can always do this by adding a container block by clicking on the “Container” button in the top navigation bar.

We now configure this new container block through the “Tag”, Permissions, setting the Default Active (since this step must be initiated), and selecting the UI type (TABS in our case since we will have to fill in different types of information in different sections).

![](https://content.gitbook.com/content/EvaEsaNo09Ib5tjr1yj1/blobs/8IT9vIevQLiqem4tirpW/PW_image_13.png)

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

```
   // Create an InterfaceContainerBlock to group all pages accessible after registration is completed.
    {
      "blockType": "InterfaceContainerBlock",
      "tag": "installer_header",
      "defaultActive": true,
      "permissions": [
        "INSTALLER"
      ],
      "uiMetaData": {
        // In this example, INSTALLER would be able to access two tabs.
        "type": "tabs"
      },
```


---

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