Understanding Collaboration Hub
Collaboration Hub is the Storyteq CMP module for planning, producing, reviewing, approving, and publishing content work. It brings briefing, production, review, and approval into one workspace, so campaigns move from request to publication without falling back on scattered tools, emails, and spreadsheets. This page explains what Collaboration Hub is responsible for, how the content workflow fits together, and how it relates to the rest of Storyteq CMP.
What Collaboration Hub does
Collaboration Hub orchestrates the content workflow: briefs, production, reviews, and approvals. Where the DAM stores and delivers finished assets, and Adaptation Studio versions content from templates, Collaboration Hub is the workflow spine that brings a piece of content from an initial request through to an approved, published result.
Work is organised into projects. A project is a single workspace that holds everything a piece of work needs: its brief, deliverables, reference files, timeline, collaborators, comments, and decisions. Full version history and an audit trail are kept against the project, so teams can see what is in progress, what has been approved, and what needs action.
The content workflow
Every project follows the same path, from the initial request through to publication. The workflow has four stages: briefing the work, producing it, reviewing and approving it, then publishing the result. The exact stages, the people involved, and the requirements at each point are tailored to your organisation, so the process is consistent for a given kind of work every time.
Briefing
A project starts with a brief. When a project is created, you choose a project type, which applies the workflow stages, collaborators, milestones, and requirements that suit that kind of work. The brief is captured through a structured form: instructions, the deliverables required, dates, collaborators, and reference files, which can be pulled from the DAM or uploaded from your device. Once the brief is complete, it becomes the source of truth the rest of the project works from.
Production
With the brief agreed, the work moves into production, and the assets that will be reviewed are added to the project. These assets are not always adaptations produced from a template. Most often they are finished assets created outside Storyteq CMP and uploaded into the project, but they can also be assets drawn from the DAM, or adaptations produced in Adaptation Studio. The brief drives what needs producing; the assets are attached to the project so they can enter at the right stage in the workflow.
Review and approval
As the work progresses, assets move into review. Reviewers open Review Studio, where several people, internal or external, come together in one place to annotate assets, leave comments, tag collaborators, and compare versions side by side. Each review names its decision makers when it is created, and only they can approve or reject the content. Other reviewers still contribute annotations and comments, but do not make that final decision. Every annotation, decision, and version is tracked in the audit trail. Approval acts as a gate: the workflow moves an asset onward only once its decision makers have approved it.
Publishing
Once assets are approved, the final stage sends them where they are needed. Approved assets can be published to the DAM, where they become governed, reusable assets that everyone with access can find, or distributed to the channels your organisation has connected, such as social, CRM, or CMS platforms. Publishing to the DAM is the step that connects Collaboration Hub back to the rest of Storyteq CMP, turning an approved piece of work into a finished asset.
Where the content comes from
The content that flows through Collaboration Hub can come from several places: uploaded from a device, drawn from the DAM, or produced as an adaptation in Adaptation Studio. An adaptation is a piece of content produced from a template, such as a resized social banner or a localised print layout. Browse templates and create adaptations covers producing adaptations.
Collaboration Hub does not produce content itself. It holds the brief that defines the content a project needs, then orchestrates what happens to that content once it exists: getting it reviewed, approved, and out to where it is needed. This is why producing an asset and approving one are distinct activities. Producing an asset sets what the content is; Collaboration Hub sets the requirements it must meet, then decides whether it is approved and where it goes.
How Collaboration Hub is surfaced
Collaboration Hub appears in a portal through the Collaboration portal type.
The Projects page is the centre of Collaboration Hub. It brings together the projects you are involved in, with dashboard and timeline views that show what is in briefing, production, review, approval, or ready to publish, and what needs your attention.
The Reviews page brings every review together in one place. A review is a first-class item in its own right: it can arise from a project or from an adaptation, and both appear in the same list, so reviewers have a single place to find the work waiting for them. Reviews that start from an adaptation begin in My Content. Understanding My Content explains that route.
A portal can also include CMS Pages: general-purpose content pages for adding custom information, such as guidance or links. They sit alongside the workflow rather than forming part of it.