Publish Review
Approve or reject requests to publish agents, apps, knowledge, design systems, and flows.
Publish Review is the queue where reviewers approve or reject requests to publish. When your account requires approval, publishing an agent, app, knowledge version, design system version, or flow doesn't go live straight away. It becomes a request here, and the item publishes once enough reviewers approve it.
The queue lists requests from every project in the account, and the Status filter narrows it. Requests for agents, apps, knowledge versions, design system versions, and flows all appear here. The separate Approval Requests page lists credit limit increase requests only.
Permissions
Open Publish Review
The View publish queue & evidence capability
Approver, Developer, Governance Manager, Auditor, Account Admin, Organisation Admin
Approve or reject a request
The matching Approve … to publish capability
Approver, Account Admin, Organisation Admin
Viewer and Billing Manager don't see Publish Review. A Developer can publish and see the queue but can't approve. See Roles.
How approval works
Each kind of publish has its own approval setting, and your account decides how many approvals it needs.
Required approvals
Start at 1 for every publish action.
Zero
With 0 required approvals, publishing happens straight away and no request is created. The setting accepts 0 to 20. An administrator changes it through the API, because no screen offers it.
Your own request
You can't approve it. A second person with the approve capability must decide it. An account with a single admin and approval switched on can't publish until a second approver exists or the setting is changed to 0.
Approvals kept
A request keeps the number of approvals that applied when it was raised. Changing the setting doesn't change open requests.
Edit access
Publishing or submitting an item for review needs edit access to it. Someone with view-only access gets an access denied error, and nothing is submitted.
One open request
Publishing again while a request for the same item is still open is refused. For an agent, the builder offers to replace the pending request.
Each kind of publish has its own count, so approval can be on for some kinds and off for others in the same account. For example, a design system version can wait for review while an app publish deploys at once, and Publish Review lists the design system request but nothing for the app. When you expect a request and don't see one, the count for that kind is 0.
The queue
The queue lists requests newest first.
Request
The kind of request, such as Publish knowledge version, Publish design system version, Publish flow, Publish agent version, or Publish app, with the item and version underneath.
Requested by
The person who submitted it.
Approvals
Approvals received out of the number required.
Status
Where the request stands.
Raised
When it was submitted.
Pending
No approval has come in.
Not published.
Partially Approved
Some approvals are in, but fewer than required.
Not published.
Approved
The required approvals are in.
The platform publishes it automatically.
Rejected
A reviewer rejected it. One rejection settles the request at once.
Nothing changes. The requester can submit again.
Cancelled
The requester withdrew it.
Nothing changes.
Request Details
Select a request, or open its row menu, shown as ⋯, and select View details, to open Request Details. The window has two tabs.
Overview
Request, Status, Approvals, Requested by, Raised, Request ID, the item and its version, Link, and Description. The fields that name the item depend on the kind of request. A knowledge request shows Knowledge and Version.
Activity
The timeline: who raised the request, how many approvals it is still waiting for, and each decision with its time and the comment the reviewer left.
The buttons in the window depend on who you are and where the request stands.
The person who raised a pending request
Withdraw Request
A reviewer who can approve a pending request
Reject and Approve
Anyone, on a request that has been decided
None
Link opens the item under review. You need access to the item to open it. Share the item with your reviewers if they need to look at it before they decide. Reviewing doesn't give them access. A reviewer without access to a knowledge request sees "Knowledge not found or you don't have access to this knowledge."
Decisions
Approve
Reject
Confirmation
The window asks Approve this request? and says that the item and version are applied once every required approval is in.
The window asks Reject this request? and says that the item and version won't be applied and that the requester will be told.
Comment for the requester
Optional. The requester and the other approvers can read it.
Required. Reject request isn't available until you type it. The requester and the other approvers can read it.
Buttons
Approve request, or Back to leave without deciding.
Reject request.
Result
Approvals goes up by one, and an Approved entry with your name, the time, and your note appears in Activity. At the required number, the status becomes Approved and the platform publishes the item. With more approvals needed, the status is Partially Approved.
The status becomes Rejected, and Approvals keeps its count. Activity shows your name, the time, and your reason. Nothing is published.
What the requester sees
In the knowledge, design system, agent, and flow builders, the publish button shows where the request stands.
Publish
Nothing is waiting. It opens a confirmation. With approval required, the confirmation asks to send the version for approval and says it's marked as published once approved. With approval off, it asks to publish the version and says it goes live straight away. After a rejection, the button returns to Publish, so the requester can submit the version again.
Pending Approval
The request was submitted. If an earlier version is already published, it stays live until the new one is approved.
Published
The request was approved.
Builder
A rejection reason doesn't appear in the builder. It appears in Activity on Publish Review, so tell requesters to look there, or share the reason with them.
Email to approvers
Eligible approvers get an email with the subject Approval needed: <request>.
Email to the requester
The requester gets Your request was <status>: <request> when it's approved or rejected. The email names the outcome but doesn't include the reviewer's comment.
Withdrawing
While a request is pending, the requester can select Withdraw Request in Request Details. The status becomes Cancelled. In the flow builder, the same action is Withdraw review, which asks Withdraw this review? and leaves the flow unpublished until it's submitted again.
Flow changes after submission
Flows are approved as submitted. If a step of the flow changes after it was submitted, approval doesn't publish it, and the request shows The flow was changed after it was submitted for review. Submit it again. Withdraw the review, or submit the flow again, to publish later changes.
What's next
Last updated
Was this helpful?

