# Policies

> Organisation-level rules that constrain what members can publish, and how public they can make it.

Policies are rules the organisation sets that individual members cannot
override. They are enforced at the point of publishing.

Editing them needs `policy.update`.

## Classification

A classification caps how public a piece of content may be. Where one applies,
the Publish step will not offer a visibility above the ceiling, and says why.

## Publish approval

Publishing can require a second person. Where it is on, publishing becomes a
submission and the content waits in
[Reviews](/foliums/blueprintr-user-guide/teams/reviews-and-approvals) for someone with
`blueprint.review` to approve.

The same setting exists per folium, so documentation can require approval while
blueprints do not, or the reverse.

## Where policy wins

> [!IMPORTANT]
> Policy always beats a member's choice. If a member sets a blueprint to public
> and a classification forbids it, the blueprint does not publish publicly. The
> conflict is reported at publish time with the reason.