Repository settings

Who can access settings?

The Settings tab is only visible to delegates of a repository. New repositories start with their creator as the sole delegate; additional delegates are added through proposals.

Non-delegates can still view all repository content (unless the repo is private), but cannot propose identity changes.

Identity proposals

Anything that touches the repository's identity document — name, description, default branch, visibility, delegate set, threshold — happens through proposals. The flow is:

1. A delegate fills in the new values and gives the proposal a short title explaining the intent.
2. Radish writes the proposal to Radicle storage, signed by the proposer.
3. Other delegates accept or reject from the same Settings page.
4. Once threshold-many delegates have accepted, the change takes effect on the next refresh.

Proposals are visible in the right column of the settings page along with their current vote counts.

Repository identity

The top section of the settings page edits the repository's metadata:

• Name — the human-readable name shown across the UI.
• Description — a short summary, displayed on cards and the repo header.
• Default branch — the branch shown when nothing else is selected.
• Private repository — whether non-delegates can read the repo.

Edit any of these fields, give the proposal a title, and submit. Other delegates will see your proposal pending in their settings view.

Delegates

Delegates are the keys allowed to mutate the repository's identity. The delegates list shows every current delegate with their alias and DID. Two operations are available:

• Add delegate. Paste in a DID and propose adding it. The new delegate can vote on subsequent proposals once added.
• Remove delegate. Click Remove next to an existing delegate to propose dropping them. Removal proposals must clear the same threshold as any other change.

You cannot remove the last delegate — every repository must have at least one identity owner.

Threshold

The threshold is the number of delegate accept-votes required before a proposal takes effect. For a single-delegate repo it's always 1. As you add delegates you can raise the threshold to require multi-party approval — a 2-of-3 setup, for example, ensures two delegates always have to agree.

Changing the threshold is itself a proposal that goes through the current threshold.

Voting on a proposal

For each pending proposal you'll see three actions, depending on your role:

• Accept. Adds your signed approval. When enough accept-votes accumulate, the proposal merges.
• Reject. Records a signed objection without applying the change.
• Redact. Available to the proposer; withdraws the proposal entirely.

The current accept/reject tally and the threshold required are shown next to each proposal.

What happens when a proposal merges

The signed identity revision is written to Radicle storage. Subsequent reads of the repository will see the new metadata, delegate set, or threshold. Existing patches and issues are unaffected — they retain their authorship and history.

If a proposal you cared about gets stuck without enough votes, Radicle keeps the proposal record forever. You can pick up where it left off with a fresh proposal at any time.