> For the complete documentation index, see [llms.txt](https://docs.b2b-sellers.com/b2b-platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.b2b-sellers.com/b2b-platform/user-documentation/faq/order-lists-admin-configuration.md).

# Order Lists - Admin Configuration

## Display Unauthenticated Visitor

If enabled, non-logged-in users may create order lists and place items in order lists, however, these order lists are only saved in a browser session instead of at the customer, so they may be gone again at the next visit.

## Which types of product lists should the unauthenticated and logged-in customer be able to see?

Select the list types that should be visible to non-logged-in users or logged-in employees.

## Which types is from Customer deleteable?

Select list types that can be deleted by users or client employees.

## Default List-Type, if not filled?

Select the type that should be used by default as the new order list if no special type is stored.

## Default order list name

**C**hoose a name that the list uses by default e.g "My Order List | My Order Template | My Wish List"

### Entities <a href="#entities" id="entities"></a>

* [PAGEB2bProductList](https://docs.b2b-sellers.com/b2b-platform/api-references/entities/b2bproductlist)
* [PAGEB2bProductListItem](https://docs.b2b-sellers.com/b2b-platform/api-references/entities/b2bproductlist/b2bproductlistitem)
* [PAGEB2bProductListType](https://docs.b2b-sellers.com/b2b-platform/api-references/entities/b2bproductlist/b2bproductlisttype)

{% content-ref url="/pages/NmLHZ3gsYvzSRRJQf7pq" %}
[Order Lists as an Employee](/b2b-platform/user-documentation/using-b2bsellers-functionality-as-a-customer/order-lists-as-an-employee.md)
{% endcontent-ref %}


---

# 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.b2b-sellers.com/b2b-platform/user-documentation/faq/order-lists-admin-configuration.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.