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

# Policy Workflow Step 1

Navigate to the top row of the interface, and click on the “Step” button which creates the 1st policy action – called Block2 – in the policy workflow, we just created.

You can edit the policy action name and the UI will automatically adjust the graphical representation of the policy action on the left side to “init\_installer\_steps”.

We then select the “Permissions” for this new Policy Action.

And then the UI “Type” as “Blank”.

We then select “Default Active” as true since this policy action must always occur at the beginning of the policy.

Now we have a Policy Action defined, however, without any specific actions

![](https://content.gitbook.com/content/EvaEsaNo09Ib5tjr1yj1/blobs/Vu1us0W4JjqTkJcCdLND/PW_image_6.png)

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

```
// After the role is selected the corresponding branch in the policy will become accessible for the user.
{
  //"InterfaceStepBlock" - similar to the InterfaceContainerBlock, with the difference that it can only render a single child element.
  //Rendered component is determined by the current step.
  //An event on a component automatically passes control to the next component.
  "blockType": "InterfaceStepBlock",
  "defaultActive": true,
  "tag": "init_installer_steps",
  "permissions": [
    //This block is only accessible to users with the INSTALLER role.
    "INSTALLER"
  ],
  "uiMetaData": {
    //Currently there is only one type - "blank".
    //Only 1 active block is rendered.
    "type": "blank"
  },
```


---

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