Profiles & Permissions

Share with


Transcript

Profiles, permissions, and permission sets are the backbone of every team's metadata setup. To make deployment smoother and faster, we've improved the way you can find and manage profiles and permissions that you need.

When initiating an instant comparison between your source and target orgs, you can manage custom filters by clicking here.

So that when selecting custom objects, you can ask Gearset to include profiles and permission set dependencies.

Once you have enabled this, Gearset will set this as the default behavior so you don't miss them in the future when loading custom objects as part of your on demand comparisons.

So let's take a look in the comparison with custom objects and profiles having been retrieved.

For example, when selecting the admin profile, I can easily pick out all the related aspects of that profile. In this case, all the different field level permissions.

I can choose them individually or select all.

I can also choose to remove any which appear in the target but not in the source, for example, this legacy field.

The hide unchanged toggle allows you to switch between seeing all components and only the change components for the selected profile or permission set, making it easier to spot the changes that you've made.

It's very easy to miss metadata types in your comparison. So whilst on a profile, by clicking fetch full profile, Gearset will pull in and retrieve any additional metadata types for you to reference.

When it comes to navigating the relations, you can view them from the profile levels up to its related objects, or you can start at the object level, view its related items as well as its profiles and permissions.

Again selecting what you'd like to include individually or in its entirety.

Once you're happy with your selection, you can move forward with your deployment.

Gearset's problem analyzer will make sure you have not missed any relevant metadata or, in this case, allow you to remove any items which shouldn't be referenced in your deployment.

And with that, you're ready to move forward and deploy your package. For more information on profiles and permissions, click on this link.