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
- Features
- Categories
Categories
Keep definitions tied to the owning organization.
OverviewActive categories×
Content Management System · Categories
New
Active categories
Content categories
| Name | Code | Organization | Effective from | Effective to | |
|---|---|---|---|---|---|
| Category 991 | CDE-438 | ORG-9306 | 26 Oct | 03 Nov | |
| Category 459 | CDE-435 | ORG-9999 | 03 Oct | 10 Oct | |
| Category 757 | CDE-308 | ORG-5518 | 12 Oct | 17 Oct | |
| Category 602 | CDE-995 | ORG-8023 | 05 Oct | 09 Oct | |
| Category 251 | CDE-291 | ORG-2571 | 13 Oct | 16 Oct |
6 of 6 records
Category 991Content categories · CC-10257
CodeCDE-438
OrganizationORG-9306
Effective from26 Oct
Effective to03 Nov
What you can do
Keep definitions tied to the owning organization
A category gives the editorial team a common definition before anyone drafts an item. The administrator enters its name and code, associates the organization and records when the definition applies. An operator then selects that category for a content item. This link makes a change to editorial policy visible at the place where an item starts, rather than leaving each author to interpret a loose label.
How the work is organized
- Define ownership. The administrator ties each category name and code to the organization that uses it.
- Set applicability. Active state and effective dates help the operator choose the right definition for the planned publication.
- Carry the definition forward. The selected category stays linked to the item through review and publication.
What to agree during setup
Check whether the organization is active and which category definition applies on the intended publication date. A category with an effective period should be reviewed before work is queued against it. The administrator also records the policy reference when a definition comes from an agreed editorial rule.
The team should rehearse its access rules with an operator, reviewer and administrator. Use an item from one organization and confirm that each person can see the record needed for their part of the work. Decide who resolves an ambiguous result and which person makes the final editorial decision.
Check the handoff on an actual case
Suppose an organization uses a category for public service announcements. The administrator enters the definition and confirms the organization. The operator opens a new content item, assigns an owner and chooses the category. At review, the reviewer can see which definition the item followed. If the definition changes later, the item still has its own revision and decision trail; the team should decide whether new content needs a different category record or an updated definition.
Before calling the handoff complete, compare the item status with its linked evidence and decision. The next person should be able to find the reason for the current state without relying on a message outside the record. If work must go back, assign a named person and preserve the previous outcome. Use the item number in the handoff so the recipient opens the same record, and check that the source revision still matches the decision under discussion.
What your team sees
- Active categories — Find active definitions by organization and effective date.
- Content Items Workspace — Inspect the selected item with its revision strip, decisions, state history and operation trace.
Follow the work through
Follow the editorial handoff and use the data model to check how the records connect.
What it keeps track of
Data model- Content categories
- Published content categories and editorial definitions offered by an organization.
- Organizations
- Agencies, departments and service organizations that own public services and cases.
- Content items
- Editorial content items tracked through revision capture, independent review and publication.
- Source mappings
- Reviewed field mappings and transform rules between source payloads and target fields.
Who uses it
Permissions- Content Management System Administrator
- , Content Management System Operator.
Set up Content Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.