> For the complete documentation index, see [llms.txt](https://docs.catalyx.solutions/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.catalyx.solutions/catalyx-blockchain-manager/canton-network/version-2.0/console-guide-canton/validators/parties.md).

# Parties

<div data-with-frame="true"><figure><img src="/files/f3DY1t4U6zvLqV3hhSBv" alt=""><figcaption></figcaption></figure></div>

{% hint style="info" %}
This page describes the screens. For the concepts — what an external party is, what multi-hosting means, and the complete onboarding and approval workflow — see [External & Multi-Host Parties](/catalyx-blockchain-manager/canton-network/version-2.0/validator-management/external-and-multi-host-parties.md).
{% endhint %}

## Header actions

| Button                     | Opens                                                                                                                                                                                                                                                             |
| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Onboard External Party** | The four-step external party onboarding wizard. For what each step does and why, see [Onboarding an external party](/catalyx-blockchain-manager/canton-network/version-2.0/validator-management/external-and-multi-host-parties.md#onboarding-an-external-party). |
| **Allocate Party**         | The Allocate Party modal                                                                                                                                                                                                                                          |

## Sub-tabs

<table><thead><tr><th width="220">Sub-tab</th><th>Shows</th></tr></thead><tbody><tr><td><strong>Hosted Parties</strong></td><td>Parties currently hosted by this participant.</td></tr><tr><td><strong>Hosting Proposals</strong></td><td>Hosting proposals naming this participant that are not yet fully authorized. Badged with a count when there are any.</td></tr><tr><td><strong>Browse Parties</strong></td><td>Lookup for any party known to this participant, including parties hosted elsewhere.</td></tr></tbody></table>

***

## Hosted Parties

*Parties currently hosted by this participant.*

<table><thead><tr><th width="200">Column</th><th>Contents</th></tr></thead><tbody><tr><td><strong>Party ID</strong></td><td>The party's full identifier, truncated, with a copy button.</td></tr><tr><td><strong>Permission</strong></td><td>One badge per distinct permission across the party's hosts: <code>submission</code>, <code>confirmation</code>, or <code>observation</code>.</td></tr><tr><td><strong>Threshold / Hosts</strong></td><td>A row of dots — one per host that can confirm, filled up to the confirmation threshold. Hover for <em>"N of M confirming participant(s) must confirm"</em>. Falls back to a plain ratio when there are more than eight.</td></tr></tbody></table>

Rows are sorted by permission strength — submission, then confirmation, then observation — and then by party ID.

**Permission filter.** A button group above the table filters to **All**, **Submission**, **Confirmation**, or **Observation**. A party matches if any of its hosts holds that permission.

**Refresh.** Reading the topology mapping is comparatively slow, so this list has an explicit refresh button rather than polling. While it loads you will see *Loading topology mapping, this may take a while…*

### Expanding a row

An expanded row shows **Hosted on (`n`)** — every participant hosting the party, with its permission, sorted by permission strength. A participant still being onboarded carries an `onboarding` badge.

For a party whose keys are held externally, the expanded row also offers **Edit hosting**, which opens the hosting amendment flow. See [External & Multi-Host Parties](/catalyx-blockchain-manager/canton-network/version-2.0/validator-management/external-and-multi-host-parties.md#changing-a-partys-hosting).

{% hint style="info" %}
**Edit hosting only appears for externally-signed parties.** A party managed by the participant itself has no external key holder to sign a hosting change, so its hosting cannot be amended this way.
{% endhint %}

### States

| Situation              | What you see                                                                                       |
| ---------------------- | -------------------------------------------------------------------------------------------------- |
| No hosted parties      | **No hosted parties** — *This participant has not authorized any PartyToParticipant mappings yet.* |
| Filter matches nothing | **No matching parties** — *No hosted party has a participant with `<permission>` permission.*      |
| Load failed            | **Failed to load hosted parties**, with the error                                                  |

***

## Hosting Proposals

*Hosting proposals naming this participant that are not yet authorized by everyone involved. These parties cannot be used until each named host approves. Approving makes this participant co-host the party — it replicates that party's data and takes part in confirming its transactions.*

Only proposals that name **this** participant are listed. The synchronizer's topology store is shared across the whole network and can hold hundreds of proposals; the rest are filtered out.

<table><thead><tr><th width="220">Column</th><th>Contents</th></tr></thead><tbody><tr><td><strong>Party ID</strong></td><td>The party being proposed.</td></tr><tr><td><strong>Hosting Participants</strong></td><td>Every named host. Your own participant is tagged <code>this participant</code>.</td></tr><tr><td><strong>Threshold</strong></td><td>The proposed confirmation threshold.</td></tr><tr><td>—</td><td>The action, or the current waiting state.</td></tr></tbody></table>

The action cell shows one of:

|                                | Meaning                                                    |
| ------------------------------ | ---------------------------------------------------------- |
| **Approve**                    | This participant is required to authorize, and has not yet |
| *Approved — updating topology* | You approved just now; the change is still propagating     |
| *Waiting on other hosts*       | This participant has already authorized; others have not   |

### Approving

Clicking **Approve** authorizes immediately — **there is no confirmation dialog.** The result appears as a toast:

| Toast                                             | Meaning                                                       |
| ------------------------------------------------- | ------------------------------------------------------------- |
| *Hosting approved — the party is now active*      | Every named host has now authorized                           |
| *Hosting approved — still waiting on other hosts* | Your authorization is recorded; the party is still not usable |
| *Approval failed*                                 | With the reason                                               |

After approving, the row's button disappears and the list polls for up to 30 seconds until the synchronizer agrees, so you do not need to refresh manually.

{% hint style="warning" %}
Approving is a real commitment. This participant will store that party's data and take part in confirming its transactions. Only approve proposals you recognise.
{% endhint %}

Empty state: **Nothing pending** — *Every party hosting involving this participant is fully authorized.*

***

## Browse Parties

*Search any party known to this participant by ID prefix, including parties hosted elsewhere on the synchronizer.*

Type at least **two characters** of a party ID prefix and press Enter or **Search**.

| Column                | Contents                                                  |
| --------------------- | --------------------------------------------------------- |
| **Party ID**          | The party's identifier                                    |
| **Identity Provider** | The identity provider ID, or `default`                    |
| **Scope**             | `Local` if hosted on this participant, `Remote` otherwise |

{% hint style="info" %}
This is a **prefix search, not a full listing.** On a production network a participant may know of hundreds of thousands of parties, so there is deliberately no "list all" — you must know roughly what you are looking for. Use **Hosted Parties** for the complete list of parties this participant hosts.
{% endhint %}

If nothing matches, the console offers **Allocate "`<your search term>`"**, which opens the Allocate Party modal pre-filled with the term.

***

## Allocate Party

*Provision a new party on this validator. The hint is incorporated into the generated party ID.*

| Field             |                                                                                        |
| ----------------- | -------------------------------------------------------------------------------------- |
| **Party ID hint** | *Choose a short, human-readable hint. Backend appends a hash for uniqueness.* Required |

Buttons: **Cancel** and **Allocate**. On success a toast reports *Party allocated* with the resulting party ID, and both lists refresh.

{% hint style="info" %}
This allocates a **participant-managed** party — the participant holds its keys and can submit on its behalf. To create a party whose keys are held outside the participant, use **Onboard External Party** instead.
{% 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 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.catalyx.solutions/catalyx-blockchain-manager/canton-network/version-2.0/console-guide-canton/validators/parties.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.