The automated provisioning to restore permissions has now been executed on all production instances. Following that fix, a subset of users in affected orgs on the NA53, NA57, and NA59 instances had their permission levels reset again, which gave them broader data access than intended. Customers on NA53 and NA59 may experience service disruption as we work through the removal of the inadvertent permissions in the affected customer orgs. For affected orgs on NA53, NA57 and NA59, users who had their permissions broadened have had their permissions restored. For admins that may need guidance on how to manually restore user permissions, please see the instructions in this Known Issue article http://sfdc.co/PermSetKI
The Salesforce Technology team is working urgently to resolve the issue. Customers should continue to check Trust for updates.
While the permissions issue did not affect every Pardot customer, we did disable jobs that sync data between Pardot and the Salesforce application in order to protect the integrity of our customers’ data. This action was taken at 17:30 UTC on May 17, 2019. As we work to restore permissions to affected orgs, we are also working to reenable sync between Pardot and the Salesforce application for those orgs that have not been affected or have had their permissions fixed. Data from interactions with Pardot is being queued, and will resume processing back to the CRM once it is safe to do so.
We have re-enabled Salesforce sync for Pardot customers with standard connector user permission configurations (https://sfdc.co/PardotPerms
), excepting those connecting with NA53, NA57, and NA59 Salesforce instances.