To maintain content quality and compliance, Rekonnect implements a publishing and approval workflow that separates content creation from final release. Every new or updated item must pass through a designated approval process, where authorized reviewers verify its accuracy and readiness. This workflow strengthens content integrity, prevents unauthorized changes, and ensures that users always access trusted, verified information.
Version control is present in the workflow for creating products, training packages, courses, forms and documents (all under content).
📌 Note: publishing approval of content, and approval of user registrations are not handled by the same controls or customisation. This document details the publishing approval of content, for more information on approval of user registrations see 3.7 auto-approve registrations.
Protection to prevent confusion with outdated content
Rekonnect ensures that:
Only one version of an item is published at any time.
Older versions are automatically archived when a new one is published.
Archived or Published items cannot be accidentally re-opened for editing.
How does Rekonnect manage content approval?
Before content becomes publicly available, it must pass through a clear approval workflow to ensure compliance and quality. The stages are:
Creating → Waiting for Approval → Approved → Published → Archived
Two available workflows:
There are two similar but fundamentally different workflows detailed here:
A self-approval workflow (where a user can approve and publish their own changes without requiring external approval).
Strict approval workflow (where an admin must review and approve content before publishing).
📌 Strict approval can be de-activated in general settings under the general tab and labelled "Approval steps". De-activating strict approval removes the need for an additional approver, and leaves the approval workflow in the self-approval mode.
Who approves new or updated content?
When strict-approval is activated, only administrators with explicit "Approve" permissions can approve content. Authors must select approvers when submitting their work for approval. When strict-approval is de-activated admins can approve and publish their own changes.
📌 When content enters the "Waiting for Approval" state, all selected approvers are notified via email that their review is needed. The workflow can therefore only progress to "approved" when one of the approvers approves the content.