Creating a Gearset account
The best way to see how much easier Gearset makes deployments is to try it out for yourself. That's why we offer a totally free 30-day no-obligation trial.
Simply follow these steps to create your Gearset account:
Log in using one of your existing Salesforce, Google, or LinkedIn accounts.
Allowwhen prompted by Salesforce, Google, or LinkedIn.
Complete your Gearset profile by naming your Gearset team (or letting us create one for you using the name generator!), and entering a contact number. You can also opt into receiving occasional product updates by email. Your email subscription preferences can be managed later from the account page of the app.
CREATE ACCOUNTto finish setting up your profile.
That's it! After signing in, you'll be automatically set up with a totally unrestricted trial of Gearset and guided through some of our key features. During your trial you can use all Gearset's features, with no usage limitations. Learn more about Gearset's features.
Initial setup wizard
The first time you sign into Gearset, you'll be guided through linking your initial org connections and running your first comparison by our setup wizard.
If you're new to Gearset, this is a great way to get going. If you've already used Gearset before, you can skip this wizard using the link at the bottom of the screen.
START QUICK ORG COMPAREto get going.
The first step is to connect to a source Salesforce org - this is the environment in which you have some changes that you'd like to deploy.
To connect to your org using Salesforce authentication, enter the username of the org, select the org type and click
You'll be prompted to log into Salesforce and authorize Gearset to access this org. Click
Allowonce you've logged in. Don't worry, you're not changing anything in this org at this stage; this is just allowing Gearset to read the metadata for your first comparison.
Once you've authorized the connection, you'll be taken back to Gearset. If you wish, you can now set up automated unit testing and change monitoring for this org using the buttons below the connection.
ADD TARGET ORGto set up the connection for your second org.
Repeat the steps above for your target org: log in, authorize and set up any automated monitoring jobs.
Once you've linked your target org, click
REVIEW AND COMPARE.
With a source and a target org connected, you're ready to run your first comparison and see the configuration differences between them. If you want, you can customise your comparison filter here, or simply click
Gearset will now run a comparison between your two orgs and show you the differences. From here, you can begin to build a deployment package to move changes between them.
To find out more about running your first comparison and building a deployment, see our quick start guides.
Want a demo? Just get in touch
If you'd like to chat with one of our team to explore Gearset and your use cases in more detail, just let us know and we'll be happy to set up a call and a guided demo of the app.
You can reach us at [email protected], call +1 (833) 441 7687, or use our in-app chat.
A few common questions about creating your account
Will Gearset access the Salesforce org I log in with?
No. Gearset will not access the metadata from the Salesforce org you log into the app with. We only use your Salesforce/Google/LinkedIn account to create a local profile in Gearset. This saves you making you create a separate Gearset account, and means we never store or access your user credentials.
Which account should I log in with?
Your Gearset profile will be linked to the account you first log in with, so it's a good idea to pick one that's going to stay around. Your production Salesforce login or a Google account are ideal, but you can also use any developer or sandbox account too. Just make sure to sign in with the same account each time.
Note when using sandboxes: when sandboxes are refreshed, your Salesforce user account is sometimes deleted and recreated. This can mean you'll lose access to your previous history in Gearset, as your Gearset account is tied to a specific Salesforce user. We recommend you don't use sandboxes for paid Gearset subscriptions.