Pipelines in Prodly give you structured control over how deployments move across environments, ensuring better governance, visibility, and consistency.
Enabling Pipelines
Pipelines can only be set up by Prodly Admins.
To enable Pipelines:
- Navigate to Settings in Prodly.
- Turn on the “Enable Pipelines” toggle.
Once enabled:
- Click the “Create Pipeline” button on the Environments page.
- A new Pipeline tab becomes visible in the Environments page.
By default, all environments that are not designated as Development Environments will be restricted from deployments until they are added into a Pipeline.
Development Environments
By default, the following are designated as Development Environments:
- Developer Sandboxes
- Developer Pro Sandboxes
- Scratch Orgs
Admins can manually change any non-production environment to be a Development Environment by:
- Clicking on the environment card in the Environments page.
- Checking or unchecking the “Development Environment” checkbox.
Product environments cannot be designated as development environments via the UI.
Deployment Flow with Pipelines
- Development Environments can deploy to each other and to the first stage of any pipeline.
- You can define stages within a pipeline and assign environments to each stage.
- Deployment flow is restricted to follow the structure of the pipeline. You cannot skip stages.
- Back deploying is not restricted.
- Deploying between environments in the same stage is not restricted.
If a branch is linked to an environment in a pipeline, any deployments from that branch will also follow the same stage-based structure.
Access & Permissions
- Only Admins can create and edit pipelines.
- Pipelines are public and visible to all users.
- All users can deploy through pipelines by default, but access can be restricted via Salesforce settings.
Multiple Pipelines Support
You can create multiple pipelines to support different teams, business units, or workflows—each with its own stages and environments.
Where Pipeline Restrictions Apply
Currently, pipeline restrictions only apply to Ad Hoc deployments.
Other deployment methods, such as Bundles, Releases, and Pull Requests do not follow pipeline stage restrictions because:
- Access is managed from the source environment.
- Bundles do not have a source environment, so pipelines cannot control their flow.
We’re actively working on expanding pipeline support to Bundles in a future release.
API & CLI Availability
- Pipelines are fully available via API.
- CLI support is coming soon—stay tuned!
Feature Summary
| Feature | Available |
|---|---|
| Setup (Admins only) | ✅ |
| Enable via Settings (Admins only) | ✅ |
| Create/Edit Pipelines (Admins only) | ✅ |
| Public visibility | ✅ |
| Stage-based deployment restrictions | ✅ |
| Branch deployments follow pipeline | ✅ |
| Multiple pipelines supported | ✅ |
| Applies to Ad Hoc Deployments | ✅ |
| Applies to Bundles, PRs, Releases | ❌ (Coming soon) |
| CLI support | ❌ (Coming soon) |
As always, we welcome your feedback and questions. Please feel free to get in touch with your Account Manager at Prodly.