> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gedonus.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Approval Workflows

> Formal review and sign-off before decks leave the team.

<span style={{display:'inline-flex',alignItems:'center',padding:'4px 12px',borderRadius:'5px',border:'1px solid oklch(0.73 0.09 93 / 0.48)',background:'oklch(0.958 0.048 93)',color:'oklch(0.37 0.105 93)',fontSize:'10px',fontWeight:'600',letterSpacing:'0.1em',textTransform:'uppercase'}}>Upcoming Release</span>

## Overview

Approval Workflows will add a structured sign-off layer to the presentation review process. Before a deck can be sent externally, it must pass through one or more defined approvers — each of whom reviews the current version and either approves or requests changes.

Every approval is logged in the version history, creating a permanent, auditable record of who reviewed what and when.

***

## Designed for finance teams

The current review process is informal: a deck is sent over email, the reviewer makes comments or edits directly, and it is unclear whether the final version reflects all feedback. There is no record of who signed off.

Approval Workflows replaces this with a process that is:

* **Explicit** — reviewers are assigned, not just cc'd
* **Traceable** — every approval or rejection is timestamped and tied to a specific version
* **Non-bypassable** — a deck cannot be sent out without completing the required approvals

***

## Planned workflow

<Steps>
  <Step title="Define an approval chain">
    Set up one or more approval stages (e.g. Associate → VP → MD). Each stage has one or more required approvers.
  </Step>

  <Step title="Submit for review">
    When a version is ready, click **Submit for approval**. Approvers receive a notification.
  </Step>

  <Step title="Approvers review">
    Each approver opens the deck, reviews the diff since the last approved version, and either approves or returns with comments.
  </Step>

  <Step title="Approval logged">
    A completed approval is signed, timestamped, and stored in the version history. The deck is cleared for distribution.
  </Step>
</Steps>

***

## Planned integrations

* **Email** — notification when a review is requested or completed
* **Slack** — optional notifications to a configured channel
* **Compliance export** — PDF approval report for audit purposes

***

## Get notified

<Card title="Request a demo" icon="calendar" href="https://gedonus.com/#demo" horizontal>
  Tell us about your approval process and we will keep you updated on this feature.
</Card>