> For the complete documentation index, see [llms.txt](https://developer.collibra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.collibra.com/workflows/out-of-the-box-workflows-walk-throughs/approval-process.md).
# Approval Process
The Approval Process workflow allows you to approve an asset in Collibra. This is a more powerful version of the Simple Approval Process.
## Roles
| Role | Task | Required |
| --------------------- | ------------------------------------------------------------ | -------- |
| Subject Matter Expert | - Review definition
- Process comments
| Yes |
| Stakeholder | | Yes |
| Business Steward | | Yes |
## Workflow status transformations
| Status | Description |
| ------------ | ------------------------------------------ |
| Candidate | The initial status of an asset. |
| Under Review | The stakeholders are reviewing an asset. |
| Accepted | The stewards approved an asset definition. |
## Start the workflow
Select **Actions** → **Approval** on an asset page to start the workflow. You can [edit](/workflows/out-of-the-box-workflows-walk-throughs/approval-process/approval-process-configuration.md#start) the label of this button on the workflow definition page.
## Review the definition
Each subject matter expert reviews the attributes and relations of the asset as part of a [Voting Sub-Process](/workflows/out-of-the-box-workflows-walk-throughs/voting-sub-process.md)
The subject matter experts receive a task to either approve or reject the changes made to the asset.
The status of the asset changes to **Under Review** when the subject matter experts vote to approve. If the changes are rejected, the start user is notified to update the asset attributes and the process can be restarted.
## Provide comments
After the approval vote, each stakeholder reviews the asset and provides comments.
The stakeholders receive a task to provide comments.
## Process comments
Once comments are provided, each subject matter expert reviews the changes.
## Vote for approval
In this step of the process, the stewards vote for approval. The stewards receive a task to approve or reject the asset definition.
If you have set the **sendVotingActionEmails** to `true`, the stewards also receive an email notification to approve.
If approved, the asset status is set to **Accepted** and the comments are automatically attached to the asset. The start user and stakeholders are notified by mail of the completion of the process.
If rejected, the start user and stakeholders are notified by mail and the subject matter experts are prompted to review and vote on the new asset again.
---
# 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://developer.collibra.com/workflows/out-of-the-box-workflows-walk-throughs/approval-process.md?ask=&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.