# Introduction

The components in the **Partner Library** may support many various scenarios, but the library is **primarily aimed at B2B commerce** where there is a need for modular business logic, repeatable workflows, and integrations.

The Partner Library is available as a perspective in the Management Dashboard.

{% hint style="info" %}
Customer tenants allow to reach the Partner Library straightaway. Partners, willing to participate and contribute, have to request partner access on their tenants first. For more information contact the [Sales Team](mailto:sales@emporix.com).
{% endhint %}

Select the Partner Library perspective from the expanded perspective chooser:

<figure><img src="/files/wVMdQ36QjOc1n5uVd8sr" alt="Access the Partner Library" width="200"><figcaption><p>Access the Partner Library</p></figcaption></figure>

## Key features

The Partner Library serves as a B2B marketplace not only as a list of products but as a set of services around that catalog:

| Feature               | Description                                                                                                                                            |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Component catalog** | Search, categories, pricing models, trials (where applicable), reviews or ratings, demos or documentation links — so buyers can shortlist and compare. |
| **Trust and quality** | Verification, security and compliance checkpoints, quality expectations, and published policies so listings meet a baseline before customers commit.   |
| **Provisioning**      | Installation and activation flows, permission or scope alignment, and tenant entitlements so only entitled tenants use paid or restricted offerings.   |
| **Lifecycle**         | Updates, compatibility, operational monitoring where relevant, and deprecation rules so end-of-life is predictable.                                    |
| **Support model**     | Clear ownership for component support (platform vs partner), escalation paths, and SLA expectations tied to what Emporix vs the partner commits to.    |

## What you can do in the Partner Library

<figure><img src="/files/GCFLCwEk8kdztOzL9tFX" alt="Partner Library Home Page"><figcaption><p>Partner Library Home Page</p></figcaption></figure>

### Discover and install extensions

Customers can browse integrations and functional extensions—for example payment or tax modules, connectors, and other add-ons aligned with their operating model. Listings are meant to reduce guesswork: you can see what exists, how it maps to your needs, and then activate what fits, within your tenant and permission model. Components are installed and licensed per customer tenant. That keeps boundaries clear for security, compliance, and ownership: what is active, where, and under which entitlements.

### Adopt packaged value streams

You can implement **repeatable business processes** using pre-built value streams, which respond to your complex needs, instead of designing every flow from scratch. The offered value streams provide automation for various workflow patterns, that consist of multiple steps, use AI intelligence or create a chain of subflows. For example, value streams can orchestrate returns handling, fraud discovery, or other process-oriented flows.

### Use AI Agents

AI Agents help automate or assist operational work: for example onboarding, guided selling, or support scenarios, with humans in the loop where required. They are offered as ready-made building blocks rather than one-off custom projects.

### Discover cloud functions

Cloud functions open numerous integration possibilities. You can adopt an external service that enhances digital processes with custom logic, automation, and system connectivity in real time.

### Commercialize as a partner

Partners can list and maintain the solutions they have built for Emporix use cases. The library provides a standardized path to reach customers who already run on ACE, with room for listing detail, compatibility expectations, and operational handover.

## Components integration within Emporix solution

The Partner Library is tightly integrated with ACE platform. It relies on shared tenant context, identity, and permissions, so discovery and activation stay consistent with how the rest of your environment is governed.

After installation, components are visible and manageable in the Management Dashboard (MD). Depending on the component type, you work with the appropriate functionalities, for example, AI Agents, Value Streams, and Extensions, so administrators have a single operational outlook for what is live in the tenant.

All the components submitted by the Emporix partners undergo a dedicated review and approval process from Emporix side to ensure that what appears in the library meets Emporix requirements. The goal is to build a verified, trustworthy catalog of components that customers can adopt with confidence, while partners get a fair, predictable process to publish.

The support for issues related to the partner components is split:

* **Emporix** handles **platform-level** issues related to the general product behavior.
* **Partners** provide **component-specific** expertise, for example, in-depth support related to how a listing behaves, component configuration, and delivering component fixes.

This split allows clear distinction for customers to know whom to contact if any issue arises.

Customers are able to try out the components in a non-production environment first before promoting them to production. This gives time and space for the teams to validate behavior and integrations before going live.

## Request and activation flow

<figure><img src="/files/aBLuCwzK3BjCoQONbKuN" alt="Emporix Partner Library request and activation flow"><figcaption><p>Emporix Partner Library request and activation flow</p></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://developer.emporix.io/partner-library/introduction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
