> For the complete documentation index, see [llms.txt](https://interfacing.gitbook.io/interfacing-help-files/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interfacing.gitbook.io/interfacing-help-files/document-control/managing-documentation-lifecycle/managing-an-approval-cycle.md).

# Managing an Approval Cycle

Approve finalized documentation to confirm it is ready for publication.

The **approval cycle** is the formal sign-off stage that confirms the documentation meets all required standards and is ready for publication.

{% hint style="warning" %}
Approval is **optional** and can be configured based on the needs of the organization. It is typically required for documentation involving compliance, legal requirements, or significant business impact.
{% endhint %}

***

## How to Configure & Manage an Approval Cycle

In **Phase 1**, governance cycle management is not yet available in the platform. All setup and administration must be performed in EPC.

For detailed instructions on managing approval cycles in EPC, refer to the following topics:

* [Approval Cycle](https://www.manula.com/manuals/interfacing-technologies/epc10-webapp/15.4/en/topic/12-1-5-5-approval)
* [Mass Approval](https://www.manula.com/manuals/interfacing-technologies/epc10-webapp/15.4/en/topic/12-1-9-8-11-mass-approval-configuration)
* [Approval Cycle by Category](https://www.manula.com/manuals/interfacing-technologies/epc10-webapp/15.4/en/topic/9-1-8-2-category-approval-workflow-conditional-rule)
* [Approval Cycle by Subtype](https://www.manula.com/manuals/interfacing-technologies/epc10-webapp/15.4/en/topic/9-1-8-1-approval-cycle-by-object-subtypes)

***

## Completing Approval Tasks

While you cannot manage approval cycles in the platform, you can complete approval tasks assigned to you. See the guides below to get started:

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="image"></th></tr></thead><tbody><tr><td><strong>Completing Approval Tasks</strong></td><td>Learn how to approve documentation items</td><td><a href="/interfacing-help-files/end-users/to-do/completing-tasks/completing-an-approval-task.md">Completing an Approval Task</a></td><td><a href="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2Fqajk87rc6tRhuZBAg7kr%2FIMS%20Icons%20(6).png?alt=media&amp;token=ad70c330-c87b-46cd-bc9b-fbdaf958fd0e">IMS Icons (6).png</a></td></tr><tr><td><strong>Managing Tasks in To Do</strong></td><td>View and organize your assigned tasks.</td><td><a href="/interfacing-help-files/end-users/to-do.md">Managing Your Tasks</a></td><td data-object-fit="cover"><a href="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FmanuRmFLiwvQFODiw6un%2FIMS-V16-NAV-Library-Icons-52.png?alt=media&amp;token=cdcc6cab-92cb-4f6c-b21c-e0aab133de45">to do icon.png</a></td></tr></tbody></table>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://interfacing.gitbook.io/interfacing-help-files/document-control/managing-documentation-lifecycle/managing-an-approval-cycle.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
