Praisma Hub LogoPraisma Hub

Workflows & Approvals

Workflows in Praisma Hub define how content moves from draft topublished. They provide visibility, accountability, and governance for teams that require multi-step approvals, compliance checks, and auditability.

Default Workflow States

Every tenant comes with a standard editorial workflow. States can be customized per content type.

  • Draft: initial creation, editable by author.
  • In Review: submitted for peer or manager approval.
  • Approved: content has passed review and can be scheduled or published.
  • Scheduled: queued for a future publish date.
  • Published: live and visible in API & integrations.
  • Archived: retired but kept for record-keeping.
  • Rejected: sent back to author with notes.

Roles & Permissions in Workflows

Who can transition between states depends on role-based permissions. For example:

  • Editors can move items from draft → in_review.
  • Admins and Owners can approve, schedule, or publish.
  • Custom roles may add fine-grained control (e.g., “Legal Reviewer”).

Approvals

Approvals ensure that sensitive or high-visibility content is checked by the right people before publishing. Options include:

  • Single approval: one reviewer must approve.
  • Dual approval: two different reviewers must approve.
  • Conditional approval: e.g., legal approval required if content mentions certain keywords.

Using Workflows in CMS

  1. Create or edit an entry in CMS → Content.
  2. Click Submit for Review to move it to in_review.
  3. Reviewers add comments and either Approve or Reject.
  4. If approved, the entry can be Scheduled or Published.

Using Workflows in Social Posts

The same workflow logic applies to Social → Posts. Drafts go through review before being scheduled or published to connected social channels.

Notifications

Team members receive notifications when workflow state changes affect their assigned items. Notifications can appear in-app and via email or Slack (if integrations are enabled).

Audit Logs

Every workflow transition is logged with timestamp, user, and action. Admins can review these logs for compliance and accountability.

Best Practices

  • Define clear rules for who approves what content.
  • Use dual approval for high-stakes or compliance-critical content.
  • Leverage notifications to avoid bottlenecks in reviews.
  • Regularly review and refine workflow states as your team grows.