> For the complete documentation index, see [llms.txt](https://docs.ins-pi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ins-pi.com/designer/configuration/enhanced-configuration/approval-workflow.md).

# Approval Workflow

Overview of the approval workflow for adjusting diagrams in Designer.

The Diagram Approval Workflow supports a configurable 3-step approval process.

Diagram Approval Process

* To initiate the approval process, press the Submit for Assessment button in the Diagram form.
* Members of the Designer – Design Assessment Group will be notified and the Request Diagram Update button will be visible in the Diagram form.
* The My Approvals module will allow the Designer – Design Assessment Group members to take action e.g. Approve or Reject.
* After receiving the approval of all Designer – Design Assessment Group members, the Designer – Architecture Committee members will be notified.
* The My Approvals module will allow the Designer – Architecture Committee members to take action.
* After the final approval the diagram content will be read-only and can't be overwritten.

{% hint style="warning" %}
**Create a clone of an approved diagram**

Create a clone of an approved diagram if you want to make changes and re-submit for approval.
{% endhint %}


---

# 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://docs.ins-pi.com/designer/configuration/enhanced-configuration/approval-workflow.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.