> ## 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.

# How approvals work

> The four things Goosy never does on his own — publishing, spending, deleting and granting access — how each stop works, and the one of them you can tune.

Four things never happen on an assistant's own judgement in Goosy Bear:

* **publishing** something
* **spending** money or credits
* **deleting** something
* **granting or changing access**

That is true whatever role you hold, and whether the request came from you
clicking or from an assistant acting on your behalf. No permission and no API
key widens it.

Three of the four always stop and ask. **Spending is the one you decide the
shape of** — it is bounded by a limit you set rather than by a fixed rule, and
the section below is about how that works, because it is the difference between
Goosy being useful and Goosy asking you about everything.

## Two different questions

It helps to keep two ideas apart, because they are enforced separately.

**Permission** answers *may this person do this at all?* It comes from your
role — Owner, Admin, Member or Client — plus any per-person exceptions an owner
or admin has set. See
[Who can use the API](/permissions) for how that works for programmatic access.

**Approval** answers *has a person said yes to this specific thing?* It is
about consequence rather than identity, so it applies even to an owner who
holds every permission there is. Having the right to publish is not the same as
having said "publish this."

## Publishing

Work Goosy makes does not go out when it is finished. It lands in **Review**,
the one queue where everything waiting on a decision collects — changes to
approve, finished pieces to sign off, assets to accept, and spend to authorise,
all in one place rather than four. Nothing publishes without a decision made
there, and the **Schedule** shows you what is going out and when.

This is the gate people notice most, and it is the one that makes the rest of
the product safe to delegate: you can ask Goosy for a week of content without
that being a decision to publish a week of content.

## Spending

Spending is the gate you configure. It lives under **Settings → Account**, in
the section called **Spending & approvals** — *"decide when Goosy checks with
you"* — and an owner or admin sets it.

### How much Goosy does on his own

One choice, three options:

| Choice                            | What happens                                                                                                                           |
| --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| **Ask me every time**             | Goosy proposes and you approve. Every action that costs money stops for a sign-off, and a standing budget never clears one on its own. |
| **Work within a monthly budget**  | Goosy acts on his own up to the monthly budget you set. Anything that would take the month past it stops for you.                      |
| **Describe it in your own words** | Write your boundaries in plain English. Goosy reads them into a monthly budget you can check before you save.                          |

The middle option is the one worth understanding, because it is the one people
are surprised by: under a monthly budget, work that fits inside it **runs
without asking you first**. That is the point of setting one. What the budget
never does is disappear — crossing it stops the work and brings it back to you.

If you would rather nothing at all moved without you, the first option is that
setting, and it overrides any budget.

### Required sign-offs

Two switches sit under the same section, independent of the choice above:

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

Turning either on sends those requests to **Review**, which is where they wait
for a decision. Nothing depends on somebody spotting a notification.

### Small runs inside a piece of work

Production work has a second, narrower version of the same idea. Re-running one
scene of a video costs a little, and doing it four times in a row costs four
times as much — so small runs proceed under a run-without-asking allowance, and
a run larger than the allowance covers stops and asks. The allowance counts a
whole video rather than each scene, which is what stops nine small runs adding
up to a large unattended one.

When one of those asks, it tells you the work costs credits and asks you to
confirm; it does not quote you an amount, because amounts are read from your
billing pages rather than recited in a dialog.

### From the API

Calling from your own tools does not inherit any of this. An action that spends
credits will not run in a single call: the first call answers with a summary of
what it would do and a confirmation id, and charges nothing; sending that id
back on a second call is what runs it. There is no single-call version.

## Deleting

Removing something is a person's decision, and the big removals are reversible
on purpose.

Closing a workspace or an account is scheduled rather than immediate: nothing is
removed for **30 days**, and one click calls it off at any point in that
window. Invoices, tax records and the record of which terms you agreed to are
kept even after a deletion runs, because the law requires them. This lives
under **Settings → Data**, and closing the whole account is an owner's decision.

See [Your data and privacy](/your-data-and-privacy) for what an export and a
deletion each cover.

## Granting access

Who can do what is changed by an owner or admin, by hand, under **Settings →
Members & invites**. Per-person exceptions stay visible in the member list, so
nobody has to remember who was given what, and a change takes effect on that
person's next action rather than at some later sync.

Support is the same shape from the other side: if support needs to look at your
account, you are asked, the answer is yours to give, and you can see who is
looking and stop it in one click under **Settings → Support access**. Nobody
looks without that.

## What this means in practice

You can hand Goosy a lot. Ask for a month of posts, a rebuild of a sequence, a
set of ads for a new offer — preparing it commits you to nothing, because
publishing it is a separate step and that step is yours.

Money is the one to set deliberately rather than leave at whatever it is. Spend
two minutes in **Spending & approvals** deciding how much Goosy may do on his
own, and you will not be surprised in either direction — by a charge you did
not expect, or by being asked about every small thing.

The corollary is worth saying too: if something you expected to happen has not
happened, the first place to look is whether it is waiting on a decision.
**Review** is where it will be.
