> For the complete documentation index, see [llms.txt](https://docs.powertable.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.powertable.com/explore-powertable/approval-flow.md).

# Approval flow

PowerTable can connect to your database live for real-time data updates and synchronization. While row and column-level access permissions ensure data integrity, you can go one step further to secure your data by setting up approval workflows.

In a team, users might need management's approval before making any data changes to ensure correctness and accuracy. There can be scenarios like multiple users accidentally changing the same data, entering incorrect values, etc. All these can be streamlined by setting up an approval workflow process in PowerTable.

## 1. Approval flow sequence

Whenever a change is made,&#x20;

:ballot\_box\_with\_check: Approvers receive an email about the change request with a link to the table.

:ballot\_box\_with\_check: Changes are indicated in the table based on how they have been set to be handled.

:ballot\_box\_with\_check: Approvers review the log in the 'Review' tab and choose which changes to approve or reject.&#x20;

:ballot\_box\_with\_check: Author is notified via email about approval or rejection.

:ballot\_box\_with\_check: Approver can also propose changes to the author.

:ballot\_box\_with\_check: Author implements or skips the suggested changes and sends it again for review.

:ballot\_box\_with\_check: Approved changes are synced to the source.

This section explains all of the above in detail.

## 2. Steps to set up approval workflow

1. [Enable Approvals in PowerTable](#id-3.-enable-approvals)
2. [Select a method to choose approvers](#id-4.-select-approvers)
3. [Set up the way to handle the changes](https://docs.powertable.com/explore-powertable/approval-flow/handling-changes-before-approval.md)

Once enabled, every change made by users undergoes an approval process before getting saved and synced to the source.

## **3. Enable Approvals**

You can turn on the approval workflow by following the steps below:

1. Click on **Approvals.**

<figure><img src="https://1781349671-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKyXRCFh0c08ryiUFvyMV%2Fuploads%2F5HtsNlRKaA8Zj2PZ2OS7%2Fimage.png?alt=media&amp;token=51326399-b1a4-48d6-98ed-f2c3ae7fcc5b" alt=""><figcaption><p>Click 'Approvals'</p></figcaption></figure>

2. Click **Configure Approvals.**

<figure><img src="https://1781349671-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKyXRCFh0c08ryiUFvyMV%2Fuploads%2FhzDPHld3Er47sCha0rUL%2Fimage.png?alt=media&amp;token=38b93744-6393-4c2a-bc9f-30ae2e805906" alt=""><figcaption><p>Configure Approvals</p></figcaption></figure>

3. Enable approvals by toggling on the highlighted button.

<figure><img src="https://1781349671-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKyXRCFh0c08ryiUFvyMV%2Fuploads%2FoA3XiGxEpQV9lzmtnDTG%2Fimage.png?alt=media&amp;token=334f3e22-d143-4964-af13-03b5e3e6c524" alt=""><figcaption><p>Enable approvals</p></figcaption></figure>

## 4. Select Approvers

The next step is to select the approvers who will review and approve any changes made to the table.&#x20;

There are three ways to select approvers.&#x20;

1. [**User Approvals:**](https://docs.powertable.com/explore-powertable/approval-flow/user-based-approvals.md) Manually entering the email IDs of approvers or IDs of AD groups (Active Directory Groups).
2. [**Rule-based Approvals:**](https://docs.powertable.com/explore-powertable/approval-flow/rule-based-approvals.md) Configuring a rule-based system to identify the approvers.
3. [**Approval using a Lookup Table:**](https://docs.powertable.com/explore-powertable/approval-flow/approval-using-a-lookup-table.md) Using a lookup table to establish the rules.

A detailed guide to each method is available in the upcoming sections.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.powertable.com/explore-powertable/approval-flow.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
