Skip to main content
A workspace’s release policy decides when saved revisions of releasable records reach their consumers. Use Automatic for release after required checks, or Manual when an owner or workspace administrator must choose the revision to release.
A new workspace uses Automatic. Until someone changes it, each revision an agent, MCP client, or API call saves is released once any required security checks pass, and no person has to approve it. If your team reviews work before agents or colleagues get it, set Manual before anyone starts building.

Before you begin

Before you start, make sure you have:
  • Workspace role: The Admin role on the workspace. Being an Admin of the organization doesn’t include it. A workspace member without the role can read the settings and sees “You don’t have permission to change how this workspace releases.” See Workspace roles and access.
The policy applies to every kind of record that supports releases. The page describes skills and agents, and the same setting decides when metrics and saved queries written to the workspace are released. See Decide what reaches agents without review. The policy does not deploy application code. The page sets the policy for the latest channel.
1

Open release settings

Open Settings, choose the workspace under Workspaces, and select Releases. Policy says whether the settings use defaults or workspace overrides.
Workspace release settings with Publishing set to Manual and Require security checks enabled.
2

Choose policy

App definitions are released only by hand: Automatic doesn’t publish their saved revisions. An owner or workspace administrator releases them, as under Manual.Turning off Require security checks allows a release before its scan finishes. Plugins still omit that revision until it passes. If the scan blocks it, the channel serves nothing for the skill until another revision is released.
3

Save policy

Select Save changes, then confirm Release policy saved. While the form has unsaved changes, an After you save note previews what the draft will do. Leaving with unsaved changes asks you to confirm Discard and leave.To clear the workspace overrides, select Use the defaults under Policy, review the confirmation, and confirm Use the defaults. This also discards unsaved policy edits; the app confirms Release settings reset to defaults.
4

Verify result

Reopen Releases and confirm the saved settings. On the next skill change, check Source: Manual leaves an eligible saved revision waiting for release; Automatic releases it once the required checks pass.

Troubleshooting

If a save is refused or you can’t change the policy, see Workspace access errors.

Next steps