> 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-guide/using-the-b2b-platform.md).

# Using the B2B Platform

How customers, employees and sales representatives work with the B2B Platform

The sections above describe how a shop operator installs and configures the B2Bsellers Suite. This section describes the other side: how the people who log into the shop actually work with it.

The B2B Platform is reached at `/b2b_platform` and is the central working area for everyone on the customer side.

## Who works where

* **Customers and employees** use the customer portal to place orders, manage their company, employees, addresses and cost centers, and to work with order lists, budgets and offers.
* **Sales representatives** use the sales representative portal to work on behalf of their assigned customers, create offers and follow customer activity.

{% hint style="info" %}
Both portals are built from the B2B Platform menu and can be customized by the shop operator. The navigation in your shop may therefore differ from the examples shown here.
{% endhint %}


---

# 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-guide/using-the-b2b-platform.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.