> ## Documentation Index
> Fetch the complete documentation index at: https://docs.assetinfinity.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Requisition types

> The kinds of purchase request people choose between, what each may ask for, whether it needs a department or leaves prices to the buyer, and which roles are offered it.

This screen sets up the kinds of purchase request people choose between when they raise a [requisition](https://docs.assetinfinity.ai/commercial/purchase-requests.md) — "New booking", "Stores replenishment", "IT equipment" — and what each may ask for. The type a request is raised as decides what its lines offer under **What it is**. Open it from **Administration → Requisition types**.

> [!NOTE]
>
> If you don't see this in your navigation, your administrator can switch the module on under **Administration → Modules** (it is part of **Purchasing**), or it may not be included in your plan.

Types are optional. With none here, a request is raised without one and any line may ask for anything, exactly as before. Once there are types, the requisition form asks **Request type** first, offering the types your roles are offered; a person may still leave it empty and raise a request of no particular type.

**Who can change this.** Types are added and changed by people whose role includes **Add configuration entries** and **Edit configuration entries**.

## The list

The stat strip counts the **types**. **New type** opens the form, and clicking a row edits that type.

| Column | What it shows |
| - | - |
| **Type** | The type's name, tagged **Not offered** where it has been switched off |
| **Applies to** | What a request of this type may ask for: **A part**, **A service**, **An asset, by its category** and **Something else** |
| **Visible to** | The roles it is offered to, or **Every role** |
| (tags) | **Department required** and **Prices left to the buyer**, where they apply |
| **Requests** | How many requests have been raised as this type |

## Adding or changing a type

| Section | Field | What it means | Notes |
| - | - | - | - |
| Identity | **Request type name** | What appears in the type list when somebody raises a request | Required |
| | **Description** | What the type is for | |
| Applies to | **What a request of this type may ask for** | The kinds of line a request of this type offers: **A part**, **A service**, **An asset, by its category**, **Something else** | At least one. A new type starts with all four, which narrows nothing |
| What it asks of the requester | **Require department** | A request of this type cannot be raised without naming the department it is for | Off by default. The requisition form then asks **Department** |
| | **Restrict price editing** | The requester may not put a price on a line. A catalogue line keeps the catalogue price; anything else is left for the buyer to price | Off by default. A line's price box then reads **Priced by the buyer** |
| Visible to | **Roles** | Only people holding one of these roles are offered this type | Leave it empty to offer it to everybody |
| Availability | **Offered** | Whether the type is offered for new requests | Turning it off keeps every request already raised as this type, and stops it being offered for new ones |

## What a type does to a request

On the [requisition form](https://docs.assetinfinity.ai/commercial/purchase-requests.md#raising-a-requisition), choosing a type narrows **What it is** on every line to the kinds the type allows; where it allows only one, the box is fixed. Lines already typed that the type does not allow move to the first kind it does, and prices already typed are cleared where the type leaves prices to the buyer. A line chosen from the catalogue keeps what it is. The type a request was raised as is shown under **Request type** in its details.

> [card] [Requisitions](https://docs.assetinfinity.ai/commercial/purchase-requests.md)
>
> Raising a request, and what its type decides.

> [card] [Vendor and contract settings](https://docs.assetinfinity.ai/config/commercial.md)
>
> The rest of the commercial vocabulary.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.