Submit content to workflow
Put your changes into an update package so they enter your review team’s workflow, then follow their progress from the Dashboard.
Before you start: workflow runs on packages, not individual items — if packages are new to you, read Update packages first. Workflow must be enabled for your repository; the steps, their names, and who reviews each one are configured for your organization, so the examples below will look different on your system.
Submit your changes
Section titled “Submit your changes”- Make your change and save it — save an edited item, or save pages in the site editor while working inside a package.
- Get the change into a package, in whichever way applies:
- If a dialog appears when you save (Add to Package? or Package Required), choose an Existing Package or a New Package — give a new one a name and optional description — and click Submit to Package.
- Otherwise, add the item to a package yourself with the Add to Package action.
- That’s it. When a package is created in a repository with a default workflow, its review workflow starts automatically — the package’s workflow history begins with “Package submitted to workflow”. Your package now appears in the dashboard queue and moves to the first review step.
Track packages in the dashboard queue
Section titled “Track packages in the dashboard queue”The Dashboard’s My Queue section lists packages in workflow, with a count on each tab:
| Tab | Shows |
|---|---|
| Assigned to Me | Packages whose current step is assigned to you — these are waiting for your action |
| My Packages | Packages you created |
| Unassigned | Active packages nobody has picked up yet |
| All Active | Every package currently in workflow |
| Approved | Packages that finished review and are ready to merge |
Each row shows the package name, workflow, current step, assignee, start and last-updated times, and status. You can filter the queue by package name or repository, sort by the date columns, and click any row to open the package’s review page. The Merge history link at the right of the tab row opens the list of already-merged packages.
If you are a reviewer
Section titled “If you are a reviewer”When a package reaches a step assigned to you, open it from Assigned to Me. The header of the package review page shows the current step and the actions that step allows — typically:
- Approve — advance the package to the next step.
- Reject — send the package back for revision (see Rejections and resubmitting).
- Route for Approval — pass the package on to the next approver.
- Cancel — end the workflow. This deletes the package and cannot be undone.
- Assign / Re-Assign — hand the step to an eligible user. Only members of the groups configured for the step can be assigned; if you are eligible yourself, an Assign to me shortcut appears.
Exactly which actions appear, and what the steps are called, depends on your organization’s workflow configuration. Each action opens a confirmation dialog with an optional Comment — the comment is saved in the package’s workflow history for others to read. You must be the step’s assignee (or an administrator) to act on it.
What happens on completion
Section titled “What happens on completion”When the final step is approved, the package’s status becomes Completed:
- If your repository is configured to merge automatically, the package is merged — and optionally published — right away.
- Otherwise the package appears under the Approved tab with a Merge button on its review page, for a manual merge.
Merging applies the package’s changes to the main repository and site — see Update packages for what a merge does.
Verify
Section titled “Verify”Open the Dashboard: your package appears in My Queue (under My Packages, and All Active while review is running). Its row shows the current step and who it is waiting on. On the package’s review page, the workflow history records every submission, approval, and comment.