> 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/simple-approval.md).
# Simple Approval
The Simple Approval workflow is a single-step process that allows you to approve an asset in Collibra.
## Roles
| Role | Task | Required |
| ---------------- | ----------------------------------- | -------- |
| Business Steward | | Yes |
| Stakeholder | | No |
## Workflow status transformations
Approved assets have the **Accepted** status.
## Start the workflow
The workflow starts when a community manager or business steward selects the **Simple Approval** action on an asset page. You can [edit](/workflows/out-of-the-box-workflows-walk-throughs/approval-process/approval-process-configuration.md#start) the label of this action on the workflow definition page.
## Vote for approval
The business stewards are prompted to vote for approval.
## Result
If the outcome of the vote is positive, the status of the asset is changed to **Accepted** and the stakeholders and the user who started the workflow are notified. If the outcome is negative, the user who started the workflow is notified.
---
# 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/simple-approval.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.