Sitecore Content Hub CMP: A Technical Overview of Content types, Triggers and Actions, Taxonomies, State flows and Roles

Sitecore Developer
  • Twitter
  • LinkedIn

Sitecore Content Hub's Content Marketing Platform (CMP) gives marketing teams one place to plan, write, review, and publish content. Content types and taxonomies are quick to configure; workflows and permissions require most of the design and testing effort.

 

What CMP Is

CMP is the content module of Sitecore Content Hub. It manages a piece of content from its first idea to archive, including who requested it, who is writing it, where it is in review, when it goes live, and which channels it is intended for.

It sits alongside Content Hub's Digital Asset Management (DAM). Images and files live in DAM, and content items in CMP link to them rather than maintaining separate copies. For many teams, CMP replaces a familiar process: drafts written in Word, feedback shared by email, and someone manually entering the final text into the website's CMS.

A CMP setup has five building blocks:

  • Content types: What kinds of content exist and which fields each one has.
  • Taxonomies: How content is tagged and found.
  • Assets: How images and files are attached.
  • Workflows: The states content moves through and who acts at each stage.
  • Roles and permissions: Who can see and do what.

 

Content Types

A content type defines a kind of content, such as a blog post or article, and the fields an author completes. Content Hub includes seven predefined types: Advertisement, Blog, Email, Recipe, Social media, Webinar, and White paper. The predefined Blog type has three fields: title, quote, and body. Custom content types can be added under Manage → Content types → Add type.

A few considerations are important when designing content types:

  • Shared entity: All content types use one entity, M.Content. Each type adds its own pair of field groups, such as Content (Article) and Article details. Fields appear only when an item belongs to that type.
  • Field names: Field names are tied to the schema and cannot be changed. A field called Title on the Article type is stored as Article_Title. Renaming it to Heading changes only the label displayed to authors. Integrations such as the Sitecore connector use the stored name, so field names should be agreed upon before implementation.
  • Field types: Fields can be single-line text, multiline text, rich text, or reference.
  • Validation: Fields can be required, have character limits, or restrict how many items a reference can point to.

 

Taxonomies

A taxonomy is a controlled list of values that users select instead of entering free-form text. Taxonomies are managed under Manage → Taxonomy. Values can be nested, for example, continent → country → state.

Content Hub also provides simpler option lists (Manage → Option lists) for small, fixed sets of choices, such as priority. Use a taxonomy for values that function as tags and need to support nesting, filtering, or mapping to the website.

 

Built-in Metadata and Shared Fields

Fields that should be available across all content types are configured under Content types → General members.

TabBuilt-in FieldsUsed For
StrategyAudience, Region, Channel accounts, Publication date, Brief and brief assets, Story pointsPlanning: who the content is for, where it goes, and when it is published.
DetailsName, Status, Campaigns, Locale, Tags, Expiration date, Content collectionsManaging and finding content, and retiring outdated items.

Channels such as Website, Email, and LinkedIn are preloaded. A channel account represents a specific destination, such as one website, so content can be planned and filtered by site.

 

Images and Files from the Media Library

Authors can attach images to a content item in two ways:

  • + Add → Add existing items: Selects assets from the media library. The picker shows assets that have already been approved in DAM.
  • + Add → Upload files: Uploads a new file directly to the content item.

Images can also be inserted into a rich-text field using its toolbar.

The brief has its own brief assets, providing a place for reference material such as the writer's original Word draft.

 

Triggers and Actions

A state flow defines a route, but content does not enter it until a trigger and action initiate the process. The trigger determines when something should happen, and the action defines what happens. Both are managed under Manage → Triggers and Manage → Actions.

A trigger monitors events such as an item being created, changed, or deleted, evaluates its conditions, and runs one or more actions. Its Conditions tab contains the rules, for example, Approved for creation equals on and Type contains Article.

The Actions tab lists actions grouped by execution stage: pre-commit, security, validation, audit, and post actions. Starting a workflow is a post action because it runs after the item is saved.

The components form a chain, with each connection configured through a specific field:

LinkWhere It Is SetThe Field That Links It
Trigger → ActionThe trigger's Actions tabPost action: the action's name
Action → State flowThe action's settingsType Start state machine, plus the state flow's name
State flow → First stateThe state flowIts first state, which assigns a group and displays that state's buttons

A disabled trigger does nothing. Saving a new trigger prompts the user to activate it. If the trigger is not active, items receive no workflow state or buttons.

 

State Flows (Workflows)

Content Hub refers to workflows as state flows, managed under Manage → State flows. Two are particularly important for CMP.

The Ideation flow (New → Pending approval → To do) approves an idea before content creation begins. The CMP flow then moves content from writing through publication:

StateButtonsMoves To
To doStartIn progress
In progressSend for reviewIn review
In reviewReject / ApproveIn progress / Ready to publish
Ready to publishStart over / ArchiveIn progress / Archived
ArchivedUnarchiveReady to publish

Each state lists the user groups assigned to it. By default, Editors are assigned to To do and In progress, while Approvers are assigned to In review. Assignment determines whose task an item is; it does not determine who can view it.

A state can also set an item's lifecycle status, which determines the columns displayed on the Work board. The flow can send notification emails when content changes state.

 

Roles and Permissions

In Content Hub, permissions are not assigned directly to individuals. Users belong to user groups, and each group has a policy made up of rules, such as allowing Read, Create, and Update on Content. Rules can include conditions, such as allowing access only when Business unit is Marketing, or can be restricted to items created by the user.

A working CMP role typically requires several permission layers:

LayerWhat It Controls
Module access (Content, Media)Which parts of Content Hub the user can access.
Page access (e.g., M.Builtin.CMP.Everyone)Access to CMP pages, including Work, Calendar, and content details.
Content rules (custom group)Which items the user can read, create, and update.
Workflow state assignmentsWho can act at each workflow state.
Page component securityWho can see parts of a page, such as the state flow panel.

 

Testing Roles

Clear the cache (Manage → Cache) after changing a policy, as Sitecore advises. Otherwise, testing may return stale results.

Test permissions and workflows with real user logins. Impersonation is useful, but in our experience, it did not display workflow buttons. Each role should have a dedicated test account.