ExplanationUnderstand the concepts

Understanding My Content

My Content is your personal area in a portal, where the content you produce collects before it is shared more widely. When you create an adaptation from a template, the result lands in My Content, and this is where you take it through review, approval, and publication. This page explains what My Content holds, how an adaptation moves from produced to published, and how that path relates to Collaboration Hub.

What My Content holds

My Content keeps the content you have produced in one place, separate from the shared assets in the DAM.

It has two parts. Your adaptation views list the adaptations you have produced, digital and print, including ones still rendering. Files holds the adaptations you have promoted, which are ready to enter a review and be acted on once approved. Promoting is the step that moves an adaptation from your adaptation views into Files, as described in Promoting adaptations.

Promoting adaptations

An adaptation starts out in your adaptation views. Before it can be reviewed, you promote it, which moves it into Files and marks it as ready to enter a review. Promotion works the same way for digital and print adaptations, so both kinds join a single, consistent process from this point on.

Promoting depends on the access an administrator has granted you. Without it, the Promote action does not appear, and you can only download or delete. To promote an adaptation, use Promote adaptations.

The review-and-approval lifecycle

From Files, one or more promoted adaptations can be sent for review. Each review runs against a defined process: an administrator configures the stages a review passes through and the people involved at each stage, and a new review is created from one of these presets. Reviewers open Review Studio to annotate the content and add comments, but only the review’s decision makers approve or reject it. A review finishes once the decision makers have decided on every asset: if the content is approved the review is marked complete, and if it is rejected it is aborted.

This is the adaptation route into review. It is one of two ways work reaches the same review-and-approval process; the other is a project in Collaboration Hub. Reviews raised either way appear together in the portal’s Reviews list.

Acting on approved adaptations

Approval acts as a gate. Until an adaptation is approved, the actions that send it onward stay locked; once it is approved, those actions become available:

  • Publish to the DAM, where the approved asset enters the shared library and becomes a governed, reusable asset, rather than an output sitting in your workspace. Publish adaptations to the DAM gives the steps.

  • Distribute to connected channels, so the content is delivered to the destinations your organisation has already integrated. Distribute adaptations gives the steps.

  • Share, by adding the adaptation to a share or enabling a shareable link for people outside the platform. Share adaptations gives the steps.

Publishing to the DAM is the step that turns an approved adaptation into an asset that everyone with access can find and reuse.

How My Content relates to Collaboration Hub

My Content and Collaboration Hub feed the same review-and-approval workflow from two different starting points. My Content is the adaptation route: you produce an adaptation, promote it, and send it for review on its own. Collaboration Hub is the project route: a brief drives what is produced, assets are attached to a project, and the whole project moves through a workflow together. Whichever route work takes, reviews surface in one place and approved content is published to the DAM, distributed, or shared in the same way.