> For the complete documentation index, see [llms.txt](https://guide.allibee.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.allibee.ai/en/clm/progress-stage/final-review-approval.md).

# \[Admin] Final Review Approval

After initial approval by the legal team member, the final review must pass to the Administrator to complete the legal review process.

{% hint style="warning" %}
Final review approval is available only to members with Admin permissions.
{% endhint %}

### Checking Contracts That Require Final Approval

There are two ways to check contracts that need final approval.

{% @arcade/embed flowId="lFUhPFeaTU5imliYblWt" url="<https://app.arcade.software/share/lFUhPFeaTU5imliYblWt>" %}

1. Via email

* Once the legal review is complete, a final review request email will be sent.
* Click \[View Contract] in the email to begin reviewing the contract.

2. In the Contract List Menu

* Contracts under ‘Legal Approval In Progress’ status can be found in Contract List > Review tab.

{% hint style="info" %}
To view all contracts in your workspace, disable the \[View only my contracts] toggle \
(only available members with Admin permissions).
{% endhint %}

***

### Approving or Rejecting the Final Review

{% @arcade/embed flowId="HSldhCrazX1of4y9Mv9G" url="<https://app.arcade.software/share/HSldhCrazX1of4y9Mv9G>" %}

1. Approving the Final Review

* If the contract is ready for signing, click Approve Final Review to approve it.

{% hint style="danger" %}
Once final approval is granted, the contract can no longer be edited.
{% endhint %}

2. Rejecting the Final Review

* If the contract needs revisions, click \[Reject Final Review] to send it back for modifications.

{% hint style="info" %}
After final review approval, the contract owner can proceed with the contract through electronic approval and e-signature.
{% 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://guide.allibee.ai/en/clm/progress-stage/final-review-approval.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.