In this guide, we’ll discuss why the SFDX default username is important in setting up and maintaining a CI/CD pipeline for Salesforce projects.
This guide explains how to implement CI/CD processes for Salesforce using Salto. It covers the role of Git integration in creating an accurate record of Salesforce configurations, linking changes to tickets, and enabling collaborative pull requests for structured approvals. You'll also learn about Salto's branching strategy, how changes are promoted between environments, and tools for conflict resolution. By automating validations and integrating with CI tools, Salto simplifies deployments and bridges the gap between admins and developers, allowing teams to adopt scalable CI/CD practices tailored to Salesforce’s unique needs.
This blog outlines our plan for a transformative 2025 in Jira administration, focusing on efficiency, simplicity, and smart automation.
We are excited to introduce Salto Pipelines — a feature designed to bring visibility, control, and efficiency to your release process. With Pipelines, teams can build an efficient release process, visualise it, track where each feature/change stands, and easily promote/back-promote them.
Philippa Greenwald-Warburg, revenue operations leader at Salto, shares her 2025 resolutions for a better Salesforce environment. From cleaning up the org to smarter automations, she’s focusing on simplicity, scalability, and user success.
As the chaos of the year-end fades, it’s time to turn our focus to fresh opportunities for improvement in 2025. For Zendesk admins, this means tackling the clutter, refining workflows, and embracing AI-driven tools—without losing sight of the human touch. In this article, we’ll explore actionable resolutions to optimize your Zendesk instance, including smart use of AI, decluttering outdated configurations, tactfully managing stakeholder requests, automating with precision, and prioritizing the agent experience.
USING SALTO
© Copyright Salto 2025 | Various trademarks held by their respective owners