Pipeline setup - key prerequisites

Setting up a Pipeline in Gearset is straightforward, but a successful transition depends on having the right foundations in place first. The teams that move fastest are those that enter implementation with their environments, access, and people ready to go.

Use the four questions below as a quick readiness check. If you can answer "yes" to all four, you're in an ideal position to implement Gearset Pipelines.

Can you arrange your transition so that your shared environments, repository, and work in progress start from a known, clean state?

This means you can:

A new Pipeline is designed to take new development from developer environments through to Production. Existing work already sitting in shared environments isn't automatically accounted for, which can introduce conflicts and validation failures. Keeping a code freeze in place after the refresh prevents those environments from drifting again before go-live.

Yes? You're starting from the strongest possible foundation.

Do you have the Gearset licenses and Git access needed to run your Pipeline effectively?

Before implementation, you should have:

Deployment Teams gives you the collaboration features typically needed for Pipelines, including role-based access control, rollbacks, team-shared connections, and issue tracking.

The right Automation tier depends on how many orgs are included in your process, including developer orgs. The following table shows how many orgs each Automation tier supports.

For a full development and release process, Automation Teams is generally the better fit for most Pipeline implementations.

As a general rule, everyone developing changes should have their own Deployment license. This gives developers access to the full Pipeline experience in Gearset, including the Pipeline UI, validation results, code review scan details, and greater visibility as changes progress through the release process.

Yes? You have the core tooling needed to build and operate your Pipeline.

Can you create and approve the service users Gearset will use across your delivery process?

We recommend having dedicated service users available for:

Service users let Pipeline automation run with consistent credentials, rather than depending on one person's account. They may need administrator-level permissions, and access approvals are one of the most likely causes of delay, particularly where security teams, single sign-on (SSO), or Git administration are involved. Start any internal security or IT approval early, including approvals for other integrations you plan to use, such as Jira or Azure DevOps.

For the permissions the people setting up your Pipeline need, see Pipeline setup - minimum permissions needed to set up Gearset pipelines.

Yes? Your access and approvals are ready before implementation starts.

Is your team ready to change how they build, promote, and release Salesforce changes?

Gearset Pipelines introduces a structured release process built around Git, feature branches, pull requests, and automated promotion between environments. For the Pipeline to work effectively, the team needs to understand and consistently follow the agreed process.

That means being prepared to:

Gearset Pipelines is designed around a unified process for changes, helping provide a clear audit trail and preventing different deployment approaches from interfering with one another.

Yes? Your team is ready not just to implement a Pipeline, but to successfully adopt it.

You're in an ideal position to begin your Gearset Pipelines implementation.

If you answered no to one or more, you may still be able to implement Pipelines. Talk to your Gearset team about those areas before go-live, so your transition is as smooth as possible.

If you have questions about these prerequisites, or you're unsure which approach is right for your team, send a message to our support team, who will be happy to help.