Team workspaces can review a submitted course version before it reaches a catalog. Publishing approvals are a workspace setting, with review policies and assigned reviewers on each catalog. Personal workspaces do not have catalog publishing reviews.
Set up a destination
In Publishing, manage catalogs and their covers, descriptions, audiences, courses, and ordered curricula. Enable workspace publishing approvals when your team needs them, then select the catalog’s reviewers and required number of approvals. Catalog management has its own role permission.
Catalogs have browse pages and can be connected to groups or Sites. A catalog’s audience determines who can access it. Review approval does not grant an audience access outside those settings.
Submit and review
- Finish the working draft and open Publish. Choose the destination catalogs; one submission can target several catalogs.
- Where approval is required, a request holds the submitted revision. Authors can continue editing without changing the version under review.
- Open Publishing reviews or a request from Inbox. Search and filter the queue, then select a request.
- Changes compares the lessons, questions, media, and settings affected by the update. Course preview shows the submitted learner experience.
- Leave comments on changed content or select a passage in the preview to start a thread. Choose Approve or Send back with feedback.
- Once the required approvals are satisfied, the publication can be delivered to its selected catalog. An approved request and a successfully delivered publication are distinct states.
Inbox collects review requests, course feedback, and publishing decisions across workspaces. Access to a request and permission to decide it are checked for each person.
Agent proposals
An Agent with permission to propose changes can prepare an update to selected courses and submit it to course editors or a catalog’s review queue. Its instructions describe the work; its access policy determines which knowledge, courses, and actions it can use. A proposal does not bypass the review policy.
Schedule recurring checks with Automations. The Knowledge base drift automation starter identifies affected courses and suggests updates; its default instructions do not edit them. To prepare actual changes, configure an Agent with proposal access and describe that task explicitly.
Drafts and history
A working draft, a submitted revision, and a catalog publication serve different purposes. Review uses the submitted version. Filesystem in course settings lets editors inspect saved versions and their files; optional branches provide a separate place to prepare changes. Version history and existing learner records remain available.