# You decide what a client can touch.

> Every field category on your site carries a permission level. Open lets the client edit freely. Warn asks first. Review hides it and sends it to you. Locked blocks it entirely.

## Why the boundary holds.

- **Set once, holds everywhere:** A guard is a policy on a field category, not a rule you repeat per page. Set headings to Warn and it holds across the whole site.
- **Code only gets stricter:** Structural and code fields start at Review and can be tightened. There is no setting that opens them to a client.
- **Search-facing fields ask first:** Page title, meta description and the on-page heading default to Warn, so a client is told what they are about to affect.
- **Nothing silently fails:** A blocked request is not an error message. It is held and routed to you with the client's own words.

## From default policy to your policy.

1. **Mapping assigns defaults** When a site connects, every editable field is sorted into a category with a sensible starting level.
2. **You adjust the policy** Settings has one control per category. Change a level and it applies to the next edit.
3. **The client edits inside it** Open fields go straight through. Warn fields show a heads-up. Review fields are never offered.
4. **Anything stricter routes to you** A Review or Locked field becomes a request in your inbox instead of a dead end for the client.

## Use cases

- **A brochure site for a cautious client:** Leave body content, links and images open, keep titles and headings at Warn, and the client can do everything they actually need.
  > The defaults already read this way: body content, links and images Open, page title and meta description Warn, structural and code at Review.
- **A site where SEO is the deliverable:** Move page title and meta description to Review, so every search-facing change comes through you first.
- **A client who has broken something before:** Set the categories you do not trust to Review. They can still ask, and you still get the request.
- **A site still under construction:** Tighten everything while you build, then open it back up at handoff.

## FAQ

### What are the four levels?

Open, the client edits freely. Warn, editable with a heads-up before publishing. Review, hidden from the client and sent to you as a request. Locked, hidden and blocked entirely, chosen per field.

### Can a client get around a guard?

No. The level is enforced when the edit is applied, not just in the interface. A hidden field is never offered, and a blocked field is refused rather than written.

### What happens to a field I set to Review?

The client does not see it as editable. If they ask for a change that would touch it, the request is held and sent to you with their message attached.

### Can I open the code fields if I decide I want to?

No. Structural and code fields can be tightened to Locked but never opened below Review. That floor holds whatever else you configure.

---

- [All features](https://cmsbrew.com/features)
- [Chat editing](https://cmsbrew.com/features/chat-editing)
- [Escalations](https://cmsbrew.com/features/escalations)
- [Publish and revert](https://cmsbrew.com/features/publish-and-revert)