OrgWideEmailAddress is not currently supported through the Metadata API as Salesforce classifies as data. This classification means that any changes to Organization-Wide Email Addresses won't appear as selectable changes in a metadata deployment or a pull request (PR), such as updates to Allowed Org-Wide Email Addresses within permission sets. Therefore, to deploy, this you will need to use our data deployment feature. Organization-Wide Email Addresses are integral to Salesforce's email and case routing system, ensuring consistent communication through designated addresses.
You can deploy these emails from your source org to target org by using the object OrgWideEmailAddress when configuring your data deployment: Here are the steps to deploy Organization-Wide Email Addresses using Gearset:
Open the Gearset app and navigate to the Data deployment section.
Configure the deployment source and target Salesforce environments.
Select the records corresponding to Organization-Wide Email Addresses from the available data objects.
Complete the deployment following Gearset's data deployment process.
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.