Governance: keeping claims right and the brand consistent

The websites make safety and performance claims, so content needs checks a typical website does not. These controls work together.

Sign-offs

A content type can require approval in steps, such as Product safety, then Legal, then Brand. Each region can have its own steps, and a step can be limited to one role. The record keeps who approved each step, their role and the version they approved. Set them up in Schema › Content types › Approval.

Approval steps of your own are part of the Growth and Enterprise plans. A single review before publishing works on every plan.

Approved claims

Claims and disclaimers are written once per region in the claims library by people allowed to, and placed on pages by key. Changing the wording updates every page that uses it.

Review dates

Product pages can carry a review-by date. The owner is reminded before it passes, so claims do not quietly go out of date.

Consent on images

Before-and-after images carry a consent reference and approval status. Pages with an image that lacks consent cannot be published.

Brand components

A component can be locked, so only people with brand:manage can add, change or remove it, and can ask for a Brand sign-off when a page changes it. Set this on the component's page under Schema › Components.

Emergencies

An emergency banner skips review and schedules for urgent notices, but only for people allowed to, with a reason, and fully recorded.

The audit trail

Every change, approval and setting is recorded with who, when and what, under the organisation's Audit log.