Resolved - Salesforce confirmed that full access to orgs is now restored. You can expect Salesforce to send out guides how to restore certain permissions manually via E-mail to the Administrators. For further updates please visit: https://status.salesforce.com/current/incidents
May 18, 13:08 BST
Identified - Salesforce continue to work on restoring access and permissions for customers affected by the permissions issue. During the restore process, some affected customers may receive error messages related to account status, billing, or single sign-on functionality after logging into Salesforce. There is no action you need to take if you receive these messages. We will update you with additional details and information on this situation as they become available.
May 18, 00:15 BST
Identified - Salesforce unblocked access for all orgs that were not affected by the permission issues. Customers with Pardot are still blocked. Once access is restored users will be able to make and receive calls via NVM within Salesforce
In parallel, they are working to restore the original permissions as quickly as possible for customers that were affected by the permissions change. Users in affected environments should continue to use regional URLs to access the ContactPad. Please continue to check Trust for updates https://status.salesforce.com/current
May 17, 23:30 BST
Identified - Salesforce have started unblocking customers who were not affected by the permission issues caused by Incident 3815. Once access is restored users will be able to mke and receive calls via NVM within Salesforce
In parallel, they are working to restore the original permissions as quickly as possible for customers that were affected by the permissions change. Salesforce customers who use Pardot, or have used Pardot in the past, will continue to have limited or no access to their orgs. Users in affected environments should continue to use regional URLs to access the ContactPad. Please continue to check Trust for updates https://status.salesforce.com/current
May 17, 21:48 BST
Identified - As a mitigation to the earlier permissions incident Salesforce will be restricting access to certain instances as they work to resolve the root cause. As a NewVoiceMedia user you can still take and receive calls in standalone mode by accessing via your regional URLs. Please contact our support desk if you need assistance. You can track status of Salesforce's incident on https://status.salesforce.com/
May 17, 19:38 BST
Investigating - We are aware of an ongoing Salesforce incident affecting the permissions of users, resulting in restricted access to certain objects or fields. This may cause subsequent issues with logging calls or creating records with NewVoiceMedia due to the permissions change.Only Salesforce customers who use a Pardot integration, or have used an integration in the past are believe to be affected.
We are liaising directly with the Salesforce support teams on this matter as will provide updates as soon as we can.
If you believe you are affected please raise a case directly with Salesforce. You can track the status of the incident on https://trust.pardot.com/
May 17, 16:44 BST