> For the complete documentation index, see [llms.txt](https://experience-digital-transform.gitbook.io/experience-digital-transformation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://experience-digital-transform.gitbook.io/experience-digital-transformation/information-mediator/configuring-your-information-mediator.md).

# Configuring your Information Mediator

A practical pathway for configuring the Information Mediator components that enable secure, interoperable data and service exchange between organizations.

### Connecting organizations for secure and interoperable information exchange

## What it is

The Information Mediator provides the infrastructure through which organizations securely exchange data and services with one another. Configuration tooling exists to help organizations set up the **Security Server** components needed to participate in that exchange, automating what would otherwise be a complex manual setup process.

## What Needs to Be Configured

At a high level, the current connector tooling covers:

* Installation of the Information Mediator Security Server
* Management of the certificates that establish trust between organizations
* Configuration of authentication and signing
* Registration of the organization with the Central Server
* Configuration of the organization's own subsystems and services on the Security Server

## The Configuration Journey

{% hint style="success" %}
**Deploy → Establish trust → Register → Configure services → Connect**
{% endhint %}

An organization deploys its Security Server, establishes trust through certificates, registers with the Central Server, configures its own services, and connects into the exchange. Registration involves an approval step by Central Server administrators before an organization is fully trusted. The current tooling automates parts of this journey — including certificate creation and import, and the pre-approval and post-approval configuration steps — while keeping the process repeatable.

## Configure in three phases

The configuration tooling's workflow is documented here as three phases, matching the repository's own playbooks:

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>⚙️ Install the Information Mediator Security Server</strong></td><td>Deploy the Security Server to Kubernetes with Helm.</td><td><a href="/experience-digital-transformation/information-mediator/install-the-information-mediator-security-server.md">Install the Information Mediator Security Server</a></td></tr><tr><td><strong>📋 Configure the Information Mediator Before Approval</strong></td><td>Initialize the server, create and sign certificates, and configure members, subsystems and services.</td><td><a href="/experience-digital-transformation/information-mediator/configure-the-information-mediator-before-approval.md">Configure the Information Mediator Before Approval</a></td></tr><tr><td><strong>✅ Complete the Information Mediator Configuration After Approval</strong></td><td>Activate the authentication certificate and register subsystems once approval has been granted.</td><td><a href="/experience-digital-transformation/information-mediator/complete-the-information-mediator-configuration-after-approval.md">Complete the Information Mediator Configuration After Approval</a></td></tr></tbody></table>

{% hint style="info" %}
Step-by-step installation and configuration guidance is now available in the three pages above, based on the `bb-im-connector` repository.
{% endhint %}

## Explore the Repository

{% hint style="success" %}
**Explore the Information Mediator configuration tooling →** [github.com/GovStackWorkingGroup/bb-im-connector](https://github.com/GovStackWorkingGroup/bb-im-connector/blob/main/README.md)
{% 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://experience-digital-transform.gitbook.io/experience-digital-transformation/information-mediator/configuring-your-information-mediator.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.