Currently, the Content Library moderation workflow is triggered only when changes are made to the Q&A text (question or answer fields). Updates made solely to metadata fields — such as tags, collections, categories, custom fields, or other non-text attributes — do not prompt the moderation queue.
AMN Healthcare has requested the ability to trigger the moderation workflow when metadata-only changes are made, without requiring edits to the Q&A content itself.
Use Case:
AMN Healthcare relies heavily on metadata (e.g., tags and categorization) to drive content organization, searchability, reporting, and downstream usage. Metadata changes can significantly impact how content is surfaced, filtered, and utilized across projects.
Because metadata adjustments can affect governance, compliance, and content accuracy, the team would like these updates to undergo the same review and approval process as Q&A text edits. Without this capability, metadata changes can be published without oversight, creating potential risks in content management and audit control.
Proposed Enhancement:
Introduce a configuration option that allows organizations to:
- Trigger moderation when metadata fields are modified, OR
- Select specific metadata fields that require moderation upon change.
This would provide greater flexibility for customers with strict governance and compliance workflows.
