Pipelines in Prodly give you structured control over how deployments move across environments, ensuring better governance, visibility, and consistency.
You can create multiple pipelines to support different teams, business units, or workflows—each with its own stages and environments.
Pipelines can only be set up by Prodly Admins.
To enable Pipelines:
Once enabled:
<aside> <img src="/icons/warning_red.svg" alt="/icons/warning_red.svg" width="40px" />
By default, all environments that are not designated as Development Environments will be restricted from adhoc deployments until they are added into a Pipeline.
This means that for Adhoc Deployments, and Deploying a Bundle as a Template, environments that are not part of any Pipeline will have no available destination environments to deploy to and won’t show up as a destination environment for other source environments.
</aside>
Set up pipelines to restrict the flow of deployments through your environments by following these steps:
<aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" />
By default, all Prodly users will be able to view and deploy through this pipeline. You can configure who has access to this Pipeline via Salesforce’s sharing rules.
</aside>
Your newly created Pipeline will appear as a new tab on the Environments page navigation.