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

# Policy Workflow Step 7

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.

Again we need a Send step since we now have to submit the CSD01, the official IREC Participant Application form, as an official verifiable credential.

Note that compared to the previous “Send” step, the Data Type is now a VC since we are submitting the official form as a verifiable credential but not to Hedera. This form is stored on the Guardian for auditors to review in the trust chain.

![](https://content.gitbook.com/content/EvaEsaNo09Ib5tjr1yj1/blobs/u60cCh7jG3I12G4DDpXf/PW_image_12.png)

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

```
    // Finally save the VC document in the vc-documents DB table.
    {
      "tag": "Submission_of_CSD01_Documentation",
      "blockType": "sendToGuardianBlock",
      "dataType": "vc-documents",
      "entityType": "Installer",
      "uiMetaData": {}
    },
    // After the document has been created; the user can access the document with grids.
```


---

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