Skip to main content

How to deploy OrgWideEmailAddress and related access in PermissionSets

Use Sandbox Seeding add-on (Data deployment tool) to deploy these changes with Gearset

Cecilia Califano avatar
Written by Cecilia Califano
Updated this week

OrgWideEmailAddress is not currently supported through the Metadata API as Salesforce classifies as data. Therefore, to deploy, this you will need to use our data deployment feature.

You can deploy these emails from your source org to target org by using the object OrgWideEmailAddress when configuring your data deployment:

Additionally, you can also deploy the related OrgWideEmailAddressAccess in PermissionSets:

To do this, you'll need to add the object SetupEntityAccess to the deployment configuration. This object defines access for multiple objects.

You can perform this in the same data deployment as the OrgWideEmailAddress or you can match on Id if the emails already exist in the source and target and those orgs are related (i.e. sandboxes from the same production org). No other external Id is needed to match those emails between source and target.

Please note that before attempting this data deployment, the PermissionSets must exist in both source and target with the same API name.

Did this answer your question?