> For the complete documentation index, see [llms.txt](https://docs.bitsafe.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bitsafe.finance/product-suite/decentralization-manager/user-guide.md).

# User Guide

Walkthrough of the web UI for day-to-day party and governance operations.

This guide walks through the day-to-day operations available in the Decentralization Manager web UI. Open the UI in your browser at the configured host and port (for example <http://localhost:8081>), authenticate via the configured identity provider, and use the workflows below.

## Creating a decentralized party (onboarding)

Configure every participant node with the others' connection details, start all participant servers, then on the coordinator's UI click Create Party and enter a party ID prefix. The coordinator invites peers and orchestrates cryptographic key generation, topology proposal creation, multi-party signing, and submission to Canton.

## Deploying contracts

From a party card, click Deploy Contracts, upload DAR files via the file picker, and configure the contract definitions (operator party, templates, fields). The coordinator distributes and uploads the DARs to all participants, prepares the ledger submission, collects multi-party signatures, and executes on the Canton ledger.

## Removing a participant (kick)

From a party card, click Kick Participant and select the participant to remove. The coordinator exports the current namespace state, creates updated topology proposals with a reduced threshold and the removed P2P mapping, collects signatures from the remaining members, and submits the proposal to Canton.

## Governance actions

The UI surfaces governance confirmations grouped by action. Members confirm a proposed action, and once the confirmation threshold is met the action can be executed. Stale confirmations can be expired or cancelled. Workflow instances and their lifecycle state are visible in the UI, where you can also dismiss or retry failed workflows.

## Monitoring status

Live peer connectivity monitoring and workflow progress tracking are available throughout the UI, so you can see which peers are reachable and how each multi-party workflow is progressing in real time.


---

# 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://docs.bitsafe.finance/product-suite/decentralization-manager/user-guide.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.