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

# Approvals and autonomy

> Choose what Alder does on its own and what waits for a person.

## Who approves routine emails

On the **Policy** page, an owner chooses:

* **Approve**: a person approves each email before it’s sent.
* **Autonomous**: Alder sends routine emails on its own, within your policy.

## Per-action permissions

Each kind of action can be set to **Off**, **Draft** (a person approves) or **Auto**:

| Action | |
| - | - |
| Reminder emails | |
| Replies to customers | |
| Sending documents (invoice copies, W-9s) | |
| Calls | |
| Recording promises to pay | |
| Recording disputes | |
| Notes | |

**Asking a person** can never be turned off.

> [!WARNING]
>
> Credits, refunds, write-offs and changes to bank details always go to a person, whatever your settings.

## Limits

Your policy sets how often Alder may contact a customer (touches per week and minimum days between touches), a calling window, and customers Alder must never call.

## Your collection policy

The policy sets stages by days from the due date, a tone for each stage (from friendly to final), escalation tasks, a send window (weekdays, in the customer’s time zone) and email caps. The standard policy allows at most 1 email a day and 3 a week per customer.

Upload a PDF (up to 5 MB) or paste your policy, and Alder drafts it. An owner reviews and **activates** it; importing never activates anything. Every version is kept with its history.

## Approving in Slack

Draft cards in Slack have **Send**, **Edit** and **Don’t send**. Deciding a draft needs the approver role. A draft that isn’t decided expires after 14 days.


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