> For the complete documentation index, see [llms.txt](https://docs.yoplanning.support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yoplanning.support/en/yoplanning-academy/yoplanning-parametrage/gestion-des-revendeurs-et-apporteurs-daffaires/gestion-des-apporteurs-daffaires/back-office-pour-apporteur-daffaires-multi-team.md).

# Back-office for business introducers, multi-team

### What is this feature for?

The back office dedicated to business introducers allows a professional who recommends clients to different teams (structures using Yoplanning) to view, via a single interface, the orders generated thanks to their recommendations. This multi-team dashboard centralizes all useful information, regardless of the partner with whom you collaborate.

### How to access the business development back office?

1. **Only one email to use**:
   * The common identifier for all your business relationships is your **email address**.
   * Make sure to **always provide the same email address** to your partners when registering in their systems.
2. **Back office registration**:
   * Go to the following URL: 👉 <https://yoplanning.pro/signup/business-provider>
   * Use the email address your partners have registered for you.
   * Create your password, then validate.
3. **Connection**:
   * Once your account is created, log in to <https://yoplanning.pro> with your credentials.

### What can be viewed in the back office?

* The **list of orders** placed in all partner **teams** that have identified you as a contributor.
* **Details of customers** (within the limits of accessible data) who have made purchases through you.
* The information is sorted **by team**, which allows you to view the results of your recommendations according to each partner.

### Usage tips and best practices

* **One email = consolidated view**: always use the **same email address** with all your partners to centralize data.
* **Check your role**: Ask each of your partners to **register you as a business introducer** with the correct email address in their Yoplanning instance.
* **Keep your password safe** and do not share it.

### Common Problems and Solutions

#### No orders displayed

* Check that the partner has correctly identified you as a contributor with **exactly the same email address**.
* Make sure that orders have been placed by customers you have referred.

#### Access denied or forgotten password

* Use the **"Forgot Password"** feature on the login page to reset your password.

#### I only see some of my partners

* This means that some of your partners have not yet entered your email address in their Yoplanning. Contact them to correct this.


---

# 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.yoplanning.support/en/yoplanning-academy/yoplanning-parametrage/gestion-des-revendeurs-et-apporteurs-daffaires/gestion-des-apporteurs-daffaires/back-office-pour-apporteur-daffaires-multi-team.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.
