Navigate to the Compare and Deploy page in Gearset, and select your source and target orgs.

Check that you have your source, target and filter selected. Click "Compare now".

​

Choose a filter or select your metadata- if you don't already have a custom filter that you use for Permission updates then you can use Gearsets' "Default profiles comparison" which includes everything you need for deploying Permission sets and Profiles.
​

In the comparison you will be able to easily filter for the new Permission set you have created - look under "New items" and then filter for Permission sets and user permissions for that new Permission set.
​

If you have other new items you can filter for these as well using the same method - permissions do not have to be deployed separately to other metadata types.

Once you have found the components you would like to deploy to the target org select them and click "Next".
​

Gearset will now run Problem Analysis and Static Code Analysis.

Problem Analysis will highlight and remove references in the permission set to components that either don't exist or are not enabled in the target environment.

​

After reviewing the suggested fixes and warnings you can proceed to the "pre-deployment summary" screen, where you will see a summary of what you are deploying.

This should be your new Permission set, the user permissions for that new Permission set, and any other components you're deploying at the same time.
​

When you're ready to validate your changes you can click the "Validate deployment" button.
​

After the validation has run you will see a list of the validated components on screen. You can either immediately deploy this to your target org, or schedule the deployment for a later time or date.
​

Click "Deploy now" to deploy your changes.

Start by creating your feature branch.
​

Next click 'Start comparison'. Once the comparison loads select Permission Set and Permission Set Group from the available metadata on the left hand side.
​

Select your Permission set, and the Permission set group.
​

Add a commit message, and commit your changes.
​

Create a pull request to validate your changes against the first environment in your Pipeline.
​

The delta of your new changes will now validate against the target environment. If you want to see exactly what changes will be deployed you can click "view details".
​

This will show you your validated components. To see them in even more detail you can click "back to results".
​

On this screen you can see the xml that makes up your settings and subcomponents which are about to be deployed to the target environment.
​

After you are satisfied that the changes are the ones you're intending you can go through your normal process of reviewing the pull request and approving it.

After approval the Permission set and Permission set group can be promoted.
​

First deploy your Permission set.

I have a new Permission set in my source org, and have assigned it to my user. I am deploying the new Permission set to my target org.
​

Gearset problem analyzers make sure that the deployment will be successful.
​

After I have deployed the Permission set, I start a data deployment to deploy the Permission set assignments. By inputting the Permission set ID Gearset can find the assignments associated with that specific Permission set.
​

At the next stage we see the objects related to the Permission set assignments.
​

Finally we run the data deployment, and confirm it’s success.
​

At the end of this process I have deployed my new Permission set and the associated Permission set assignments successfully to the target org.
​