Why Granularity Matters  

Deploying metadata in Salesforce can often feel like a balancing act. Not every change is ready for production, and teams often need to deploy specific updates—like adjusting a single field in a profile or modifying part of a flow—without overwriting the entire metadata element. In large teams, the stakes are even higher. With multiple admins and developers working on the same elements—like profiles, page layouts, or flows—the risk of conflicts or overwrites increases significantly. Being able to do granular deployments helps mitigate these risks, enabling admins and devs to deploy specific changes without impacting others’ work, fostering better collaboration and minimizing deployment errors.

Deploy only what you need - no more, no less

Ever wanted to scope your deployment to include only a specific change you’ve made to a Lightning Page? Are you often finding yourself wanting to deploy only YOUR changes to production? 

Salto takes the granularity to the next level by breaking complex metadata into small, granular components. This means you’re not limited to deploying the entire metadata element, you can isolate and deploy only the specific parts you’ve worked on. For example, rather than pushing an entire flow, you can deploy just the specific changes you’ve made. Moreover, you don't have to take all the changes to the next environment - you can pick and choose which changes to include. Salto’s approach makes granular deployments not only possible but flexible, giving Salesforce teams full control over what gets deployed and when.

‍

The Benefits of Salto’s Granular Deployments  

1. Better control - Deploy exactly what you need and leave work-in-progress items behind 
2. Reduced risk - Minimize the chances of overwriting someone else’s work or deploying incomplete changes.
3. Improved collaboration - Multiple team members can work on the same metadata element without conflicts, streamlining teamwork in large teams.
4. Faster, incremental deployments - Roll out updates and fixes quickly by focusing on ready-to-go components instead of waiting for an entire element to be finalized.
5. Cleaner production orgs - Avoid pushing unnecessary or incomplete changes, keeping your production instance streamlined and error-free.

Salto’s Granular Deployments in Action  

Salto’s cherry-picking capability applies to all metadata types, but it’s particularly impactful for flows, lightning pages, value sets, permissions and CPQ records. 

When creating a deployment and picking the element you want to deploy, Salto will flag the changes made to the element. In the example below, you can see some deletions made to FLS permissions in a Solution Manager Profile. Salto will list all the changes separately. 

‍

‍

In addition, Salto will let you select the specific changes you want to delete. You can pick one, you can pick a few, or you can pick all of them by clicking the Field Permissions object above.

‍

‍

The same level of granularity and flexibility also applies to CPQ records. In the example below, you can see an SBQQ field with two modifications: one in the inline help text and the other a deletion of a value set. The user has complete control over the changes they want to make to that field, with the option to select either one or both modifications.

‍

To conclude   

Salto empowers Salesforce teams with unparalleled precision and flexibility in their deployments so they can deploy only what they need - no more, no less. By enabling granular deployments, Salto reduces risk, enhances collaboration, and streamlines workflows for both individual users and large teams. Whether you’re deploying critical bug fixes or coordinating complex, team-wide updates, Salto ensures your deployments are accurate, efficient, reliable, and ready for scale.

‍