Skip to main content
Approval Flows govern how a Proposal or Spend Request collects review input before a final outcome is recorded. Corgtex provides a flexible policy engine. Different types of decisions or different Circles can be bound to different Approval Policies.

​
Approval Modes

When configuring an Approval Policy, you define the required mode:
  • SINGLE: Requires approval from a single designated role (e.g., the Finance Steward for small expenses).
  • MAJORITY: Requires a simple >50% vote from the eligible voters.
  • CONSENSUS: Requires unanimous agreement (AGREE) from all eligible voters.
  • CONSENT: (Recommended) The proposal is open for review during a defined window. People can mark it reviewed or raise a reasoned objection.

​
Objections and Integration

In a Consent-based flow, the primary way to stop a proposal is by raising an Objection. When a user selects Object on an active proposal, they must provide the reasoning. Corgtex records this objection so the team can integrate the concern before the proposal is resolved. The focus then shifts to Integration:
  1. The proposer and the objector engage in a discussion directly on the platform.
  2. The proposer can edit the draft proposal to address the concerns.
  3. Once the objector feels their concern has been integrated (the proposal is no longer harmful), they can Resolve their objection.
  4. If all objections are resolved, the proposal is ready for the resolver to adopt manually.

​
Automation and Time Limits

Approval Flow windows make review timing visible. For proposals, the current product treats approval input as advisory: the review window, vote counts, and objections are visible to the resolver, but the proposal only becomes adopted, not adopted, or withdrawn when someone uses the Resolve action. This avoids silent automatic adoption while still making it obvious which proposals are waiting for review.