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

# Autonomy

> How much Goosy may spend and do on his own in this workspace, who signs off on spending, and where test leads' emails go.

**Settings → Goosy → Autonomy** says what Goosy does on his own in this
workspace, and when he checks with you. Anything he asks for lands in
**Review** — **Open Review** at the top takes you there. See
[How approvals work](https://docs.goosybear.ai/how-approvals-work.md).

Owners and admins change these settings. Everyone else sees the same rows with
**View** in place of **Change**.

## Spending

The **Spending** block shows four lines: **Mode**, **This month**, **Your
approval before money is spent** and **Client sign-off**. Choose **Change** to
edit them.

### Mode

| Mode | What it does |
| - | - |
| **Ask me every time** | Goosy proposes, you approve. Every action that costs money stops for a sign-off. |
| **Work within an ad spend limit** | Goosy acts on his own up to the **Ad spend limit** you set — the most this workspace's ad spend may commit in a calendar month before an approval is required. Anything that would take the month past it stops for you. |
| **Describe it in your own words** | Write your boundaries in plain English, such as a monthly figure. **Check how Goosy reads this** shows the limit he took from it before you save. |

A second setting, the share he may shift onto an already-running campaign
without asking, sits under **More options**. Leave it blank for no limit of its
own.

**This month** shows what is already committed against the limit and how much
is left. If no limit is being enforced, it says so rather than showing a figure.
When the month is fully committed, Goosy keeps proposing but nothing new runs on
its own until the limit is raised, and the page offers to raise it. Goosy holds
a booking until the ad platform confirms what happened; the page lists any held
bookings and lets an admin release one.

### Who signs off

Under **More options**, two switches decide who says yes before money is spent:

* **Require my approval before money is spent** — Goosy prepares the ad or
  purchase and waits for your yes. Requests show up in Review.
* **Require a client sign-off too** — adds a second yes from your client before
  anything goes out.

## Spend envelopes and Every week

Two more blocks appear on this page only where they are switched on for your
account, and they are absent otherwise.

**Spend envelopes** — approve a capped, expiring ceiling once, and spend actions
that fit inside it stop asking. Anything over a cap, outside its scope, or after
it expires still stops for a sign-off. Under **Grant an envelope** you set a
total cap, a per-day cap and when it expires, and can narrow it to a provider
and destination. The table shows each envelope with the room left today and in
total. Caps cannot be raised or extended after the grant; that takes a new
envelope.

**Every week** — what Goosy does on his own each week for this brand. A switch
runs it every week or pauses it, and the block shows the next sitting. Below it:

* **What he makes each week** — posts and ad changes always come to your queue
  for your call (ad changes need a connected ad account). Video and clip ideas
  go either into the queue or straight to the board; research and the weekly
  performance check are either **Ask first** or **On its own**.
* **How you review** — **Review rhythm** is **Weekly brief** (one sitting,
  everything from the week in one place) or **Rolling** (items reach your queue
  as they are ready). **Publish approved items automatically** sends anything you
  approve out on its schedule with no extra step; off, approved items wait on
  the Schedule board; unset, this brand publishes the way the company already
  does.
* **What we measure** — **Optimise for** one number (cost per lead, cost per
  acquisition, return on ad spend, cost per booked call, list growth or cadence
  held), guardrails such as a maximum daily spend, and what counts as a result
  (read from your contacts, your calendar or your payments).

## Test address

**Test address** is where a test lead's emails go, so no real person receives
them when you test a page or a pipeline. A Mailosaur address or any inbox your
team owns is fine. Leave it blank and test leads stay off.


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