# Your client says it. The site changes.

> No fields to hunt for and no dashboard to learn. Your client types the change like a text, and sees it on the real page.

## Why clients actually use it.

- **Nothing to learn:** There is no admin interface to train a client on. If they can send a text message, they can edit the site.
- **It finds the text:** The client does not need to know which page or component holds a phrase. They describe it and the editor locates it.
- **It never writes code:** Every edit is a new value for a field that already exists, so a client's typo cannot become a broken build.
- **Nothing to install:** No plugin, no app and no password. The client opens a link and starts typing.

## From a sentence to a published change.

1. **Open the site** The client picks the page they want from the list of pages you allowed them to see.
2. **Say what to change** They type it in plain words, the way they would ask you for it.
3. **See it on the page** The pending change is painted onto the real deployed page before anything ships.
4. **Publish** One click sends it live. Anything out of scope comes to you instead.

## Use cases

- **The phone number changed:** The three-minute job that used to arrive as an email to you. The client does it themselves instead.
  > “Our new number is 555 0134” updates the header, the footer and the contact page together, in one publish.
- **Seasonal copy:** Holiday opening hours, a price change, a new staff name. Small edits that carry a deadline.
- **A typo on a Sunday:** The client spots a mistake at the weekend and fixes it at the weekend, without finding you first.
- **A fresh headline:** Swapping the wording on a hero or a section, and seeing it at the real width before it goes out.

## FAQ

### Does the client need an account they have to manage?

No. You invite them, and they sign in with Google or a six-digit code emailed to them. There is no password to keep and nothing to install.

### What happens if the client asks for something the editor cannot do?

It is refused in the editor and routed to you with their original message attached. The client is not left guessing, and you get the request in their own words.

### Can the client edit anything they want?

Only what you allow. Every field category carries a permission level you set, and structural and code fields can never be opened to a client.

### Can I see what the client changed?

Yes. AI edits, publishes and escalations are listed in the activity trail with the person and the time attached, and every publish is a labelled commit in your own repository.

---

- [All features](https://cmsbrew.com/features)
- [Inline editing](https://cmsbrew.com/features/inline-editing)
- [Real-site preview](https://cmsbrew.com/features/preview)
- [Escalations](https://cmsbrew.com/features/escalations)