Skip to main content
Goosy prepares the work; you decide whether it goes. Review in the sidebar is where every decision waiting on you collects — one queue, whatever kind of work it is. It opens with a count and the order it is in: 10 waiting on you · most urgent first.

​
Read a row

The queue is a table, and the columns are the whole story: Most urgent first means money leads, then whatever has been waiting longest against a deadline. You do not have to sort it yourself.

​
Decide

The actions on a row match the decision it is. They are not the same on every row, and that is deliberate:
  • Approve and Deny on something that spends money.
  • Approve and Send back on a change to something already running. Sending it back returns it with your reason attached.
  • Read the claim first, then Decline, where you are being asked to accept or reject something written down — you are shown the exact wording before you rule on it.
  • Read and decide on an inbound reply, which opens the message.
  • Details on most rows, for the longer version.
Some rows are marked Decided where the work is and offer Open instead of an approve button. That is not a broken row: a whole piece of content is accepted in the lane where it was made, and the queue’s job is to tell you it is ready and take you there.

​
Deciding several at once

Tick rows and decide them together. The header checkbox is labelled pick every row that can be decided here, and it means it — on a queue of ten it may pick three, because the rest are the decided where the work is kind. The bar that appears tells you what you picked and what it can do: Approve and Decline in bulk, and a plain note that sending things back is one at a time, because some of them ask you for a reason.

​
Narrowing the queue

Filter chips run along the top: Everything · Changes · Approvals · Assets · Pieces · Spend · Publish checks · Replies · Offers. They filter what you can already see; they never reveal anything new. You only see what you are allowed to decide. The queue is shaped by your role and permissions, so two people on the same workspace can open Review and see different lists.

​
An empty queue

“Nothing is waiting on you” is the goal, not a gap — you approve as you go. If one part of the queue could not be read, the surface says so rather than quietly showing you less. Treat a short list carrying that message as incomplete, and come back to it.

​
What Review is for

Approving something here is the human decision the product always stops for. Publishing, spending, deleting and granting access never happen without one, whatever role the person holds, and whether the request came from you or from an assistant acting on your behalf.