> For the complete documentation index, see [llms.txt](https://docs.fairmarkit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fairmarkit.com/buyers/requests-intake-buyers/approve-requests/set-up-request-approvals-admin.md).

# Set up request approvals (Admin)

As an Admin for your company, you will need to do the following to start using the request approvals process:

### Intake users <a href="#intakeusers" id="intakeusers"></a>

Users will need to have access to create intake requests.

### Create rules <a href="#createrules" id="createrules"></a>

For your company, you will create automation rules that define when requests should be routed to approvers. Only Admin users can set up and maintain rules.

{% hint style="info" %}
See: [Automation rules](/buyers/administration/automation-rules.md).
{% endhint %}

<figure><img src="https://docs.fairmarkit.com/content/intake/approvals/images/automation-rules-intake_thumb_0_0.png" alt=""><figcaption></figcaption></figure>

For each rule for intake, you'll set the following:

### Select a Trigger

Select *Requests* and *Before submitting* to create a rule for intake requests. This means the rules will run when you submit a request.

### Set an If Statement

* Set one or more conditions and/or condition groups that will trigger the rule. You can set a condition for the following request data:
* Location country
* Budget (must add a line for Budget minimum, Budget maximum, and Currency to set the budget)
* Single role

For example, you may run a rule for approval when the request *Location country* is *France*.

* Additionally, you can work with Fairmarkit to set up rules for your custom fields. For example, if you have a project that involved customer data, you could trigger a rule that requires approval from a cybersecurity team.

### Select approvers

Select one or more approvers and the number of days they have to approve the request.


---

# 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://docs.fairmarkit.com/buyers/requests-intake-buyers/approve-requests/set-up-request-approvals-admin.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.