Manage assets and versions
Assets are reusable building blocks such as prompts, flows, model settings, and policies. A release uses specific asset versions so that its configuration can be reviewed and reproduced.
Before you start
Choose the workspace where the workload will use the assets. You need permission to create assets or versions there. Shared and built-in assets can have different editing restrictions.
Create or reuse an asset
- Open Build → Assets.
- Search for an existing asset that meets the workload’s needs before creating another.
- To create one, choose the new-asset action and select the appropriate kind and owner.
- Complete the fields shown by its builder or editor.
- Review validation messages, save the content, and create the version required by that asset’s authoring workflow.
Some asset kinds use dedicated builders; others use a generic content editor. Follow the validation and save controls on the selected kind rather than assuming all editors have the same steps.
Check the result
Open the asset and confirm that the intended version exists and its validation succeeded. Saving an editable draft is not always the same as creating a version that can be used in a release.
Versions are immutable. To change a released configuration, create a new version and update a draft release to use it. Editing an asset’s metadata does not replace the versions already used by existing releases.
Resolve common problems
| Problem | What to do |
|---|---|
| The asset is missing | Check the workspace and whether it is shared with you. |
| Validation fails | Correct the fields identified by the editor and validate again. |
| A model or connection cannot be selected | Ask the administrator responsible for its approval, availability, or credentials. |
| An asset cannot be edited | Check whether it is built-in, shared, or outside your editing permissions. |
Next
Prepare a release using the asset versions you have checked. The technical asset reference provides field and schema details for integrations.