This policy option is available for organizations that want to add layers of control over which Use Cases get published and who approves them. You can change these settings at any time.
Set the moderation policy
Open Queue, select Manage Approvals. This is only accessible for those with the roles: "Org Admin".
To change your moderation policy:
Open Queue.
Select Manage Approvals.
On How do you want to moderate your organization's use cases?, pick one card:
No moderation. All use cases are automatically published.
Select moderators maintain quality. Chosen people review each submission before it's published. This card is labelled Default (recommended).
Select departments maintain quality. Everyone in the departments you choose can review and approve.
How do you know which option is best?
No Moderation: Best for small teams without a formal process. This is the fastest way to get your Use Cases created and shared.
Select Moderators (Recommended): This lets you select specific people to create and maintain use cases in your AI Hub. This is best for organizations with subject matter experts in various departments who are best suited to approve use cases. This allows leaders and early adopters to keep growing by helping the organization.
Specific Departments: Best for organizations that silo approvals of information sharing through well-equipped teams with already established processes. Multiple departments can approve use cases, it is not restricted to just one.
This screen does not choose who can submit use cases. Only one policy can be active. The change applies to future submissions, never retroactively.
Selecting No moderation opens Are you sure?. Submissions will go live without anyone reviewing them first. Type confirm, then select CONFIRM.
Assign moderators
On Select moderators maintain quality, the dialog is Who can approve submissions. On Select departments maintain quality, it is Which departments can approve.
Org admins always have access and cannot be removed. The people or departments you add can review, edit, publish, and archive any use case in the organization, not only approve new submissions. What a moderator cannot do is in For Employees | Moderator Permissions.
Review the queue
Open Queue, open an item on Needs Your Attention, then approve it or send it back. The page subtitle is Use Case Queue is for Moderators Only.
Open Queue under Manage.
Stay on Needs Your Attention for items waiting on a decision, or open All Use Cases to browse decided ones. Search with Search submissions. Filter by Department on either tab, and by Status on All Use Cases.
Each waiting row is a New Use Case or a New Version.
To approve a new use case, open the row or select Approve and publish. Confirm Approve "name"?. It will be published to the AI Hub straight away and everyone it is visible to will be able to use it. Select Approve & Publish.
To decide a proposed change, open it and read the fields that changed. If a newer version went live after it was proposed, approving it overwrites that newer version. Select Approve & Publish to apply it, or Decline. Declining leaves the live use case as it is. Give a reason so the contributor can propose it again.
To send a new use case back, select Send back to the submitter. Fill in Why is this going back?, then select Send back. It will not be published. The submitter cannot resubmit that same draft.
Approved items leave Needs Your Attention and show on All Use Cases. If nothing is waiting, you see You are all caught up.
Version History
Version History is a tab on a use case that lists every published version, what changed, and who published it. You see the tab if you can review use cases.
The live version is labeled Current.
The change line says First published, the field names that changed, or a rollback that names the version it restored.
A score for that version shows when one exists. A version that is still scoring, or that failed scoring, shows a dash. A carried-forward score names the version the number came from.
A version is written when someone publishes or when a moderator approves a proposed change. Select View to open Past version as read-only. Restoring does not rewind the list. It adds a new version.
To restore, you need permission to publish. Open Past version, select Restore this version, confirm Restore version N?, then select Restore. Restore is hidden on the version that is already live, and it is not offered when the use case is archived or was sent back. If someone published while the page was open, select Reload history and try again.