When a working preview meets the task, choose the Site that should receive it. A Project may supply several Sites, so identify the destination explicitly. Connecting a Project as a Site source does not release anything on its own.
Review before production
Inspect the selected component and saved source revision, the Site's visitor audience, production configuration, data compatibility, and readiness checks. Then use Release to Site or Update Site for that destination. The Site validates and activates an immutable revision. Source edits afterward stay in development until another authorized update.
If activation fails, inspect the release status and the Site's operational evidence. The previous healthy version should remain the serving version; do not treat a queued request as a completed release. Site releases covers the destination workflow and recovery boundary.
Example: release one change
Suppose the request board now supports priorities. Select the saved revision containing that change and the exact Site that should receive it. Check whether production needs a schema update and whether the existing records remain compatible.
After activation, open the Site and create or inspect a representative record under an authorized test workflow. Confirm the active revision and behavior rather than relying on the Project preview. See Site releases.
Hand off a reviewable release
Keep the selected revision, intended Site, checked workflow, and any data or configuration changes together in the release review. For example: “Release the priority-field change to the internal portal; existing requests should display Normal until edited.” Resolve an ambiguous destination before submitting the update.
Use Site access to review the audience and Testing to record what the selected revision has actually passed.
See Release Projects to Sites for the release overview.