> For the complete documentation index, see [llms.txt](https://docs.xyb.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xyb.co/xyb-console/product-configurations/managing-products-in-the-xyb-console.md).

# Managing Products in the XYB Console

The **Products dashboard** within the **Product Configuration** module is your central hub for creating, organizing, and managing all financial products across the XYB ecosystem. It lets you design products once, then attach services, schemas, and configurations that power their behavior across your platform.

***

Products are modular building blocks that define the structure and lifecycle of financial offerings, like BNPL services, or savings accounts. Each product is a container for:

* **Behavioral logic** (when it becomes active or archived)
* **Attached services** (backend modules like ledger, entity, and account services)
* **Schema configurations** (defining data and operational rules)

***

The Products dashboard gives you full visibility and control over all your products. Key capabilities include:

* **List View of All Products**\
  Browse every product created across environments and services. Each product entry shows its name, reference ID, updated timestamp, owner, and current status (Active/Passive).
* **Recently Updated Section**\
  Quickly access products that were recently modified for rapid iteration and testing.
* **Search, Filter & Sort**\
  Filter by product name, reference ID, date range, or status to locate products instantly.
* **Lifecycle Management**\
  Activate or deactivate products as needed. Passive products are safely preserved without impacting live environments.

***

To create a new product:

1. Click **+ New Product** on the top right.
2. Enter a **Product Name** (displayed in the dashboard).
3. Choose a **Product Reference** (auto-generated or custom).
   * This is the unique ID used by other XYB modules (Access Management, logs, APIs).
4. Add a **Description** to document its purpose or scope.
5. Click **Create product**.

Once created, you can start attaching **services** and **schema configurations** to bring your product to life.

> **Tip:** Use descriptive names and references to make products easy to identify when they’re consumed by other services.

***

### Importing Products

If you have predefined product definitions, you can bulk import them:

1. Click **Import**.
2. Drag and drop your import file or select it manually.
3. Click **Import**.

Imported products are added as **Passive** by default, so they don’t affect production until you activate them.

***

### Exporting Products

You can export product configurations to share or version-control them:

1. Click **Export**.
2. Select up to 100 products from your dashboard list.
3. Click **Export products**.

This produces a file containing your selected product definitions.

***


---

# 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.xyb.co/xyb-console/product-configurations/managing-products-in-the-xyb-console.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.