Getting started

Review and approve

A change set waits for a decision before it becomes part of your configuration.

Open a change set and you can see exactly what's in it: the configuration items chosen, anything included alongside them, and the description its author wrote. Nothing about your setup has changed yet. A change set is just a proposal until someone decides on it.

The list of changes comes first on the screen, and the Approve and Deny buttons sit underneath it. You pass what's changing on your way to the decision, so scroll through the added, changed, and removed items before you get there. Anything under Changed opens up to show the old value beside the new one.

Approve or deny

You have two choices:

  • Approve: the change set becomes part of your configuration, the tracked record of how things should be set up.
  • Deny: the change set is set aside and doesn't join your configuration. Nothing in Aprimo changes either way.

Turning a change set down asks you for a short note saying what should change. The author reads it on the change set, under Turned down by and your name, so they know what to do differently next time.

If an AI agent put the change set together, it's marked Put together by AI at the top, and the review panel says so too. Same decision, same buttons. It's a nudge to read the changes rather than take the description's word for it.

Approvals are optional
A workspace can name the people who approve a configuration change and set how many approvals it takes. If you haven't turned that on, a change set becomes part of your configuration as soon as it's created. Turn approvals on when you want a second set of eyes first. See Set up approvals.

When a heads-up rule names people

A heads-up rule can ask specific people to approve before a change set goes ahead. Those people get a button of their own on the change set, under the rule's note: Approve this heads-up. Approving the change set itself is a separate act, done by whoever has the role for it. Someone who is both answers the rule and approves the change set in one click.

What approving unlocks

Once a change set is part of your configuration, it's ready to deliver to your other environments through a pipeline, carrying the same change from a sandbox up to production, with an optional checkpoint along the way. Mochi delivers it when a run carries it there, whether you start that run or a pipeline runs automatically.

If any checks name the change set's items, or belong to a work item it's linked to, they run in the environment it was captured from as soon as it's approved. The result shows on the change set's page.

Review and approve · Mochi Deploy docs