> 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/getting-started/getting-started-with-fairmarkit/user-types-in-fairmarkit.md).

# User types in Fairmarkit

Fairmarkit defines distinct roles for each user in the sourcing process, catering to their specific needs. Whether you're a requester, buyer, or supplier, Fairmarkit simplifies your sourcing tasks and communication.

### Requesters <a href="#requesters" id="requesters"></a>

Request the goods or services you need. Fairmarkit’s Intake tools ensure that your requests comply with company policies and are automatically routed to the appropriate buyer team.

[Learn more about requesters](https://docs.fairmarkit.com/content/requesters/overview.htm)

### Buyers <a href="#buyers" id="buyers"></a>

Manage the sourcing process: create events from various pathways, including reviewing requests, invite suppliers to submit responses, and after evaluating these submissions, award the event, ensuring efficient and cost-effective purchasing decisions. [Buyer roles](https://docs.fairmarkit.com/content/buyers/gs/user-roles.htm), which are a subset of permission sets such as Buyer, Observer, Requester, Team Lead, Supervisor, Admin, and Collaborator, allow you to customize permissions and responsibilities based on your team's needs.

[Learn more about buyers](https://docs.fairmarkit.com/content/buyers/buyers.htm)

### Suppliers <a href="#suppliers" id="suppliers"></a>

Respond to buyer events by providing pricing for goods and services and accessing new sales opportunities. Supplier roles, which are a subset of permission sets such as Admin and Sales Rep, allow you to customize permissions and responsibilities based on your team's needs.

[Learn more about suppliers](https://docs.fairmarkit.com/suppliers/)<br>


---

# 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/getting-started/getting-started-with-fairmarkit/user-types-in-fairmarkit.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.