> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/classes/administrative-functions/approve-requests/custom-approval.md).
# Custom Approval
Custom Approval is the most flexible approval mode in equipme.
It is designed for companies that need approval logic beyond the predefined Simple Approval options. Instead of using one standard approval responsibility, Custom Approval works with a configured workflow in the equipme Automation module.
This makes it possible to reflect more specific approval rules and internal processes.
### When Custom Approval is needed
Not every approval process can be covered by one predefined responsibility.
Simple Approval works well when requests should be approved by a supervisor, department manager, location manager, or cost center manager.
Custom Approval is used when the approval process needs more specific logic. For example, approval may depend on the requested service, budget related rules, internal policies, or other conditions that are specific to the organization.
In these cases, the approval process needs to be modeled through a workflow.
### How Custom Approval works
When Custom Approval is active, incoming marketplace and self service requests are handled through a configured workflow.
The workflow defines what should happen when a new request is created, which approval steps are required, and how the request should continue after the approval decision.
This gives companies more flexibility than a predefined approval type. At the same time, it also means that the workflow must be configured correctly before Custom Approval can be used effectively.
### Custom Approval requires a workflow
Custom Approval is not just a switch that activates a ready made approval process.
It requires a workflow in the equipme Automation module. Without the required workflow, equipme does not have the custom approval logic needed to process new requests through this mode.
That is why Custom Approval should be planned carefully and set up with the right workflow configuration.
### What the workflow can control
A custom approval workflow can define approval behavior that is specific to your organization.
Depending on the configuration, it can determine which approval components are used, which approval steps are required, and when a request should be marked as approved.
This is useful when the approval process cannot be represented by one predefined approval responsibility alone.
### Approved and pending requests
Custom Approval still works with the approval status of order requests.
Requests that have not completed the required approval workflow remain pending and do not move forward in the standard ordering process.
Once the workflow approves the request, it can move into the approved order requests. From there, it can be processed and ordered.
### When Custom Approval is the right choice
Custom Approval is the right choice when your organization needs a tailored approval process.
It is useful when approval depends on rules or conditions that go beyond a single predefined approval responsibility.
If your approval process can be handled by supervisor, department manager, location manager, or cost center manager approval, Simple Approval is usually the easier setup.
If your approval process requires custom logic, Custom Approval gives you the flexibility to model it through a workflow.
### Custom Approval compared to other approval modes
equipme supports different approval modes for different levels of control.
Automatic Approval approves requests without a manual approval step.
Simple Approval adds a predefined approval step based on a selected responsibility.
Custom Approval uses workflows for more advanced approval processes.
If your company needs a tailored approval process, Custom Approval provides the flexibility to build it. Because this mode depends on workflow configuration, it should be planned and set up carefully.
---
# 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://hub.equipme.io/classes/administrative-functions/approve-requests/custom-approval.md?ask=&goal=
```
`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.