Glossary
The handful of words Mochi Deploy uses, in plain terms. Each links to a fuller explanation where one exists.
Workspace
Where one team's environments, configuration, change sets, and work items live. Most teams need only one. Members, roles, and settings like approvals are set per workspace.
Environment
A connected Aprimo instance: a sandbox, a QA instance, your production instance. Each environment carries the instance's address and the credentials Mochi uses to reach it. You add each one once, and Mochi shows you what configuration lives there, reading it and, when a change is delivered, writing it. See Environments.
Production
An environment you mark as a delivery target a pipeline ends at. A workspace can have several. Several at the end of one pipeline deliver in parallel. See Environments.
Configuration
The tracked record of how your Aprimo configuration is set up: fields, content types, classifications, and the rest. It's built up one change set at a time. See Configuration.
Change set
A bundle of configuration changes, grouped so you can look them over and move them together. See Change sets.
Work item
A piece of work you're tracking, like a request or a requirement, sitting on a board. Link change sets to it and you can see what work reached which environment. See Work items.
Approval
An optional checkpoint where named approvers say yes before a change moves ahead. You can require any one of them, everyone, or a set number. Approvals are off until you turn them on. See Approvals.
Pipeline
An ordered path that carries a change from one environment toward a production environment, with an optional checkpoint along the way. See Pipelines.
Run
One trip through a pipeline. A run carries one change from an environment to the next and records what happened. See Pipelines.
Gate
A pause built into a pipeline. When a run reaches a gate it waits for an approval before going on, so nothing reaches an environment until the right person has said yes. See Approvals.
Roll back
Putting the configuration Mochi manages in one environment back to an earlier version. The changes stay part of your configuration, so they can reach that environment again later. See Undoing changes.
Undo
A change set that takes an earlier one back out of your configuration. It goes through review and delivery like any other change set. See Undoing changes.
Broken reference
A tracked item that points at a piece of configuration Mochi isn't tracking yet. Mochi flags these and helps you bring the missing items in. See Broken references.
AI access
The workspace setting that lets people connect an AI assistant to Mochi. Turning it on lets an assistant look at things; letting it change anything is a separate setting. See Give an AI agent access.