> For the complete documentation index, see [llms.txt](https://docs.ib.b2core.b2broker.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ib.b2core.b2broker.com/for-brokers/how-to-articles/how-to-create-an-ib-type.md).

# How to create an IB type

{% hint style="info" %}
Before creating a new type, make sure that the following necessary parameters are configured and enabled in the Back Office:

* Navigate to **Products** > **Products** and check that at least one product with type **Partner** is created and enabled. You can use filter by type for quick search. If there is no product with this type, [create one](/for-brokers/how-to-articles/how-to-set-up-a-wallet.md).
* Navigate to **Introducing brokers** > **Promo** > **Landings** > **Links** and make sure that at least one link is created. Go to **link details** and check that the **URL** field has a correct value.
  {% endhint %}

{% stepper %}
{% step %}
Go to **Introducing brokers** > **Program** > **Types**.
{% endstep %}

{% step %}
Click **Create**. The **Preferences** tab of the Type details will open.
{% endstep %}

{% step %}
Click **Save** to apply the changes.
{% endstep %}

{% step %}
In the **Name** field, enter a partnership program name.
{% endstep %}

{% step %}
In the **Description** field, enter a partnership program caption. This can be, for example, conditions for participation.
{% endstep %}

{% step %}
From the **Registration** dropdown, select an option of joining a partnership program:

* **Auto**: Each client signing up to the B2CORE UI automatically becomes a partner. If multiple partnership programs are available, an IB account is created for each program.
* **Public**: Clients can see available partnership programs in the B2CORE UI and can apply for it. For this type of registration, **Approvement** option is available and enabled by default, which means that clients join a partnership program only after their [joining requests](#user-content-fn-1)[^1] are approved by a Back Office admin. If the option is disabled, the partner can access the IB Room immediately after the registration.
* **Private**: Clients are added to a partnership program by a Back Office admin. Applying via the B2CORE UI is unavailable.
* **Restricted**: Clients can join a partnership program only using a link provided by a participant of another or the same program. Specify the program identifier in the **Restriction** field. For this type of registration, **Approvement** option is available and enabled by default, which means that clients join a partnership program only after their [joining requests](#user-content-fn-1)[^1] are approved by a Back Office admin. If the option is disabled, the partner can access the IB Room immediately after the registration.
  {% endstep %}

{% step %}
From the **Product** dropdown, select a product.
{% endstep %}

{% step %}
From the **Currency** dropdown, select a currency.
{% endstep %}

{% step %}
Click **Save** to apply the changes.
{% endstep %}
{% endstepper %}

[^1]: To learn more about client requests, refer to [B2CORE documentation](https://docs.b2core.b2broker.com/back-office-guide/clients/requests).


---

# 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.ib.b2core.b2broker.com/for-brokers/how-to-articles/how-to-create-an-ib-type.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.