Prompt template activation in the destination org
Key Takeaway
By default, prompt templates deployed with a change set arrive inactive in the target org, so someone must activate them there. Setup settings can make activation automatic, but only for change set deployments.
A prompt template must be activated before users can use it, and activating it picks the one version users get. A change set doesn't carry activation status by default. So when you deploy templates from a sandbox to production, they stay inactive until someone activates them. Setup settings can change this default for change set deployments, and one setting can also limit a deployment to the active version of each template.
What activating a template does
Prompt templates aren't available to users by default, because you usually draft several versions to test which combination of template body, grounding data and LLM works best. Activating a template makes one specific version available to users.
Only one version of a template can be active at a time. If no version is active, the template is unavailable to users.
Activating a version changes its status from Draft to Published. A published version can't be changed back to a draft, and it can't be modified, even after you deactivate it. When you deploy a published version, the deployment skips it. To change a published version, save it as a new version instead of trying to overwrite the published one.
When a template is in use, you can't deactivate a version unless another version is active. You also can't delete the active version.