Operations

A catalogue of org-management operations — access, packages, sandboxes, and tests — each run as a tracked, approvable flow.

codev is repository-first, but orgs still need day-to-day administration — access grants, package installs, sandbox lifecycle, test runs. Manage Orgs > Ops presents these as a catalogue of operations. Operations is instance-wide: it sits outside any single project and acts on the orgs the instance has registered — an operation's form asks for the project where one is relevant. Each operation is created from a card, runs as a flow on the codev server, and lands under Recent Runs.

The Operations page with catalogue cards grouped into Access, Package, and Environment operations, and the Recent Runs panel alongside
The Operations catalogue — access, package, environment, and test operations, with recent runs alongside.

The catalogue

GroupOperations
AccessRequest elevated privilege in production · Freeze users in an environment · Unfreeze frozen users by profile
PackageInstall an sfp artifact to one or more orgs · Install a managed or unlocked package
EnvironmentCreate a Salesforce sandbox · Refresh a sandbox · Delete a sandbox · Sync an org to a branch
TestRun Apex tests on an org, optionally storing the results for dashboards

The catalogue requires the project's issue tracking integration to be configured — operations are raised and tracked as issues. Workflow Settings turns individual operation flows on or off for the project.

Running an operation

Create on a card opens the operation's form: the project, the target org or environment, and the operation's parameters. Submitting starts the operation in the background; its progress and outcome appear under Recent Runs, filterable by project and category. An operation behind an approval gate waits for the approval before executing — a waiting run shows where under Flows.

The Ops - Sync dialog with project, target environment, org-to-branch and branch-diff-deploy modes, branch, domain, packages, test level, and a dry run option
Sync an Org to a Branch — converge an org to what a branch defines, with a dry run to preview the changes.

The sync operation shows the repository-first model directly: it compares the artifacts installed in an org against a branch and deploys only the changed and new packages — converging the org to the branch. The same capability, approached from the environment side: Syncing environments.

  • Elevated access requests — the access operation's approval flow and automatic revocation
  • Approvals — how gated actions are approved
  • Flows — runs, statuses, retries, and turning flows on or off

On this page