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
- Editorial publishing teams
Editorial publishing teams
A publishing team can use the item number as the shared reference for authors, editors and publication operators. Category definitions give editors a consistent place to record the content type, and the revision strip shows which source was reviewed.
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 publishing team can use the item number as the shared reference for authors, editors and publication operators. Category definitions give editors a consistent place to record the content type, and the revision strip shows which source was reviewed.
Use one organization and a small set of active categories. Assign an owner to each item and agree how a reviewed item moves to the publication date. An editor can inspect the review decision and published link before reporting that a release is complete.
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.
Choose a release that can be checked at its destination. The operator records the returned link, and the reviewer can trace the exact revision behind the published copy.
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.