# A real change deserves a clear review.

> Headful keeps preparation, approval, and the result together so you can tell what is proposed and what Salesforce confirmed.

Canonical: https://headful.cloud/docs/reviewed-changes

## From draft to effect.

Agent access, a plugin installation, and a selected org do not approve a provider write. Supported changes include user creation, permission-set assignments, and bounded custom permission-set definition edits. Lead viewing remains read-only.

1. Prepare the supported change in a saved workflow.
2. Review the exact org, target, fields, and effect in Headful.
3. Explicitly choose Create or Apply for that operation.
4. Read the Salesforce result and retained receipt before continuing.

## A changed draft needs a fresh review.

Reviews are tied to the exact draft and connection context, expire, and can be used only once. If relevant state changes, Headful rejects a stale review instead of applying the earlier version. Reopen the workflow, inspect the updated details, and prepare a fresh review.

## Partial success is still success worth keeping.

A confirmed user remains created when later access setup fails. Independent assignments can succeed or fail separately. Headful preserves confirmed progress and shows what remains, so you can continue from the evidence.

## An uncertain outcome needs inspection.

If a response leaves the write outcome unknown, do not assume the change failed. Use supported reconciliation or inspect Salesforce directly. An unknown operation is not blindly replayed. A reversal needs its own reviewed change.

- [Troubleshooting](https://headful.cloud/docs/troubleshooting)
- [Security](https://headful.cloud/security)

## Early access

Headful is a free Mac beta, Salesforce first. Public stable distribution is not available yet. [Join early access](https://headful.cloud/#waitlist).