> For the complete documentation index, see [llms.txt](https://airporttaxis.gitbook.io/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://airporttaxis.gitbook.io/doc/management/affiliates.md).

# Affiliates

In this section, you will have access to a list of all affiliates registered in the system.

[#list-of-affiliates](#list-of-affiliates "mention")

[#invoicing](#invoicing "mention")

[#add-new-affiliate](#add-new-affiliate "mention")

***

### List of Affiliates

The list of all affiliates is presented in paginated format, with 15 users per page. The entry for each affiliate includes data such as:&#x20;

* User ID
* Name
* Email
* Commission rate
* Automatic settlement activity flag with the system administrator
* Payment via invoice or immediate
* Link for settlement process
* ["More Info" button for user editing](/doc/management/users/user-profile.md)

Also, at the top of the page, there is an option to assign a new affiliate.

<figure><img src="https://108171149-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6rEa2ptIaH88ofilryun%2Fuploads%2FvF2fhsCOJBAbTo915nHi%2Fimage.png?alt=media&amp;token=cda6970d-b626-4222-80a9-79720ff5ac94" alt=""><figcaption><p>List of Affiliates</p></figcaption></figure>

### Invoicing

<figure><img src="https://108171149-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6rEa2ptIaH88ofilryun%2Fuploads%2FZPflBVxJ2hCgVyTqVt8r%2Fimage.png?alt=media&amp;token=eee2c7e9-d9fe-4a8d-90b2-e942f7dde791" alt=""><figcaption><p>Invoicing Section</p></figcaption></figure>

This section displays all orders that have been created by the affiliate. The list is presented in the form of: order date, order #, total order cost, discount (if any), order status, affiliate commission.

The administrator can select the orders for which they want to settle accounts using checkboxes, and then generate an invoice for all selected orders using the "Actions" option.

Following this, the system will generate an invoice and issue it to the affiliate for payment.

### Add New Affiliate

<figure><img src="https://108171149-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6rEa2ptIaH88ofilryun%2Fuploads%2FqcShajf3VX0Kw6oHfHQd%2Fimage.png?alt=media&amp;token=773d1b49-a983-48da-9879-72ea4c4285b7" alt=""><figcaption><p>Add New Affiliate Pop-up</p></figcaption></figure>

After clicking on the "Add New Affiliate" option in the top right corner of the page with the list of all affiliates, a popup will appear overlaying the page, allowing the system administrator to assign a new affiliate.

To do this, they need to select a user they want to make an affiliate. The user selection field supports autocomplete, so it's enough to just start typing the user's name and the system will itself suggest options. Additionally, it is necessary to specify the commission amount, whether settlements with this affiliate will be automatic or not, and whether the affiliate will pay in one lump sum for all their orders via an invoice, or for each order separately.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://airporttaxis.gitbook.io/doc/management/affiliates.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.
