imbahub
Menu +
US
Talk to us
IMBAHUB / Platform

Make approval refer to the content that actually goes live.

An approved task is insufficient if the content changes before publication. ImbaHub can implement a focused workflow between editing, approval and publishing. We establish what the actual installation can enforce and what needs development. This is a separate project, rather than a claim that every Imba CMS installation already provides approval workflows.

Three pieces of evidence behind valid publication approval
  1. Version

    Reviewed content is identified.

  2. Decision

    The right person approves under the change rule.

  3. Public check

    The delivered page matches the intended version.

An approved task and a verified public page are separate checkpoints.

A condition changes after approval. Should the old decision always remain valid?

Not without an explicit rule. Identify the edit and follow the agreed re-review or version-locking process.

Connect a decision to an identifiable content scope

Start with one page type and identify the fields, languages, images and relationships covered by review. Approving body text does not automatically approve a subsequently changed call to action or document link.

Fictional example: a team approves a service page's scope. An editor then changes an important condition. The workflow needs to detect that change and follow an agreed review rule, rather than silently retaining an old green approval badge.

Choose change rules and publishing permissions

Define which changes invalidate approval and which version may be published. One model could lock an approved snapshot; another could require review when selected fields change. The choice must be technically enforceable and understandable to editors.

Check roles and publishing actions on the actual execution route. Hiding a button or writing an instruction does not enforce a technical restriction. Include automated builds and integrations that might otherwise bypass the workflow.

ElementDecision before implementationAcceptance evidence
VersionWhat does the reviewer approve?Clearly identified evidence
ChangeWhat needs a new decision?Relevant edits are detected
PermissionWho may execute publication?Intended role works; prohibited action stops
TimingImmediate or scheduled, in which timezone?Intended version at the intended time
DeliveryWhen does published mean published?Actual public page matches approval

Treat scheduling as its own delivery capability

CMS products and extensions handle scheduled entries differently. A queued release may refer to a changeable record rather than a frozen snapshot. Do not assume that selecting a time freezes the reviewed content.

Where scheduling is required, define date, time, timezone, cancellation and failure ownership. A started job is not a published page. Build, deployment and any cache need checking within the agreed delivery chain.

Hand over a workflow the team can practise

An initial delivery can cover one content type, one review step, an explicit version rule and one publishing route. Additional languages, batch publication and external systems expand scope. Review product capability and licensing against the actual installation.

Handover includes decision mapping, role checks, change cases, failure handling and retest instructions. We propose scope and price after review. Show a common change and who must be able to stand behind its public version.

Sources and further reading

Questions, answered

Does every change need several reviewers?

No. Start with actual responsibility and content risk. A small working step may be more useful than an elaborate chain.

Can we assume a scheduled job uses the approved version?

No. Establish how the installation selects content at execution time and test changes after scheduling.

IMBAHUB

Let’s plan your website

Show one content type, a post-review edit and your actual publishing route.

Talk to us
Existing English product interface with fictional demonstration content; reused for the US website.

Existing English product interface with fictional demonstration content; reused for the US website.