Parties

The Parties tab shows the parties this participant hosts, the hosting proposals waiting on it, and a lookup for any party on the synchronizer — and it is where all party operations start.

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.

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.
Allocate Party	The Allocate Party modal

Sub-tabs

Sub-tab	Shows
Hosted Parties	Parties currently hosted by this participant.
Hosting Proposals	Hosting proposals naming this participant that are not yet fully authorized. Badged with a count when there are any.
Browse Parties	Lookup for any party known to this participant, including parties hosted elsewhere.

---

Hosted Parties

Parties currently hosted by this participant.

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

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.

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.

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.

Column	Contents
Party ID	The party being proposed.
Hosting Participants	Every named host. Your own participant is tagged this participant.
Threshold	The proposed confirmation threshold.
—	The action, or the current waiting state.

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.

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.

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

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.

If nothing matches, the UI 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.

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.