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

# Actions and approvals

> How the Co-founder proposes changes, how you approve them, and how much it may do on its own.

When the Co-founder recommends something concrete — new metadata, a review reply, an issue for your team — it doesn't just describe it. It prepares the exact change as an **action** and puts it in your queue. You decide.

***

## Review the queue

Open **App Co-founder → Actions**. Each card shows the change, why the Co-founder wants it, and the data behind it.

| Column | Meaning |
| - | - |
| **Pending** | Waiting for your decision |
| **Approved** | You said yes, but applying it failed or hasn't run yet. Safe actions retry automatically; use **Retry** for the rest. |
| **Applied** | The change went through |
| **Rejected** | You decided not to act. You can restore a rejected action. |

You can approve or reject one card at a time, or all pending cards at once. You can also decide from where the action reaches you:

* **Email**: each briefing email carries one-click approve and reject links for up to five decisions.
* **Slack** and **Telegram**: approval buttons on the message.
* **Chat**: **Approve** and **Skip** under the Co-founder's reply.

A pending action the Co-founder stops re-proposing for 14 days is retired automatically, so the queue stays current. A rejected idea comes back only when new evidence changes the case.

> [!TIP]
>
> **App Co-founder → Decisions** keeps the full history: every action, what you decided, and what happened next when it could be measured.

***

## What it can propose

| Action | What approving does |
| - | - |
| **App Store metadata update** | Updates title, subtitle, keywords or description in App Store Connect |
| **Review reply** | Posts a reply to an App Store review |
| **New version** | Creates an empty new version in App Store Connect for you to attach a build to. It ships nothing by itself. |
| **Google Play listing update** | Updates your Play store listing |
| **Linear issue / GitHub issue** | Opens an issue for your team |
| **Coding agent task** | Hands a scoped build task to your connected coding agent. See [Coding agents](https://docs.appeeky.com/docs/cofounder/coding-agents.md). |
| **Apple Ads / Meta Ads / TikTok Ads change** | Pauses or enables a campaign, changes a budget or bid, or adds negative keywords |
| **Monetization change** | Makes a RevenueCat offering the current one |
| **Win-back campaign** | Emails you a ready-to-run win-back plan |
| **UGC clip** | Starts rendering a short video with one of your personas (uses media credits). You approve the finished clip again before it posts. |
| **Slack summary, Notion page, webhook post** | Sends a summary to that destination |

***

## Read and write modes

**Settings → Automation → Agent mode** decides whether the Co-founder may change things outside Appeeky at all.

| Mode | What it can do |
| - | - |
| **Read** (default) | Analyze and propose. Every action waits for your approval in **Actions**. |
| **Write** | Also apply changes directly: App Store changes, issues, review replies |

### Autopilot level

**Autopilot level** sets how much runs without asking. Write access still needs write mode.

| Level | Behavior |
| - | - |
| **0** | Report only. No action queue. |
| **1** (default) | Suggests and drafts. You approve everything. |
| **2** | Opens Linear and GitHub issues automatically |
| **3** | Also saves metadata and version drafts when the evidence is strong |
| **4** | The most autonomy; high-impact changes still need approval |

### Auto-approve

Pick action types that skip your approval, such as Slack summaries or review replies. Auto-approve only applies in write mode; in read mode everything waits for you.

> [!WARNING]
>
> Some actions **always** need your approval, at any autopilot level and even when auto-approve is set: ads changes, monetization changes, win-back campaigns and UGC clips. Coding agent tasks never auto-approve by autopilot level; only an explicit auto-approve setting lets them through.

### Policy rules

**Settings → Automation → Policy rules** give you a hard override per action type:

| Rule | Effect |
| - | - |
| **Block** | Never run it. Blocked actions show in **Actions** with the reason. |
| **Require approval** | Never auto-approve it |
| **Log only** | Allow it, just note it |

For rules the Co-founder must follow in its recommendations — "never suggest removing the free tier" — use the hard rules in your [business profile](https://docs.appeeky.com/docs/cofounder/knowledge-base.md#business-profile).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.