Skip to main content
Approval Flows govern exactly how a Proposal or Spend Request transitions from submitted to approved. 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 (APPROVE) from all eligible voters.
  • CONSENT: (Recommended) The proposal passes automatically after a defined time limit, unless a valid objection is raised (BLOCK).

​
Objections and Integration

In a Consent-based flow, the primary way to stop a proposal is by raising an Objection. When a user selects BLOCK (Object) on an active proposal, they must provide the reasoning. Corgtex records this objection and halts the timer. 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 passes.

​
Automation and Time Limits

Every active Approval Flow has an expiration. If a policy is set to a 48-hour Consent window, and 48 hours pass without any un-resolved objections, Corgtex’s background worker automatically transitions the Proposal to APPROVED and executes the requested database mutations safely. This guarantees that proposals don’t stagnate for weeks waiting for someone to “sign off.” Silence means consent.