> 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/automatic-approval.md).

# Automatic Approval

Automatic Approval is the simplest approval mode in equipme.

<figure><img src="/files/rvUWJ2bW1t9psiVA3d47" alt=""><figcaption></figcaption></figure>

It allows marketplace and self service requests to move directly 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 their request process lightweight and do not need every request to be manually approved before it can be ordered.

### How Automatic Approval works

When Automatic Approval is active, new marketplace and self service requests are approved automatically.

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 decision.

Instead, it appears directly in the approved order requests. From there, the request can be processed and ordered as usual.

### What this means for the order process

Automatic Approval keeps the path from request to order simple.

A user submits a request through the marketplace or self service area. equipme approves the request automatically. The request then becomes available in the approved order requests, where it can be handled by the responsible team.

This means that teams can continue working with approved requests directly, without first waiting for an approval decision.

### Approved and pending requests

The order request area separates requests by approval status.

Approved requests are ready to be processed. Pending approvals are requests that still need a decision before they can move forward.

With Automatic Approval, new requests move directly into the approved area because no manual approval is required.

### 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.

For example, it can be used when requests should move quickly into the order process, or when the company already has a simple internal request structure and does not require approval by a specific manager or approver.

It is the most direct approval setup in equipme.

### 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, such as approval by a supervisor, department manager, location manager, or cost center manager.

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/classes/administrative-functions/approve-requests/automatic-approval.md?ask=<question>&goal=<endgoal>
```

`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.