> For the complete documentation index, see [llms.txt](https://docs.licensespring.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.licensespring.com/vendor-platform/orders.md).

# Orders

This is a summary view that displays a table with order information. Clicking on one of the orders will open the orders summary view.

Actions you can take on the orders summary view include:

* Search for an order
* Download all orders and licenses for a given date range
* Start the order creator process

![](https://content.gitbook.com/content/gLzurdfXUuKr9IziZWLz/blobs/QNFxIpxVevl4lNrTtTtk/KLP8NbzK1WCjzE25jL44H_image.png)

The columns you can specify for the orders table are:

* `Created on` — Date/time at which an order was created
* `Customer email` — If a customer is specified for this order, then the customer's email address will appear in this column
* `Customer name` — Customer name if the order has a customer specified
* `Customer company` — Company of the customer if the `Order` belongs to a customer with a company field
* `Customer account` — Account of the customer if they belong to one, and if the order has a customer specified
* `Customer reference` — Customer reference number if one is specified
* `Customer Labels` — Customer label if one was specified
* `Order ID` — Orders will always have this value
* `Order reference` — Optionally specified reference number of the order
* `Last updated` — Last time the order information was updated (order reference, campaign parameters, downloadID, is test, or is trial)
* `Type` — If created using the [**Trial Key**](https://docs.licensespring.com/license-api/trial-key.md) License API endpoint it will be set as `api_trial` and in rest of the cases it will be set as `normal`. It can be overwritten using the Management API when using the [**Create Order**](https://docs.licensespring.com/management-api/order/create-order.md) endpoint
* `Campaign parameters` — Optional field, currently not used
* `Is trial` — If the order was created when generating a trial license via the License API, there will be a green check mark in this field

#### Remove users from orders

Remove users from every user-based license in one or more orders by pasting their emails. Key-based licenses are not affected.

**From several orders:**

1. **Select the orders.** On the `Orders` list, tick the orders, or tick the box in the header to select the page. The selection is kept when you change pages, search or filter. You can select up to 100 orders. When the whole page is selected and more orders match, click `Select all orders found`.
2. **Click `Remove users`** in the bar above the list.
3. **Enter the emails.** Type or paste them; an email is added when you press `Enter`, `Tab` or a comma.
4. **Click `Remove users`.**

<figure><img src="https://1783554078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgLzurdfXUuKr9IziZWLz%2Fuploads%2FeFNpVJbfkaw8ZBETmyD4%2F23-platform-orders-selection.png?alt=media&amp;token=554301af-4cc1-4820-a6ef-3870997c7788" alt=""><figcaption></figcaption></figure>

**From one order:** open the order, go to its licenses and click `Remove users`.

If every user was removed, the dialog closes. Otherwise it shows a summary and one row per email:

| Result          | Meaning                                                               |
| --------------- | --------------------------------------------------------------------- |
| `Removed`       | The user was removed. `Licenses removed` shows from how many licenses |
| `Not assigned`  | The user has no user-based license in these orders                    |
| `Unknown email` | There is no license user with this email                              |

<figure><img src="https://1783554078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgLzurdfXUuKr9IziZWLz%2Fuploads%2F90uYUwevCxa774qZhdX8%2F24-platform-remove-users-orders-results.png?alt=media&amp;token=81878a81-1098-4bda-acd3-5067697c3e9e" alt=""><figcaption></figcaption></figure>

> Removing users this way does not reset their devices. The devices are no longer linked to the users, but stay active. To free the activations, reset the devices from the license's `Devices` tab, or use `Batch remove users` on the license with the device reset option.

More than 50 emails are sent in batches of 50, and more than 10 orders in groups of 10. You still get one result per email. If a part fails after others went through, the changes made so far are kept, and the dialog lists the orders that were not fully processed. Those orders stay selected in the list, so you can try again straight away.

The same action is available in the Management API: [Unassign users from orders](https://docs.licensespring.com/management-api/order/unassign-users-from-orders.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.licensespring.com/vendor-platform/orders.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 `automate deployments from our CI pipeline` 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.
