These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Content Management System
- Who it's for
- Public information teams
Public information teams
A public information team often needs to explain who approved a statement and when readers could see it. The item, source revision and reviewer decision keep those questions linked. Evidence documents can hold the source material that informed a notice.
How Content Management System is set up for you
Content ownership
Give each item a named owner and organization so the next handoff has a responsible person.
Review evidence
Keep source revisions, supporting documents and reviewer decisions beside the item.
Publication check
Compare the published link and completion record with the result the audience can open.
A public information team often needs to explain who approved a statement and when readers could see it. The item, source revision and reviewer decision keep those questions linked. Evidence documents can hold the source material that informed a notice.
Start with a category for each kind of notice and a named person for independent review. Rehearse a returned decision and a correction after publication. Keep the publication link and the follow-up resolution available for later questions.
Use the [prepare and review](/content-management-system/processes/prepare-and-review) process for the first editorial cycle. Then rehearse [publication](/content-management-system/processes/publish-and-reconcile) with one approved item. If the team already has published content to correct, use the [correction process](/content-management-system/processes/revise-and-correct) to retain the earlier decision and assign the remaining work.
Before go-live, agree who maintains category definitions, who prepares revisions and who makes the independent decision. Ask each participant to demonstrate their part from the item record. Check that an analyst can explain a completed case from the recorded revision, decision and published result.
For a public notice, ask the reviewer to compare the source document with the text readers will see. The operator should keep the publication link on the same item as that decision.
Features to start with
Roles on the team
- Content Management System Administrator
- Maintains approved configuration: record entry on Content Categories, read-only on all operational, review and provenance tables, and access to all four app pages. No schema editing, deletion, bulk operations or export grants.
- Content Management System Reviewer
- Reviews independent assigned work: record entry on Review Decisions only, read-only on every other table. Reviewers must not approve their own preparation; verify the reviewer-independence guard when activating the workflow.
- Content Management System Operator
- Prepares assigned work: record entry on Content Items, Content Revisions, Follow Up Actions and Evidence Documents, read-only on configuration, review and provenance tables. Verify organization-scoping guards when activating the workflows.
- Read Only Analyst
- Reads authorized summaries and aggregates across every table plus the four app pages. No record creation or editing, no schema or administrative capability.
Set up Content Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.