> 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/equipme/main-menu/approvals/automatic-approval.md).
# Automatic Approval
Automatic Approval is the most direct approval mode in equipme.
It allows marketplace and self service requests to move into the order request process without an additional manual approval step. When a user submits a request, equipme approves it automatically and shows it in the approved order requests.
This mode is useful for companies that want to keep the request process lightweight and do not need every request to be reviewed before it can be ordered.
### How Automatic Approval works
When Automatic Approval is active, new marketplace and self service requests are approved automatically.
Once Automatic Approval is saved, the selected setup applies to new incoming requests.
There is no approval task for a supervisor, department manager, location manager, cost center manager, or custom workflow. The request does not wait for a manual approval decision.
Instead, it appears directly in the approved order requests. From there, the request can be processed and ordered as usual.
### Approved does not mean ordered
Automatic Approval approves the request, but it does not automatically complete the order.
The request still appears in the Order requests area, where the responsible team can continue with the order process. This keeps the operational process clear: the request is approved first, then it can be ordered.
### Approved and pending requests
The Order requests area separates approved requests from requests that are still waiting for approval.
With Automatic Approval, new requests move directly into the approved area because no manual approval step is required.
Pending approvals are used when a request still needs a manual approval decision, for example with Simple Approval or Custom Approval.
### When Automatic Approval is the right choice
Automatic Approval is a good fit when an organization does not need an additional approval step for incoming requests.
It works well when requests should move quickly into the order process and do not need to be checked by a specific approver first.
This makes Automatic Approval the simplest setup for companies that want a direct path from request to order request.
### Automatic 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, such as supervisor, department manager, location manager, or cost center manager approval.
Custom Approval uses workflows for more advanced approval processes.
If your company wants requests to move directly into the approved order requests, Automatic Approval is the right setup. If requests need to be checked before they can be ordered, Simple Approval or Custom Approval may be a better fit.
---
# 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/equipme/main-menu/approvals/automatic-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.