Public role privilege modification impacted for some Business Critical instances

What happened

On June 27th, the new predefined roles feature*  for AuraDB customers inadvertently removed database Admin access from some Business Critical (BC) instances. As a temporary fix, the team disabled the feature for Business Critical instances. While the fix took place, it also replaced the database public RBAC role privileges which are available on Business Critical with enhanced public role privileges available on Free/Pro instances. System logic prevented customers from modifying the public role during that time.*https://neo4j.com/docs/aura/user-management/#_predefined_roles 

Neo4j restored the public role to its original limited permissions for all Virtual Dedicated Cloud instances on June 30, and for all Business Critical instances on July 1. 

How customers were affected

Customers were affected by this issue from June 27th to July 1st.  The issue impacted some Business-Critical (BC) instances and a small number of Virtual Dedicated Cloud (VDC) instances. All project admin users with affected instances received an email confirming the issue was resolved on July 1st. 

What we are doing now

Neo4j remains committed to providing reliable service and is implementing additional safeguards to prevent similar incidents in the future:

• We have implemented safeguards in our system to prevent misconfigured role changes and better isolate feature toggles from production permission models
• We are reviewing our internal release processes to improve testing and validation of role-based access control (RBAC) changes
• We are implementing additional detection methods for misconfigured RBAC which will alert our operational teams