---
title: "Decision settings"
description: "Decision settings control whether governance changes in Talkspirit apply directly or become a proposal that circle members can object to first"
category: structure-governance
section: proposals-and-decisions
tags: [admin]
type: Reference
lastUpdated: 2026-10-19
locale: en
canonical: https://support.talkspirit.com/en/structure-governance/what-are-decision-settings
---

# Decision settings


Decision settings control how your organisation decides governance changes: adding a role, reshaping a circle, adopting a policy, running an election. You choose whether a change applies as soon as someone makes it, or becomes a proposal that the circle's decision makers can object to first. Only administrators can open the page.

> **In summary:** Decision settings live on **Structure settings → General → Decision settings**. Four cards (three without the Holacracy add-on), each with its own **Save** button: **Proposal adoption** decides whether governance changes go through a proposal and when a proposal is adopted, **Draft proposal access** and **Proposals workflow in meetings** refine the process, and **Circle rights** decides whether circles may override it.

## Open decision settings

You need administrator rights.

1. In the **Structure** app, click **Structure settings** at the bottom of the left sidebar.
2. Click **General**.
3. Open the **Decision settings** tab.

![The Decision settings tab in Structure settings, with the left sidebar, the tab bar including a Holacracy tab, and the Proposal adoption card showing its switch and three adoption options.](/images/structure-governance/what-are-decision-settings/01-decision-settings-tab.png)

## Proposal adoption

**Require proposals for governance changes** decides whether a governance change is submitted as a proposal or applied at once. While it is on, a change creates a proposal. Switch it off and a change takes effect as soon as it is submitted, with no review round. An organisation created from scratch starts with the switch off; an organisation migrated to Talkspirit keeps the settings it arrived with.

Under **When are proposals adopted?**, choose what happens to a proposal submitted outside a meeting:

- **N days after submission, if nobody objects**: the proposal opens a consent round with the circle's decision makers and is adopted when the period ends without an objection. The field accepts a whole number from 1 to 365, and an organisation created from scratch starts at 2. When the circle has at most one decision maker, there is nobody to object and the proposal is adopted on submission.
- **As soon as they are submitted**: the proposal is adopted the moment it is submitted, with no review period.
- **Only in a governance meeting**: submitting starts nothing. The proposal stays open until someone adds it to a governance meeting with **Bring this proposal to a governance meeting**, where the meeting decides it, or withdraws it. This option belongs to the Holacracy add-on and is offered only while the add-on is on. Without the add-on it is absent, whatever your organisation has stored: a saved **Only in a governance meeting** then runs, and is shown, as **N days after submission, if nobody objects**, with the number of days saved on the card, or 2 if none was ever saved. Nothing is rewritten, so switching the add-on back on brings the option and your saved choice back. See [Holacracy add-on overview](/en/structure-governance/holacracy-add-on-overview).

A proposal raised during a governance meeting is always decided by the meeting, whichever option is selected.

The adoption options stay editable while **Require proposals for governance changes** is off, under the hint **Used when a circle requires proposals**: a circle that turns proposals on for itself inherits them.

## Draft proposal access and meetings

**Draft proposal access** sets who can see and edit a proposal while it is still a draft: **Only the author can edit**, **Author and circle leads can edit**, or **All circle members can edit**. A proposal that has been submitted stays visible to the circle even if it returns to draft.

**Proposals workflow in meetings** applies only to a proposal decided during a live governance meeting. **Present and decide**, the default, lets the facilitator adopt or reject straight after the presentation. **Full validation workflow** runs the complete present, clarify, react, object and integrate sequence. This card also belongs to the Holacracy add-on and is shown only while the add-on is on. Without the add-on the card is absent, whatever was saved: a saved **Full validation workflow** runs as **Present and decide**, with no objection round, until the add-on is switched back on, when the card and the saved choice return.

![The Draft proposal access card with its three options and its note about submitted proposals, above the Proposals workflow in meetings card with Present and decide selected.](/images/structure-governance/what-are-decision-settings/02-draft-access-and-meeting-workflow.png)

## Circle rights

The **Circle rights** card holds one switch, **Allow circles to override these settings**, on by default. While it is on, each circle can set its own **Require proposals for governance changes**, its own number of days before adoption and its own **Draft proposal access** on its **Decision settings** tab. The adoption option itself and the meeting workflow are set for the whole organisation, and every circle inherits them.

Switch it off and only the organisation can change these settings. A circle's **Decision settings** tab then reads **Your organisation manages these settings, so this circle cannot override them**, and any new override is refused. A circle that already set an override keeps it until it returns to the organisation's default: switching the lock off rewrites nothing.

Neither this card nor **Draft proposal access** depends on the Holacracy add-on. Each card saves on its own, and its **Save** button activates once something on that card has changed.

## Who proposes and who objects

Creating a proposal in a circle requires the **Decision maker** flag on an active assignment in that circle. Administrator rights alone do not grant it. Every new circle member starts as a decision maker, so the flag is something you remove rather than something you award.

When a decision maker declines a proposal, a written reason is always required. No setting makes it optional.

## Settings for a single circle

A circle can depart from the organisation's defaults while **Allow circles to override these settings** is on. On the circle's own settings page, the **Decision settings** tab repeats the organisation's cards. Each overridable control carries a **Use org default** switch, and **Reset to org defaults** returns the whole circle to the organisation's settings at once.

Whether a working agreement goes through a governance proposal is set per document type in **Structure settings → Working agreements**, not here.

## What's next

- [Proposals Overview](/en/structure-governance/proposals-overview)
- [Setting up consent decision-making for my organisation](/en/structure-governance/how-to-set-up-consent-decision-making-for-my-organization)
- [Decision makers in a circle](/en/structure-governance/what-is-a-decision-maker-of-a-circle)
- [Personalising a circle's settings](/en/structure-governance/personalizing-your-circles-settings)
